SABnzbd Forums

I never really had any problems, but since the last update to latest version SABnzbd doesn't start at all, giving me the following message:

Cannot connect

Chrome can't establish a connection to the server at 127.0.0.1:8080.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
You can then click on a 'Try Again' button, but it has little effect.

I have 2 desktops and it still worked on one of them, but not on the other. I then changed the port on the one that was still working to see if that would help with the one that wasn't working. Unfortunately, now I can't access the one that was working either :-S

Reinstalling didn't help, completely removed the program, deleted the folder, but to no avail :-(

I also turned off the antivirus, firewall, and VPN, but it still doesn't respond :-S

Anyone have any ideas?

Do you (re)cognize this problem and -more importantly- do you have a solution for it?

I am running Windows 11

Can you remove SABnzbd and delete the sabnzbd.ini (use the Delete settings in the uninstaller).
Seems it's some port issue.
VPN could definitely be a problem.

I'm receiving this too today:
"unable to bind to port 8080 on 127.0.0.1"
Windows 11, via Chrome.
Was running 4.3.1 and tried upgrading to 4.3.2 to no avail.
http://localhost:8080/sabnzbd/ just spins at 'loading'.
No VPN.

Firewall and/or Virusscanner!

No firewall and using Avast and malware bytes. Pretty minimal.
Are you saying the virus scanner may be the culprit? And if so, what steps will resolv?

No firewall? Oh.
Virusscanner ... disable it?

What might also help:

On Windows, open CMD
go to C:\proram files\sabnzbd

from there, run "sabnzbd-console.exe"

Post the last output on pastebin.com, and post url here.

Thanks for the quick replies.
Disabling AV is not something any Windows users should imo, do, but I tried running the console via command line and it wouldn't do anything.
I fully uninstalled it, rebooted and reinstalled 4.3.2 and it's working again.
Not sure what happened here.

Reboot is always good on Windows!