Can't access UI with Chrome

I can get to it with IE but not with Chrome on Windows 7 64 bit. Don’t like IE but I guess I have to use it until there is a fix.

When I first install Sonarr it works well with Chrome but I think it’s when I reboot that it starts failing. Haven’t really figured that out yet. I’v been unistalling and deleting the folder then reinstalling every time it happens then it works again for a while. Today is the 4th time it happened in the last couple weeks but this time I tried IE before reinstalling and was surprised it worked.

I tried incognito too so it’s not an extension causing it.

Anyone else have this happening?

I pretty much only use Chrome with Sonarr (occasionally I use Firefox to test something) and I don’t have any issues with it.

What issue are you having with it?

Even i seem to be facing the same issue. When i access sonarr on IE and then on chrome it magically works. So either it’s a system error or some co-incidence that is happening.

The page just says “This webpage is not available”

Is Sonarr running when you get the error?
Anything in the Sonarr logs?
What OS is Sonarr running on?

Sonarr is running. I’m using windows as the host machine. It’s the latest version in master. I use teamviewer and connect to my server and open it on the web browser there. After which it works on my machine. The same thing happens if i don’t access the UI for a long time. Utorrent completes downloads, new ones are added and processed. So, i’m fairly sure Sonarr is working properly. It just seems to be the issue with the UI access.

Sonarr is running.
Nothing in the Sonarr logs or Windows Event logs.
Running on Windows 7 64 bit.

I can always open it in IE when it fails on Chrome. If I re-install I will be able to open it in Chrome again for a while.

Sonarr installed itself to use port 563 which Chrome doesn’t like for some reason. It’s weird because SABnzb is using port 568 with no problem.

I changed the port for Sonarr to 8989 and now it’s working fine with Chrome.

The only port Sonarr would set is 8989, which it does once on the first start.

If Sonarr’s port is changed to 563 (which is secure a newsgroup port) its because something auto-filled it to that port (likely saved from when SAB was setup) and the settings were saved.

If you go to Settings -> General you may find that it gets reset back to 563, its not something Sonarr is doing though.