Blank Page Issue in Sonarr Identified with Purew White Background

Hi guys,

Pure white background screen testing has been incredibly helpful in identifying display issues, and I used it to check if the blank page problem with my Sonarr setup was related to rendering issues. When accessing Sonarr via localip, everything works fine. However, when using mydomain, I can log in, but it displays a blank page afterward.

This issue also occurs with Radarr and Bazarr. The white background testing confirmed that the problem is not related to my browser or device display, so it seems to be tied to the Nginx configuration or Docker setup.

Has anyone else experienced this issue? Could it be related to reverse proxy settings or container misconfigurations?

Guarantee your reverse proxy is misconfigured.

Review your implementation with the official one on the wiki.

F12 browser network tools may give some insight as well

I am having the same problem. It is not related to reverse proxy, I don’t even have that configured.

This just started happening for me today when i upgraded to latest version of chrome (Version 131.0.6778.71 (Official Build) (x86_64)). I disabled all plug-ins to test, still nothing. It looks like Chrome thinks this is some sort of an app and wants to “launch” it as an app, not render it like a web page. Same thing happens in prowlarr, so it is the entire family of apps that are affected.

I tried it in safari (I am on a mac BTW) and it works fine. It is something with the new chrome browser.

Hi everyone,

Pure Black screen appears when I try to access the Sonarr web interface. The page loads partially, but the interface stays blank, and I can’t interact with it.

Iam using Sonarr version 3.0.9 on Windows 10, accessed through Google Chrome. This issue started after a recent update. I have tried clearing the browser cache, restarting the Sonarr service, and checking the logs, but I haven’t found a solution for Black screen yet.

Has anyone encountered this issue or knows how to fix it? Any help would be appreciated. Thank you!

I haven’t been able to reproduce this issue in Chrome, does it also happen in an Incognito window in Chrome?