Page 1 of 1
Login woes
Posted: May 23rd, 2011, 2:22 pm
by dudemann
So I have been using sabnzbd on my macbook for a while now with no problems, but I have always used the 'simple' skin. When I updated to .6.1 I thought I would go back to that skin and so I changed it and pressed restart. When I tried to log back in it asked for a password but I don't have a password set so I left it blank, this didn't work so I just pressed cancel. Well now I seem to be locked out of the user interface, it says "page not found, or can't connect to localhost... etc" I tried to uninstall and went to library/application support/sabnzbd and deleting the folder, but it still won't play nice with any internet browser. Any help would be greatly appreciated.
Re: Login woes
Posted: May 23rd, 2011, 3:28 pm
by shypike
Is the program running at all?
Do you see the down-arrow in the top menu bar and does it provide a pull-down menu?
If you remove ~/library/application support/sabnzbd folder the Wizard should
come up when you start up SABnzbd.
Re: Login woes
Posted: May 24th, 2011, 12:19 pm
by dudemann
I deleted the file and sabnzbd turns on but is unable to connect to my newreader provider. The queue can be added to, but nothing downloads and because I can't view the graphical interface I can't remove anything. If I click on "queue" or "history" it just pulls up a screen which looks like this:
Re: Login woes
Posted: May 24th, 2011, 1:13 pm
by shypike
Does any other browser work?
Chrome is a bit notorious due to it's intermittent IPV6 support on OSX/
Re: Login woes
Posted: May 24th, 2011, 11:00 pm
by dudemann
Oh yeah I forgot to mention that, unfortunately firefox and safari are both giving me similar error messages. I don't know if this is helpful, but for some reason, when I turned on sabnzbd today it looked as though it was connecting, showed a download speed of ~2.8 MB/s calculated a download time, and then completely froze. Is there anywhere else it would save settings besides the folder in application support?
Re: Login woes
Posted: May 25th, 2011, 12:19 am
by sander
dudemann wrote:
I deleted the file and sabnzbd turns on but is unable to connect to my newreader provider. The queue can be added to, but nothing downloads and because I can't view the graphical interface I can't remove anything. If I click on "queue" or "history" it just pulls up a screen which looks like this:
Your screendump says you're trying to connect your webbrowser to
http://news.supernews.com:119/sabnzbd/
That is VERY, VERY wrong.
You should use
http://localhost:8080/
Re: Login woes
Posted: May 25th, 2011, 7:52 am
by dudemann
That's where is takes me when I select "queue" or "history" from the drop-down menu in the menu bar, but I also tried
http://localhost:8080/, with the same result
Re: Login woes
Posted: May 25th, 2011, 9:01 am
by sander
dudemann wrote:
That's where is takes me when I select "queue" or "history" from the drop-down menu in the menu bar,
So, you *can* access SABnzbd, right? Via which URL? And please post a screendump again.
Re: Login woes
Posted: May 29th, 2011, 12:31 am
by dudemann
Ok so this is kinda hard to explain, but sabnzbd turns on, the icon appears in the menubar, the DL speed goes up and hit ~2.75 then the whole thing just freezes. If I go to the menubar I can click on queue or history but I can't access them in any browser
Re: Login woes
Posted: May 29th, 2011, 1:54 am
by sander
dudemann wrote:
Ok so this is kinda hard to explain, but sabnzbd turns on, the icon appears in the menubar, the DL speed goes up and hit ~2.75 then the whole thing just freezes. If I go to the menubar I can click on queue or history but I can't access them in any browser
Hmmm: again your webbrowser tries to access
http://news.supernews.com:119/sabnzbd/, which is useless. You must access SABnzbd via
http://localhost:8080/ or
http://localhost:8085/ or something like that. That means you have to find out on which port SABnzbd is running
Method 1:
Can you find the file ~/Library/Application Support/SABnzbd/sabnzbd.ini ? If so, can you open it (read-only) and find each occurrence of "port" in that file, and post it here?
Method 2:
A trial-n-error method to find the URL that SAB is listening to: try these URLs:
http://127.0.0.1:8080/
http://127.0.0.1:8085/
http://127.0.0.1:8090/
http://127.0.0.1:8095/
http://localhost:8080/
http://localhost:8085/
http://localhost:8090/
http://localhost:8095/
http://[::1]:8080/
http://[::1]:8085/
http://[::1]:8090/
http://[::1]:8095/
Access via HTTPS:
https://localhost:9090/
https://localhost:9095/
https://127.0.0.1:9090/
https://127.0.0.1:9095/
Method 3:
Another way to find the ports that are being listened to, is to use the command 'netstat' from the commandline.
I Tried Mac OS X in a VMware Virtual Machine, and here's what you should type on Mac OS X to see the ports that are being listened to:
Code: Select all
Mac-Pro:~ MacAdmin$ netstat -an | grep LISTEN
tcp4 0 0 *.8080 *.* LISTEN
tcp4 0 0 127.0.0.1.631 *.* LISTEN
tcp6 0 0 ::1.631 *.* LISTEN
Mac-Pro:~ MacAdmin$
So, in the above case, SABnzbd listening to port 8080.
I haven't a method to find which process (/ process ID) is listening to which port.
On Ubuntu/Linux "netstat -plnt" will give you the best information:
Code: Select all
sander@R540:~$ netstat -plnt
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 10764/python
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 21061/transmission-
tcp 0 0 127.0.0.1:36437 0.0.0.0:* LISTEN 9200/GoogleTalkPlug
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN -
tcp6 0 0 :::80 :::* LISTEN -
tcp6 0 0 :::51413 :::* LISTEN 21061/transmission-
tcp6 0 0 ::1:631 :::* LISTEN -
sander@R540:~$
The above tells me SABnzbd on my system is listening on port 8080, so on my system the URL is
http://localhost:8080/
Re: Login woes
Posted: May 31st, 2011, 1:42 am
by sander
With Mac OS X installed in Virtualbox on my Ubuntu, I found another method to see whether SABnzbd is running, and if so, on which port:
Code: Select all
Sander-Mac-mini:~ sander$ lsof -i | grep LISTEN
SABnzbd 113 sander 13u IPv4 0x042cbf28 0t0 TCP *:http-alt (LISTEN)
Sander-Mac-mini:~ sander$
or even better:
Code: Select all
Sander-Mac-mini:~ sander$ lsof -i | grep -i SAB
SABnzbd 113 sander 13u IPv4 0x042cbf28 0t0 TCP *:http-alt (LISTEN)
Sander-Mac-mini:~ sander$
So: SABnzbd is running, and it's listening on port "http-alt", which is port 8080. Hopefully there is a way to just see the number (8080), and no 'resolving'.
Re: Login woes
Posted: May 31st, 2011, 2:30 am
by sander
And 'lsof' is also useful on Ubuntu Linux (although a bit slow: up to 11 seconds):
Code: Select all
sander@R540:~$ time lsof -i | grep -i listen
GoogleTal 2314 sander 15u IPv4 24070 0t0 TCP localhost:53153 (LISTEN)
SABnzbd.p 4244 sander 5u IPv6 80597 0t0 TCP *:9090 (LISTEN)
SABnzbd.p 4244 sander 8u IPv6 77487 0t0 TCP *:http-alt (LISTEN)
real 0m0.909s
user 0m0.000s
sys 0m0.060s
sander@R540:~$ man lsof
sander@R540:~$
sander@R540:~$
sander@R540:~$ time lsof -i | grep -i sabnzbd
SABnzbd.p 4244 sander 5u IPv6 80597 0t0 TCP *:9090 (LISTEN)
SABnzbd.p 4244 sander 8u IPv6 77487 0t0 TCP *:http-alt (LISTEN)
SABnzbd.p 4244 sander 14u IPv4 84490 0t0 TCP R540-2.fritz.box:54222->newsreader.eweka.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 16u IPv4 84491 0t0 TCP R540-2.fritz.box:54223->newsreader.eweka.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 18u IPv4 84492 0t0 TCP R540-2.fritz.box:54213->newsreader.eweka.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 20u IPv4 84493 0t0 TCP R540-2.fritz.box:54214->newsreader.eweka.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 22u IPv4 84494 0t0 TCP R540-2.fritz.box:54215->newsreader.eweka.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 26u IPv6 80608 0t0 TCP [2001:222:1af4:6aff:fe9c:ced4]:38251->newszilla.ipv6.xs4all.nl:nntp (ESTABLISHED)
SABnzbd.p 4244 sander 28u IPv6 80609 0t0 TCP [2001:222:1af4:6aff:fe9c:ced4]:38252->newszilla.ipv6.xs4all.nl:nntp (ESTABLISHED)
real 0m11.945s
user 0m0.000s
sys 0m0.060s
sander@R540:~$ time lsof -i | grep -i sabnzbd | grep -i listen
SABnzbd.p 4244 sander 5u IPv6 80597 0t0 TCP *:9090 (LISTEN)
SABnzbd.p 4244 sander 8u IPv6 77487 0t0 TCP *:http-alt (LISTEN)
real 0m0.814s
user 0m0.030s
sys 0m0.060s
sander@R540:~$
Re: Login woes
Posted: May 31st, 2011, 2:42 am
by sander
Ah: -P is the option both on Linux and Mac OS X to 'not resolve' and see the numeric ports
Code: Select all
sander@R540:~$ lsof -i -P | grep -i listen
GoogleTal 2314 sander 15u IPv4 24070 0t0 TCP localhost:53153 (LISTEN)
SABnzbd.p 4244 sander 5u IPv6 80597 0t0 TCP *:9090 (LISTEN)
SABnzbd.p 4244 sander 8u IPv6 77487 0t0 TCP *:8080 (LISTEN)
sander@R540:~$
sander@R540:~$ lsof -i -P | grep -i listen | grep -i sabnzbd
SABnzbd.p 4244 sander 5u IPv6 80597 0t0 TCP *:9090 (LISTEN)
SABnzbd.p 4244 sander 8u IPv6 77487 0t0 TCP *:8080 (LISTEN)
sander@R540:~$
So, on both Linux and MacOSX, the above command will tell if SABnzbd is running, and if so, on which port. That's useful in a lot of questions on this forum.