External Source Connection Failure
When using an externalSource content engine, TVS may display an “Connection Error” message when trying to connect to a Television Simulator Studio headend server.
Why does this error occur?
Section titled “Why does this error occur?”This error typically occurs when TVS is unable to connect to the specified headend URL. Common reasons include:
- The URL is incorrect or malformed.
- The external source server is down or unreachable.
- Network issues preventing TVS from accessing the external source.
- Firewall or security settings blocking the connection.
- CORS (Cross-Origin Resource Sharing) restrictions on the external source.
Troubleshooting Steps
Section titled “Troubleshooting Steps”-
Verify the URL: Double-check the URL specified in the
externalSourcessection; it should be in the formathttp://your-tvs-studio-server:3994/headend -
Check server status: Ensure that the the TVS Studio instance is operational and accessible from the network where TVS is running.
For Server Admins
Section titled “For Server Admins”If you’re the administrator of the TVS Studio server, consider checking the following:
-
Public URL configuration: In
appsettings.json, ensure thatHeadend:PublicUrlis set correctly to the URL that clients will use to access the server.appsettings.json {"Headend": {"PublicUrl": "http://your-tvs-studio-server:3994/headend"}} -
Network connectivity: Test the network connection to ensure there are no issues preventing access to the TVS Studio server (e.g.
http://your-tvs-studio-server:3994).Make sure you can reach the server from the machine running TVS. You can use tools like
pingorcurlto test connectivity.Terminal window ping your-tvs-studio-serverTerminal window curl http://your-tvs-studio-server:3994 -
Firewall settings: Review any firewall or security settings that may be blocking TVS Studio traffic (is port 3994 open?)
For example, on Linux with UFW:
Terminal window sudo ufw allow 3994/tcp -
HTTPS vs HTTP: If your TVS Studio server is running behind a reverse proxy, make sure the protocol (HTTP/HTTPS) matches what is configured in the
PublicUrl.