add exception

Hi @radra,

The intention of enforcing SSL on a website is not to allow any insecure content. If the audio stream only works via http, this is considered insecure.

The best solution would be to explore whether the audiostream could be upgraded to work over https as well. If for any reason this is not possible, it is possible to exclude single pages from SSL. These articles might be of assistance:
https://really-simple-ssl.com/knowledge-base/exclude-url-mixed-content-fixer/
https://really-simple-ssl.com/ssl-only-on-a-few-pages/

Please note that browsers will keep showing insecure warnings for these pages.

Kind regards,
Leon

it doesn’t work on chrome ??

this is the message i’ve got:

(index):1 Mixed Content: The page at ‘https://rvecj.ro/’ was loaded over HTTPS, but requested an insecure element ‘https://89.36.154.3:8000/stream.mp3’. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

The problem is that the stream.php file is requested over an ip number, which doesn’t have an SSL certificate.

If you the stream.php file is hosted on your own website, you can change the ip number to your domain, which should resolve the issue.

Hi @radra,

Did you manage to resolve the problem, or do you need any further assistance?

Regards,
Leon