I have Sonarr setup and configured just fine. I can access it via localhost on the computer that hosts it, and also via the 192.168.1.5 LAN IP. If I try to access it on a different computer on the network/LAN I will get an ERR_CONNECTION_TIMED_OUT.
I’ve been reading about this all day and haven’t had any success. I’ve tried starting Sonarr as administrator to ensure the firewall rule is added (as suggested in the Installation wiki). I’ve even went so far as to add my own and verified that it was for the right profile. I also tried to disable the firewall completely and didn’t have any success (tried to disable and also just tried to leave it on but enable all inbound connections).
I don’t think my router has any firewall enabled. It’s a Nighthawk r7000 netgear router.
The firewall rule Sonarr creates only affects the private profile, if your connection is set to public or domain (less likely its domain), then its not opened up.
Your router has a firewall of sorts protecting you from connections being opened from the internet to a computer on your system, but it would block communication on your network.
Yeah, I double checked that my network connection was set to private. Can you tell me what the rule should look like so I can verify it? Should both remote and local port be set to 8989?
Interesting. Well, my inbound firewall rule is setup for NzbDrone.exe and the local port is 8989 and remote is all ports. Still no gravy.
I can’t think of what else on my system might be preventing access. What baffles me is that disabling the firewall itself doesn’t allow access, so I am thinking it has to be something else. Also, to verify, I checked the firewall logs and I don’t see anything about traffic on Port 8989 being blocked.
Do you know of any other culprits that might be blocking it? The only other software used is Microsoft Security Essentials, as far as I know. Perhaps I will try to disable that and see if it is allowed through.
Ultimately, for now, I can just remote into my PC to get access to Sonarr both remotely and over the network, but I’d like to eventually point it to my domain once I figure out how to make it accessible on my LAN.
The only other thing would be to verify that Sonarr is listening on *:8989, which is shown in the logs when Sonarr is starting up. Any other firewall could block it, but besides that I’m not sure.
Ok, fair enough. I’ve verified it’s listening on *:8989. Next step I will try to go through and disable any programs which look like they might be interfering. I am wondering if for some reason there’s another program using the port and that’s the problem, although I’ve tried a variety of ports with no luck.
Posting so that any others who search and find this thread may get the answer.
I had recently installed WTServer Stack and for some reason it messed with the settings through netsh. To get Sonarr to work over the network (and remotely), I had to run: