Page 1 of 1

sabnzbd won't start

Posted: April 1st, 2009, 1:11 pm
by nostringsattached
I have a problem that is very common with sabnzbd. That is that it won't start. I have tried to uninstall and reinstall. I have tried several things suggested in this forum and even tried to change the ini file. When I start in save mode I see that my localserver is occupied. But even after I change the ini into another port it won't start.
And all of the above has suddenly began and before sab worked fine..
Help please! ???

Versio 0.4.8 Standard skin
OS Windows XPpro

Re: sabnzbd won't start

Posted: April 1st, 2009, 9:28 pm
by switch
Try, start>run

Code: Select all

"C:\Program Files\SABnzbd\SABnzbd.exe" -s :8085 -b1

Re: sabnzbd won't start

Posted: April 2nd, 2009, 12:29 pm
by nostringsattached
Windows firewall blocked sabnzbd. I fixed that problem..and still
It won't start...

In save mode it says..

HTTP info port 8080 not free on cp....
error failed to start web interface
warning cannot launch the browser probably not found..

Any suggestions now.. ???

Re: sabnzbd won't start

Posted: April 2nd, 2009, 12:44 pm
by switch
Did you try what I posted? If so it would be saying port 8085 not 8080

Re: sabnzbd won't start

Posted: April 2nd, 2009, 12:54 pm
by nostringsattached
yes sir I did..
finger error...
But even when I disable the firewall it won't work..

Re: sabnzbd won't start

Posted: April 2nd, 2009, 4:39 pm
by shypike
nostringsattached wrote: finger error...
What's that?

Re: sabnzbd won't start

Posted: December 17th, 2009, 10:46 pm
by mwills
i'm having the same issue.  i just installed the latest 4.12 version (first time user):

-restarted
-added SABnzbd to the allowed programs in windows firewall
-i have tried to disable firewall completely
-i tried the above which i assume changes the port to 8085
-safe mode does not work either

nothing happens when i try to start the application.  any advice??

Version: 4.12
OS: Windows 7 Ultimate 32
Install-type: Windows installer
Skin: none
Firewall Software: Windows, does AVG 9.0 block anything?  i don't think it does.
Are you using IPV6? no
Is the issue reproducible? yes, it has never worked

Re: sabnzbd won't start

Posted: December 18th, 2009, 12:05 am
by mwills
installed the beta version and it started up just fine. 

ReNEWED!: sabnzbd STILL won't start...

Posted: May 16th, 2013, 1:10 am
by willow6124
I am having the same problem with the new version 0.7.11. I updated recently, but it has been working with the update.
I have done nothing to my knowledge to alter anything recently.

our error code:
"SABnzbd needs a free tcp/ip port for its internal web server.
Port 8090 on 192.168.1.8 was tried , but it is not available.
Some other software uses the port or SABnzbd is already running.

Please restart SABnzbd with a different port number.

Press Startkey+R and type the line (example):
"C:\Program Files (x86)\SABnzbd\SABnzbd-console.exe" --server 192.168.1.8:8091

If you get this error message again, please try a different number.

Program did not start!"

--> as you can see the recommendation for change is not the default port 8080, as I have tried all the ports between the two.
SabNZBd 0.7.11 is on the list of allowed programs in windows fire wall. For arguments sake, I have entirely disabled windows firewall (I have a very good firewall on my internet line in so no real concern there),

I can start in safe mode, as well as "localhost" and "0.0.0.0" also seems to be running stably, however, I need to be able to remote connect in as I have it running on a headless server.
any suggestions or troubleshooting techniques would be helpful.

Thank you!

Re: ReNEWED!: sabnzbd STILL won't start...

Posted: May 16th, 2013, 10:31 am
by sander
willow6124 wrote: I can start in safe mode, as well as "localhost" and "0.0.0.0" also seems to be running stably, however, I need to be able to remote connect in as I have it running on a headless server.
... so use "0.0.0.0" and you should be fine.

Re: sabnzbd won't start

Posted: May 18th, 2013, 11:46 am
by willow6124
I was thinking the same thing but at the time, 0.0.0.0 wasn't working for network remote access. I had everything programmed to have sab on 192.168.1.8:8080.

So after hours of tweaking every setting I could think of I finally started up my network diagnostics and noticed it was putting all traffic on 192.168.1.7. ---> I had at some point plugged the network cable into the wrong port (I have dual NICs with IP assignments: ...8 and ...7.

Felt like a moron, but wasn't getting any diagnostic info back to that effect from sab, so hopefully my idiocy is helpful to someone.
IE: check your network cables before you go freaking out.