Modern browsers block http:// audio on https:// websites. This is called "mixed content", and it is the most common reason a player "won't play". SHOUTcast Widgets handles this for you automatically.
How it works
- When a widget or station website is shown on an HTTPS page and your stream is plain
http://, the audio is played through our secure stream proxy. - Your listeners get a secure
https://connection, and your stream server doesn't need an SSL certificate. - This applies to the players, the Website Builder themes and the stream URL returned by the API.
You don't need to change anything. Leave Direct Stream URL blank, or enter your normal http:// address, and the proxy is used when it's needed.
Checking your stream type
Open Quick Links. The Direct Stream URL card shows either an HTTPS badge or an HTTP only badge.
If you build your own player
If you use your own <audio> tag on an HTTPS site with an HTTP stream, the browser will block it. Either:
- use one of our player widgets, which use the proxy automatically, or
- use the
stream_urlvalue from the Now Playing API, which is already the right URL for your page.
Still silent? Check the stream plays when you open the Direct Stream URL in a new browser tab. If it doesn't play there, the problem is with the stream server or encoder, not the widget.
Autoplay: browsers don't allow audio to start without a click. Players show a play button, and visitors need to press it once.
