I am getting connection refused when trying to go to 127.0.0.1:8989 and 192.168.0.31:8989 but not on localhost:8989. This is on WIndows. I really don’t get it. Anyone else?
Binding is set to *
I don’t see anything in the logs. http://hastebin.com/juvizomudi.tex
Edit: oh ya, sab, plex and CP all work fine.
Are you running as a service, or nzbdrone.exe directly?
So typically what is recommended is for you to check your Firewall settings. If you run NzbDrone.exe as administrator, it should create the necessary rules to allow this.
I have also a similar post right now where I’ve tried everything I can think of to access anywhere but localhost with no luck. Curious to see what others recommend.
Thirrian, what would this affect?
Tried it both ways. I finally found something worked.
Don’t ask me why, cause it makes no sense since other apps were working.
By default Sonarr only listens on localhost running it once as administrator (or running as a service) should register Sonarr to listen on *:8989 (all IPs, port 8989), essentially we’re running the same netsh command, but to all IPs to avoid future issues.
I figured, cause it was working in the past. Somehow it got borked. I think it may have been from WTServer Stack I installed. Anyway, at least it’s working again.
It’s interesting that you mention you recently installed WTServer Stack. I also did this and was having the exact same problems as you.
Adding 127.0.0.1 and 192.168.1.5 (in my case) via netsh http add iplisten fixed all of my problems!
markus101, do you have any context what that command does and why it was causing us problems? Thank you Krunch for figuring this out…I spent the last two days trying to figure this out so I could make my Sonarr available via my domain. It’s working now!
I misspoke before, its not the same command Sonarr runs, the command we run registers a specific port, this registers the entire IP address to be able to listen at all.
https://msdn.microsoft.com/en-us/library/windows/desktop/cc307219(v=vs.85).aspx
Sonarr relies on the HTTP Service for its web server and it sounds like WTServer Stack affects that somehow, might be worthwhile to ask them about it.
Good find @KrunchMuffin
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.