Unable to access computer remotely after update
Posted: August 3rd, 2017, 5:49 pm
Version: 2.1.0 [443efb5]
OS: Windows 10 Pro
Install-type: Windows Installer
Skin (if applicable): Glitter - Night
Firewall Software: None
Are you using IPV6? not sure, all my computers have IPV6 addresses but personally I still use IPV4 and that's how everything is set up.
Is the issue reproducible? yes
Problem started a couple weeks ago after I upgraded to current version. Not sure what prior version was but I don't think it was pre-2.0
I can no longer access the web interface from other computers on my network when previously I could. I'm still able to access CouchPotato (:5050) and Sickbeard (:8081) on that computer from other computers, and everything else like Plex, remote desktop, teamviewer, etc. No connectivity issues except Sabnzbd all of the sudden. No firewall software on any of the machines and Windows firewall is off.
On the machine Sabnzbd is running on, I can access the web interface through http://127.0.0.1:8080/sabnzbd/ and http://localhost:8080/sabnzbd/ . I can not access it even on the local machine from http://[computername]:8080/sabnzbd/ or http://[networkIP4address]:8080/sabnzbd/, when I'm pretty sure I was able to in the past.
I previously didn't have any authentication in my general settings at all, but I tried setting a username and password and in the "External internet access" dropdown I selected "Full Web Interface - only external access requires login" but that didn't do anything for me.
So, any idea why I can't access Sabnzbd from other computers on my network anymore?
Oh, forgot to mention, a portscan shows open ports on 5050 (CouchPotato) and 8081 (Sickbeard) but not 8080, which Sabnzbd is running on.
OS: Windows 10 Pro
Install-type: Windows Installer
Skin (if applicable): Glitter - Night
Firewall Software: None
Are you using IPV6? not sure, all my computers have IPV6 addresses but personally I still use IPV4 and that's how everything is set up.
Is the issue reproducible? yes
Problem started a couple weeks ago after I upgraded to current version. Not sure what prior version was but I don't think it was pre-2.0
I can no longer access the web interface from other computers on my network when previously I could. I'm still able to access CouchPotato (:5050) and Sickbeard (:8081) on that computer from other computers, and everything else like Plex, remote desktop, teamviewer, etc. No connectivity issues except Sabnzbd all of the sudden. No firewall software on any of the machines and Windows firewall is off.
On the machine Sabnzbd is running on, I can access the web interface through http://127.0.0.1:8080/sabnzbd/ and http://localhost:8080/sabnzbd/ . I can not access it even on the local machine from http://[computername]:8080/sabnzbd/ or http://[networkIP4address]:8080/sabnzbd/, when I'm pretty sure I was able to in the past.
I previously didn't have any authentication in my general settings at all, but I tried setting a username and password and in the "External internet access" dropdown I selected "Full Web Interface - only external access requires login" but that didn't do anything for me.
So, any idea why I can't access Sabnzbd from other computers on my network anymore?
Oh, forgot to mention, a portscan shows open ports on 5050 (CouchPotato) and 8081 (Sickbeard) but not 8080, which Sabnzbd is running on.