Web interface becomes unavailable remotely.

[BoomSchtick]

I'm currently running 0.7.11 on Windows Home Server 2011.

Everything is fine and I can access SAB locally (from the server and from the lan with a 10.x.x.x IP) or remotely (from the internet) via port forwarding on my router. Also my Chrome Plugin can hit SAB without a problem.

For some reason, after a day or two, I can no longer hit SAB remotely (over the internet). The connection will just time out trying to get a response back from SAB on port 9090 (https). The only way I can access SAB once this happens is to RDP into my server. I can hit SAB from the server via localhost or via it's IP address. If I restart the SAB service, then all accessibility is returned as it was the previous day.

At first glance it seems like a firewall issue, but I do not believe that is the case. The application becomes unavailable without changing ANY settings on the firewall, and they become available by just bouncing the SAB service. That tells me that there is something wrong with SAB or the web server that it uses.

I have tried 0.7.7 - 0.7.11 and I get the same results on all of them eventually.

I previously ran SAB on Linux and never had any of these issues, but the interaction with Windows was poor, so I switched.

I would love some suggestions on how to resolve this major annoyance.

Thanks!

[dtrobson099]

Are you downloading at 100% of your bandwidth? Your internet connection could be maxed out by SAB and the requests you're making from outside could be timing out. On the LAN that wouldn't pose a problem since you likely have plenty of bandwidth inside your LAN. If you throttle your connection by say, 100kB/s, does that make any difference?

[BoomSchtick]

I'm not downloading at 100%. When I have SAB rocking at 3.5 MB/sec it turns everything else to crap (web, SIP, etc). I have my QOS settings such that SAB is not allowed to take up everything all at once.

[sander]

For some reason, after a day or two, I can no longer hit SAB remotely (over the internet). The connection will just time out trying to get a response back from SAB on port 9090 (https). The only way I can access SAB once this happens is to RDP into my server. I can hit SAB from the server via localhost or via it's IP address. If I restart the SAB service, then all accessibility is returned as it was the previous day.

When the problem occurs, can you still access SAB remotely from your LAN?

[BoomSchtick]

For some reason, after a day or two, I can no longer hit SAB remotely (over the internet). The connection will just time out trying to get a response back from SAB on port 9090 (https). The only way I can access SAB once this happens is to RDP into my server. I can hit SAB from the server via localhost or via it's IP address. If I restart the SAB service, then all accessibility is returned as it was the previous day.

When the problem occurs, can you still access SAB remotely from your LAN?

I can not... not by ip or hostname. It is doing it right now as I type this.

Local access to the server only via localhost or IP. The dyndns does not work locally, as would be expected under the circumstances.

Sickbeard (also hosted on that server) can even send NZB's to SAB when it is doing this (via API), but I can't send NZB's from the LAN to SAB when it's in this state.

I just tried a ipconfig /release and /renew and it had no effect on the issue.

[sander]

Do you use HTTPS to access SAB?

Do you use a SAB plugin in your webbrowser?

At the moment SABnzbd is unaccessible from the LAN, can login on the Windows system, and type:

Code: Select all

netstat -aon | find "8080"
netstat -aon | find "9090"

... with "8080" and "9090" the ports is using; change accordingly

[BoomSchtick]

Do you use HTTPS to access SAB?

Do you use a SAB plugin in your webbrowser?

At the moment SABnzbd is unaccessible from the LAN, can login on the Windows system, and type:

Code: Select all

netstat -aon | find "8080"
netstat -aon | find "9090"

... with "8080" and "9090" the ports is using; change accordingly

I have tried both http and https with the same result.

I do use the SAB plugin. It works great when I can hit the interface, it does not work at all when I can not.

When I do netstat on port 9090 I get almost 8000 results. Most of the results can be seen here (along with the 8080 results):

http://pastebin.com/Yr9g6MQs

I had to trim some of it down so that pastebin would let me post it.

[sander]

Is it SABconnect+?

If so: it's a well known problem between SABconnect++ and SABnzbd. Not clear who's fault it is. The problem has been there for a few years now.

From the back of my head: only happens with HTTPS.

Workarounds:
- do not use sabconnect. Or
- let sabconnect use HTTP, not HTTPS. Or
- restart SABnzbd each few hours

Somewhere on this forum there might be more precise info.

EDIT:

Oh, I had already described it in the SAB FAQ: http://wiki.sabnzbd.org/faq#toc33

[BoomSchtick]

Is it SABconnect+?

If so: it's a well known problem between SABconnect++ and SABnzbd. Not clear who's fault it is. The problem has been there for a few years now.

From the back of my head: only happens with HTTPS.

Workarounds:
- do not use sabconnect. Or
- let sabconnect use HTTP, not HTTPS. Or
- restart SABnzbd each few hours

Somewhere on this forum there might be more precise info.

EDIT:

Oh, I had already described it in the SAB FAQ: http://wiki.sabnzbd.org/faq#toc33

Awesome! I'll try that. Is there a chrome plugin that behaves better?

[genocidejim]

Don't know if this will help, but I just solved my own issue with not being able to connect to Sabnzbd via LAN.
Turns out that my trial version of Norton Internet securities ran out and it kicked me back to using the old windows firewall which was set to 'PUBLIC'. Changed it back to home and it instantly fixed my problem.