Page 2 of 2

Re: Startup error on OSX

Posted: June 18th, 2012, 6:01 pm
by renegade
Same issue here, 0.7.0 wont launch on OS X 10.7.4

editing the .ini to 127.0.0.1 (also ::1) will allow launch and will allow it to work, but I cannot access the web gui using my IP, nor can I access sab externally using my IP. Using localhost:8080 works in browser (safari), but using a ssl connection no longer works, and again cannot connect via external IP any longer.

Downgrading to previous version brings back full functionality.

Re: Startup error on OSX

Posted: June 19th, 2012, 1:33 am
by ghostcorps
I have just updated to 7.0 on my FreeBSD 8.2 machine and am getting the same issue.

By using 'host = ::1' in the config I can start SABnzbd and access it locally, but I can not get remote access, which since my server is headless it is pretty much useless at the moment.

My hosts file is as basic as it gets:

Code: Select all

::1                         localhost
127.0.0.1               localhost
I am assuming there is some basic networking thing I don't know?


[EDIT:] I just added this line to my sabnzbd.ini and it works :)

Code: Select all

LOCAL.IP.ADDRESS             EXTERNAL.IP.ADDRESS

Re: Startup error on OSX

Posted: June 19th, 2012, 2:37 am
by shypike
ghostcorps wrote: [EDIT:] I just added this line to my sabnzbd.ini and it works :)

Code: Select all

LOCAL.IP.ADDRESS             EXTERNAL.IP.ADDRESS
I assume you changed this in /etc/hosts.
What exactly did you change?
There's a bug in SABnzbd where it cannot handle that "uname -n" doesn't give a resolvable name.

Re: Startup error on OSX

Posted: June 19th, 2012, 3:06 am
by ghostcorps
shypike wrote:
ghostcorps wrote: [EDIT:] I just added this line to my sabnzbd.ini and it works :)

Code: Select all

LOCAL.IP.ADDRESS             EXTERNAL.IP.ADDRESS
I assume you changed this in /etc/hosts.

Thanks Shypike, I just came back cos I had a sinking feeling I said sabnzbd.ini not /etc/hosts! :-[

Sorry, I was pretty busy at the time. I won't fix the post now cos that would be confusing. Or should I?


My sabnzbd.ini host entry is actually my home URL, but I assume the external IP would work just as well.

Code: Select all

host = my.domain.com
/etc/hosts file looks exactly like this:

Code: Select all

::1                   localhost
127.0.0.1             localhost
192.168.0.2           my.domain.com

Re: Startup error on OSX

Posted: June 19th, 2012, 4:58 am
by shypike
It's clear to me now.

Re: Startup error on OSX

Posted: July 12th, 2012, 9:44 am
by bunhead
@shypike
No I do not run VMWare Fusion or any other virtualization software on this machine as it is my headless server.

I cannot ping the resulting name from the uname -n command, however I can ping localhost. Hmmm I will have to look into that when I get some time later on.

Re: Startup error on OSX

Posted: July 17th, 2012, 9:00 pm
by Jazradel
uname -n returns earth.local (earth is my hostname).

My hosts file already has all the localhost entries. bunheads solution allowed sabnzbd to start with 0.0.0.0 as the host, but I now can not access it from an external address.

I do not have VMWare Fusion.

Re: Help With Categories

Posted: July 18th, 2012, 12:11 am
by shypike
Wait half a day until release 0.7.2 is released.

Re: Startup error on OSX

Posted: August 6th, 2012, 8:47 pm
by Jazradel
I've upgraded to 0.7.3 and still can't access it externally. I can access transmission running on the same computer. That's the only computer on the network, sabnzbd and transmission are basically the only things that computer is used for, and AFAIK I haven't changed any settings. It was working with 0.6.9.

Re: Startup error on OSX

Posted: August 7th, 2012, 12:45 am
by shypike
Instead of 0.0.0.0, try the numerical IP of your system.
And tell your router not to change that anymore.

Re: Startup error on OSX

Posted: August 8th, 2012, 6:08 pm
by Jazradel
Changed the IP, still can't connect. I also tried setting up a domain name and using that.

Edit: I think my ISP may actually be to blame for this.

Edit2: Yep, ISP decided to implement filtering on a couple of ports, including 8080. It's all working now.