Back to the knowledge base
Technical and reachability1 min read

Your stream does not work on a secure site, here is why

Fixing mixed content blocks with the free SSL proxy.

Website on https but your stream on http? Browsers block your player. That is a mixed content block, and it is the most common reason a player fails for some visitors.

How to recognise it

  • The player loads but there is no sound
  • Your browser console shows a message about mixed content or an insecure resource
  • It sometimes works on mobile and not on desktop, or the other way round

The fix

Every radio plan includes a free SSL proxy. You then use an https address for your stream instead of http. You find that address in Centova Cast, or request it via a ticket.

Does not work:  http://stream.centova.nl:8000/stream
Does work:      https://stream.centova.nl/yourstation

Replace the address in your player and in your directory listings and the problem is gone. TuneIn and most apps also work better with an https address.

Everywhere you need to change the https address

  • The player on your own website
  • Your listing on TuneIn and other directories
  • Links you share on social media
  • Your app if you had one built
  • Any third party widgets

Checking it yourself

  1. 1Open your website in Chrome.
  2. 2Press F12 and go to the Console tab.
  3. 3Refresh the page and click your player.
  4. 4A red mixed content warning means there is still an http address somewhere.
  5. 5Search your page source for http colon slash slash and replace it with your https address.

A padlock in the address bar only means your page is secure, not your stream. The console does show whether unsafe parts are still being loaded.

Still stuck?

Open a ticket and describe what you see. You get an answer from someone who works on the servers, usually within a few hours.

Open a ticket