Question:When I start a stream in Centova Cast, it reports that the stream has been started successfully, however I am unable to connect with a live source or encoder software. How do I fix this?
Answer:This indicates one of the following problems:
- You are connecting to the wrong hostname or port. Please login to Centova Cast and click the "Quick links" page to double-check the source connection details for your stream.
- You are using the administrator password for your stream instead of the source password. Note that every stream has two passwords; theadministrator password is used to manage the stream, and the source password is use to connect with a live source. If you configure your live source software to use the administrator password, it will not be able to connect.
- You are connecting to a ShoutCast server and another streaming source (or the autoDJ) is already active on the server. You will need to either turn off the autoDJ or disconnect the other streaming source before you will be able to connect with your live source.
- You have configured the stream to with "localhost" or "127.0.0.1" (known as the "loopback address") as its IP address and/or hostname. Binding any server to the loopback address will prohibit any connections that do not originate on the streaming server itself.
To fix this, change the stream configuration to use the actual IP address of your server.
- You have a firewall blocking your stream ports. Your firewall may be on your machine itself (i.e., an iptables software firewall) or it may be implemented by your datacenter/hosting provider through a hardware firewall.
Note that for ShoutCast servers, the streaming source port number is actually your stream port number PLUS ONE. So for example, if you have configured your stream on port 8000, you also need to open port 8001 in your firewall otherwise your live source will not be able to connect.
To fix this, contact your systems administrator and ask them to allow access to your stream port.
It still doesn't work, what do I do?
Please note that in the vast majority of situations the problem is one of the above; please ensure that you have thoroughly examined the above possibilities before seeking another potential cause.
If you are absolutely certain the problem is not above, please contact support.