Cannot Access Shoutcast Admin Page

If you are having issues acessing the Shoutcast Admin Page it is most likely due to a http redirect. Modern browsers are increasingly redirecting the access to http websites to https, for security reasonc outlined in HTTP Strict Transport Security (HSTS) policy.

The SHOUTcast administration page is not accessible with HTTP/SSL. This is a known issue with SHOUTcast 2.6 server and is not a problem exclusive to MediaCP software.

We have contact SHOUTcast about this and from what we can tell they are not interested in fixing this anytime soon: https://www.mediacp.net/portal/index.php/knowledgebase/89/SHOUTcast-Admin-is-not-working-with-HTTPS-or-SSL.html

As a workaround for now you can regain access to the admin.cgi page by excluding the panel domain from redirection. On Chrome/Edge/Chromium based browsers follow these steps:

  1. Go to the following page: chrome://net-internals/#hsts
  2. Scroll all the way down to the section below and enter your panel domian, then selcect “Delete”
  3. You should now be able to access the shoutcast admin page in your browser without issue

If this does not resolve your issue please contact our helpdesk so we can look into this further: https://www.mediacp.net/portal/submitticket.php?step=2&deptid=2

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Media tracks or files placed directly in content is not detected

Media file information is processed and stored in the database which means that files placed in...

AutoDJ -> Shoutcast Transcoder 2 (sc_trans v2) dj port 32kbps sounds terrible

With the latest release of sc_trans v2, there appears to be a bug (referenced here) causing low...

Creating a Relay Stream

Creating a Relay Server Create or Manage a shoutcast server. Select the Relay tab under the...

Streaming NSV video files guide

Streaming NSV Video Files Open NSVGUI 2 Locate the files you have just encoded and add these...

Delay between stream and listener/viewer

We are often asked why there is a delay between the stream source and the listener, this is due...