Page 1 of 1

Cannot connect to web interface

Posted: September 15th, 2012, 3:43 pm
by rustafur
Hello,

I'm just installed the latest version of SAB from your PPA, on a new headless 12.04.1 Server box. And I cannot get connected to the web interface. When I try to access 192.168.0.111:8080/sabnzbd I get a "web page unavailable, connection interrupted" error.

Here's what I've tried so far.

- Killed the firewall on my WIN7 desktop (running avast)
- Opened iptables to accept all connections (iptables -P INPUT ACCEPT, iptables -P OUTPUT ACCEPT, iptables -P FORWARD ACCEPT, iptables -F)
- Different web browsers
- Checked running services (service --status-all) to make sure SAB was running.
- Uninstalling/re-installing SAB

Thanks in advance!

Re: Cannot connect to web interface

Posted: September 15th, 2012, 4:38 pm
by rustafur
Okay, so, I mis-diagnosed this problem

While SAB does run as a service at startup, the program itself does not seem to. As when I try to connect to server:8085 (actual webserver port, not 8080) after the server boots, I am unable to connect. However, when I remote in with Putty, and run sabnzbdplus, I can then get to the web ui from my WIN7 desktop.

Any thoughts?

Re: Cannot connect to web interface

Posted: September 16th, 2012, 5:43 am
by sander
What is the output of:

sudo service sabnzbdplus start

Re: Cannot connect to web interface

Posted: September 16th, 2012, 6:44 am
by rustafur
sander wrote:What is the output of:

sudo service sabnzbdplus start
root@ubuntu:/home/adam# service sabnzbdplus start
* SABnzbd+ binary newsgrabber: already running (pid 1111)

Re: Cannot connect to web interface

Posted: September 16th, 2012, 6:54 am
by sander
And what's the output of

netstat -apon | grep :8085

Assuming SAB is still running on 8085

Re: Cannot connect to web interface

Posted: September 16th, 2012, 7:45 am
by rustafur
So, I think we got it running now.

I started getting frustrated, because depending on where I launched sabnzbdplus from, manually, the port would be different. If I was connected via SSH, sab would start on 8085, and if I started it from the box itself, sab would start on port 8090. So after starting manually, I went into SAB's config page, and change the port setting to 8080, then rebooted the server. Once the server was up, I verified that the sabnzbdplus service was running, and it was, so I tried accessing the web ui on port 8080, and sure enough there it was. SAB started up as a service, as intended, and I can access the web ui.

For some reason though, it seems that all my configuration settings were wiped out, as I was greeted with the Wizard page. I wonder if this is a because I was never really using the sabnzbdplus service, but a separate instance of it running by me manually starting SAB.

Still, thank you for the help and input sander, it's greatly appreciated! I'll be sure to post back here if this isn't fixed, but for now the problem seems to be resolved :)