Since 2.2.1 update, can't access remotely

dbinott · Post by **dbinott** » August 28th, 2017, 7:22 pm

Can't access web gui or add nzb's. Windows10

I have the setting fully open but require login for external.

Python Version: 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)] [cp1252]
OpenSSL: OpenSSL 1.0.2j 26 Sep 2016 [TLS v1.2, TLS v1.1, TLS v1, SSL v3]

Post by **sander** » August 29th, 2017, 5:23 am

That's little info ...

Which URL do you use?
How do you know SABnzbd is running at all?

dbinott · Post by **dbinott** » August 29th, 2017, 7:24 am

i can't publicize the remote URL, but it's the same i have been using for 2 years. I know it's running cause I can remote into the box and use it and I am still getting downloads from it. Sonarr, Plex, PlexPy all still work remotely.

Post by **safihre** » August 29th, 2017, 7:28 am

So, what did you set for SABnzbd host?
Is the firewall open for the ports?

Nothing changed in 2.2.1 with regards to these things, so it might just have coincided with other system updates/changes.

dbinott · Post by **dbinott** » August 29th, 2017, 7:41 am

crap i do recall something in the log about needing pyopenssl, so installed it. just uninstalled and rebooted. still no access. damn it. should I reinstall python?

Post by **safihre** » August 29th, 2017, 7:54 am

No, pyopenssl has not been required since 1.2.0, so more than a year ago.

First answer our questions we can help you:

What page do you get when you try to connect? No page at all, or 'Access denied'?
What do you have set for SABnzbd host on Config > General? Is it set to 0.0.0.0 (the value it should be to allow external access)?

dbinott · Post by **dbinott** » August 29th, 2017, 7:56 am

Ya, that log msg was from CP not sab.

1. Error is ERR_CONNECTION_TIMED_OUT
2. Yes it is 0.0.0.0 port 8085

Post by **safihre** » August 29th, 2017, 8:14 am

And when you are in the network with that computer, can you access it then?

dbinott · Post by **dbinott** » August 29th, 2017, 8:19 am

yes that is correct.

Post by **safihre** » August 29th, 2017, 8:22 am

So then it is not SABnzbd, because if you can access it from within the network, then SABnzbd is allowing connections from outside. Some other things are blocking the port.

dbinott · Post by **dbinott** » August 29th, 2017, 8:30 am

All apps are using port 80 and I use nginx to forward. That hasn't changed.

I even turned windows firewall off to test.

Post by **safihre** » August 29th, 2017, 8:37 am

What version of SABnzbd were you previously using? You can always re-install it again https://sabnzbd.org/download-stats and see if that solves the problem?

dbinott · Post by **dbinott** » August 29th, 2017, 8:41 am

thanks for the kick in the ass. somehow the box IP became dynamic when it was static.

Post by **safihre** » August 29th, 2017, 8:47 am

Good to hear it's fixed!

Support Forum

Since 2.2.1 update, can't access remotely

Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely

Re: Since 2.2.1 update, can't access remotely