Can't access web interface from anywhere except the PC Sonarr is running on

[contact411]

I’m having a strange issue that appears to be directly related to Sonarr. I have no issue accessing the web admin page using localhost or the static IP address while on the host PC (Window 8.1).

When attempting to access the web interface from another PC within my local network I receive a “ERR_CONNECTION_TIMED_OUT” only for attempting to access Sonarr. All of my other web admin pages are accessible without a problem (Plex, CouchPotato, SabNZBD). I’ve attempted changing the port Sonarr is using to the port I was using successfully for SickBeard but still receive the same timeout.

Any thoughts on what might be causing this issue? I’m fairly certain it isn’t a issue within the router but am open to any suggestions.

Thanks!

[slug]

Make sure the listen address is not 127.0.0.1. It should be set to your Internal IP address or maybe 0.0.0.0 might work

[trrohith]

You can use the listen address as the asterisk key (*). Also make sure you start sonarr as admin once to enable it to get the authorization. After that i don’t think there should be any issues.

[markus101]

Make sure you ran Sonarr as admin at least once to register it properly with Windows.

Check the Windows firewall as well, depending on the profile the port won’t be opened automatically.

[Alex240188]

Also having this same issue.
I have always used sickbeard and wanted to give Sonarr a try.
Installed onto a Windows Server 2008 R2 machine.
I first just installed as a service but have also tried installing normally and running as admin.
The symptoms are exactly as contact411 has described.
Launching the Icon it will load up localhost:8989 which works fine
127.0.0.1:8989 works fine
192.168.1.60:8989 works fine
so all address variants work fine on the local machine

If i switch to another machine and use 192.168.1.60:8989 it just times out.
accessing another app running on the same server works fine 192.168.1.60:8585

Just managed to get this working now.
I removed the inbound firewall rule automatically created by Sonarr and manually setup my own rule allowing the port that i will be choosing.
After doing this the remote machine connected straight away.
So hopefully this will be useful to you contact411

[contact411]

Alex240188 nailed it… I thought I had the firewall disabled but clearly was incorrect.

I updated the firewall rules in Windows 8 to include Public IP addresses and all is happy in the world again.

Thanks to everyone for their ideas and suggestions!!

[arrowheadpro]

Alex240188, thank you so much, I had the same problem and your solution was the exact answer I was looking for.

One bit of clarification tho in case it helps anyone else:
When I checked MY firewall, I saw that there were 4 NZBdrone inbound firewall rules.
Altering, modifying, disabling, (whatever-ing) the current rules did not fix my problem, I had to create a new inbound rule.

After doing so and setting the rule to listen to sonarr’s specified port, all is well and working!