Server appears to go offline when listener limit is reached


If I set the max connection to 10 (for example), and 9 or more listeners tune in, Centova Cast reports the server as being down, and the "Server Administration" link and ShoutCast administrative URL at stops responding.


This is not a bug, and it is not related to Centova Cast -- this is unfortunately just how ShoutCast works.

The "listener limit" in ShoutCast is actually a "client limit", and every connection to the ShoutCast server (whether it's an administrative connection to the "Server Administration" or http://server-name:port link, or an actual tuned-in listener) is counted toward that limit.

Once you reach that limit, ShoutCast will not allow any further connections of any kind, which is why Centova Cast thinks the server is down and the administrative link no longer works.

Unfortunately, because this is an internal "feature" of the ShoutCast server application, there is nothing that we can do about this as part of Centova Cast.

  • 8 Користувачі, які знайшли це корисним
Ця відповідь Вам допомогла?

Схожі статті

Intro file or fallback file does not play

Question: I uploaded an intro file, but it does not play when listeners tune into the...

Kicking the autoDJ

Question: When I kick the autoDJ and begin streaming live, Centova Cast reports an...

Listener statistics show more listeners than listener limit

Question: I notice that in my listener statistics, some hours show more listeners than the...

Problems tuning in: Intro file plays, then stream stops

Question: When listeners tune in, they only hear the intro MP3 and then playback stops....

Problems tuning in: Relayed stream stops after 30 seconds

Question: When listeners tune in to my relay stream, they are disconnected after 30 seconds....

Powered by WHMCompleteSolution