Sonarr wont open, starting NZBDrone service immediatly stops

Help & Support
#1

Sonarr version (exact version): Latest on install file via website, unable to launch successfully ever
Mono version (if Sonarr is not running on Windows):
OS: Windows 10
((Debug logs)) (posted to hastebin or similar):
Description of issue: Everytime I try to open sonarr I either get localhost:8989 in my web browser unable to connect, or an error saying portinusexception: make sure it is not already running. I check, the NZBDrone service is topped and what I try to start it goes immediatly from starting back to stopped. I used netstat -p tcp -ano | findstr :8989 command and can see that nothing is using port 8989 so there shouldn’t be any issue. Any help is appreciated

#2

You’ll need to look at the ((log file)) (the path where those are found is in that link) to see why Sonarr is failing to start, if you’d like us to take a look, post them to hastebin, but without them we can’t advise what to check.

#3

http://hastebin.com/semiqoxako.tex
http://hastebin.com/isabitecad.tex
http://hastebin.com/jojibikagi.tex

Thanks!

#4

The first logs are over 2 weeks old. The other logs show Sonarr being started, but nothing past the initial message. What do you get if you run NzbDrone.Console.exe theough Windows Explorer? (The full path is in the log files).

#5

This was the result of your instructions. also not that after all the errors it seemed to be doing something, there was no input from my end between the red text what was after, The NzbDroneService still is not running

Pasted image2523Ă—950 57.6 KB

#6

Do you get the same error if you run NzbDrone.Console.exe as an admin?

#7

I do :confused: I’ve tried uninstalling and re-installing as well

#8

Have you tried changing the port in Config.xml and starting Sonarr?

#9

No, what would be an acceptable port for it?

#10

Anything above 1024 would be fine, 18989 is an easy one. Mostly looking to see if something is blocking Sonarr from using that port or any port.

#11

I fixed it thanks! I saw in the xml file it was bound to the IP address of a VPN server, maybe that was the issue, changing the port didn’t fix it so I just uninstalled, deleted that whole folder and re-installed and now it works :slight_smile:

1 Like
#12

Ahh yes, that would do it, the bind address is pretty picky and doesn’t work quite the way its expected to (or how we want it to).

#13

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