Server R2 TCP Port Error (In Use)

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
Nick123
Newbie
Newbie
Posts: 20
Joined: April 4th, 2010, 8:14 am

Server R2 TCP Port Error (In Use)

Post by Nick123 »

Hi, Having an issue with Windows Server R2 I keep getting the "SABnzbd needs a free tcp/ip port for its internal web server." error no matter which tcp port I try. I'm using AVG firewall however I have disabled it and I still get the same error.

Any advice as to what else could be the issue.

Thanks
User avatar
switch
Moderator
Moderator
Posts: 1380
Joined: January 17th, 2008, 3:55 pm
Location: UK

Re: Server R2 TCP Port Error (In Use)

Post by switch »

Disabling firewalls usually doesn't actually disable them. Try uninstalling it, or specifying a host other than localhost

e.g.

Start->Run, enter either
"c:\program files\sabnzbd\sabnzbd.exe" -s 0.0.0.0:8085
or
"c:\program files\sabnzbd\sabnzbd.exe" -s :8085
(second one needs to be access by your local ip address instead of localhost).
Nick123
Newbie
Newbie
Posts: 20
Joined: April 4th, 2010, 8:14 am

Re: Server R2 TCP Port Error (In Use)

Post by Nick123 »

Figured It out it was because I set to use HTTPS and the port was in use, changing HTTPS port worked.

Thanks
User avatar
sander
Release Testers
Release Testers
Posts: 9070
Joined: January 22nd, 2008, 2:22 pm

Re: Server R2 TCP Port Error (In Use)

Post by sander »

switch wrote: Disabling firewalls usually doesn't actually disable them. Try uninstalling it, or specifying a host other than localhost

e.g.

Start->Run, enter either
"c:\program files\sabnzbd\sabnzbd.exe" -s 0.0.0.0:8085
or
"c:\program files\sabnzbd\sabnzbd.exe" -s :8085
(second one needs to be access by your local ip address instead of localhost).
Switch,

Would it be a good idea if SAB itself would find an unused port (after checking it's not already running)? So if 8080 is already in use, try 8081, then try 8082, etc, until a free port was found. As SAB autostarts a webbrowser, a changed port is not a problem.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Server R2 TCP Port Error (In Use)

Post by shypike »

We're already at war with some virus scanners / firewalls.
I think that such a solution would invoke even more nasty behavior.
User avatar
sander
Release Testers
Release Testers
Posts: 9070
Joined: January 22nd, 2008, 2:22 pm

Re: Server R2 TCP Port Error (In Use)

Post by sander »

shypike wrote: We're already at war with some virus scanners / firewalls.
I think that such a solution would invoke even more nasty behavior.
OK. And if 10 different ports are refused, is that a signal that a virusscanner is the problem?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
User avatar
switch
Moderator
Moderator
Posts: 1380
Joined: January 17th, 2008, 3:55 pm
Location: UK

Re: Server R2 TCP Port Error (In Use)

Post by switch »

sander wrote:
switch wrote: Disabling firewalls usually doesn't actually disable them. Try uninstalling it, or specifying a host other than localhost

e.g.

Start->Run, enter either
"c:\program files\sabnzbd\sabnzbd.exe" -s 0.0.0.0:8085
or
"c:\program files\sabnzbd\sabnzbd.exe" -s :8085
(second one needs to be access by your local ip address instead of localhost).
Switch,

Would it be a good idea if SAB itself would find an unused port (after checking it's not already running)? So if 8080 is already in use, try 8081, then try 8082, etc, until a free port was found. As SAB autostarts a webbrowser, a changed port is not a problem.




Unless it has been taken out, 0.5 should actually do that. Checks 8080, then intervals of 5 for something like 5 different port numbers.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Server R2 TCP Port Error (In Use)

Post by shypike »

switch wrote: Unless it has been taken out, 0.5 should actually do that. Checks 8080, then intervals of 5 for something like 5 different port numbers.
It's in, but it doesn't work :)
Post Reply