Page 1 of 1
Server R2 TCP Port Error (In Use)
Posted: April 4th, 2010, 8:17 am
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
Re: Server R2 TCP Port Error (In Use)
Posted: April 4th, 2010, 11:05 am
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).
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 4:28 am
by Nick123
Figured It out it was because I set to use HTTPS and the port was in use, changing HTTPS port worked.
Thanks
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 5:48 am
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.
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 7:08 am
by shypike
We're already at war with some virus scanners / firewalls.
I think that such a solution would invoke even more nasty behavior.
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 11:40 am
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?
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 11:53 am
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.
Re: Server R2 TCP Port Error (In Use)
Posted: April 5th, 2010, 3:29 pm
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
