Blank Screen after upgrading to macOS Sierra

I was running Sonarr successfully on pre-GM public betas of macOS Sierra. After updating to the GM I’ve not been able to get to GUI.

I can run Sonarr, and it sends shows to SAB, but I can’t login or get to anything from all browsers, and different computers.

Updated the Sonarr.app to the latest build, and that made no difference.

Looking for ideas to resolve, is anybody else experiencing this too?

Do you get the login page?

If so try disabling authentication and re-enabling it.

I do not get the login screen, should I give that a shot anyway?

No it, probably won’t help.

You could try: https://github.com/Sonarr/Sonarr/wiki/FAQ#i-use-sonarr-on-a-mac-and-it-suddenly-stopped-working-what-happened

Without the logs requested when you opened this thread we don’t know what the issue is though.

@randyharris Yes, give disable-authentication a shot.
@markus101 iirc, the other guy explicitly browsed to /login after he got a blank screen

Sorry for not including logs.

I did try the disable authentication as Taloth recommended, and it did in fact get me to GUI!

Thanks very much.

well it doesn’t end there… If I disable authentication I get in and get GUI no problem, but upon restarting Sonarr after re-enabling authentication I get blank screen again after being asked for my login credentials.

Are there any errors in the logs?
If you do the same and use Basic auth does it work or also fails to load?

Got the logs, I’m not really able to decipher what may be issues in there though. Is there some where I can make it available if that would help?

Hastebin it.

http://hastebin.com/ulocokoyap.md

Are you accessing Sonarr through a reverse proxy?

I see this error in the logs with Sonarr failing to connect to SAB:
16-9-12 21:57:39.9|Warn|HttpClient|HTTP Error - Res: [GET] http://192.168.0.101:8888/api?mode=get_config&apikey=(removed)&output=json: 504.GatewayTimeout

Followed by the contents of a web page offering suggestions on how to connect (which isn’t what I’d expect to see if SAB is offline).

Nothing else stands out as being a problem.

Don’t really know what a reverse proxy is…

My setup is an Airport Extreme that directs external traffic on specific ports to my iMac which is running things like Sonarr and SAB. I also use a dynamic IP service to easily get to my iMac from the external world.

the *.101 address is my iMac, port 8888 is SAB, it’s always running.

Probably not a reverse proxy then, but weird that your Airport Extreme is intercepting the request to SAB (or something else is).

Have you tried basic auth instead of forms auth?

Since you didn’t include the basic information we request when you opened the thread, we need:

Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS:

<a href='http://www.downforeveryoneorjustme.com/192.168.0.101'>Down for every one or just me?</a>

Lol, whoever wrote that cache deserves to be fired.

That would be glimmerblocker, by the looks of it.

I have the exact same problem but on OSX Yosemite and I also use a reverse proxy with nginx. Removing auth “fixes” it but that would leave the world to use my sonarr … Basic auth doesn’t promt anything. Just blank.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.