Mixed content behind SSL reverse proxy

I setup Sonarr 2.0.0.2850 behind a reverse proxy with SSL and I’m getting the following message in the browser console:

Mixed Content: The page was loaded over HTTPS, but requested an insecure script ‘http://piwik.nzbdrone.com/piwik.js’. This request has been blocked; the content must be served over HTTPS.

I know this is pretty trivial, but just wanted to bring it to the devs attention. Looks like piwik is just used for analytics, so this probably doesn’t affect any functionality of Sonarr, right?

Thanks for letting us know, we have fixed it in develop already (not sure if you caught that on IRC).

1 Like

Awesome, thanks for the update! I dropped out of IRC before seeing that.

I thought I would reply to this topic rather than create a new one, since the title accurately reflects what I wanted to talk about. I’m also using Sonarr (2.0.0.3154) behind a reverse proxy with SSL.

Mixed Content: The page at ‘https://{mysonarrdomain}/addseries’ was loaded over HTTPS, but requested an insecure image ‘http://thetvdb.com/banners/posters/81189-10.jpg’. This content should also be served over HTTPS.

This seems to happen for all banner images loaded when searching for a series. Changing the prefix to HTTPS works just fine and I believe TheTVDB has full site HTTPS support, so it’d be nice for Sonarr to load them over HTTPS by default.

Thanks, I’ve added an issue to Github to track it: https://github.com/Sonarr/Sonarr/issues/583

Nice, thanks!