SABnzbd Forums

So that works for you. Weird.

'[Errno 64] Host is down') seems to be an OSX error message.
Some random questions:
- you have just *one* Mac, right?
- do you have "Little Snitch" or another firewall installed?

OK, issue resolved!! SABnzbd is connecting again! Hurray!

Well,... it was Little snitch, but quite a hidden one.
In my defense, I did try before disabling FW and LS. I also checked the rules of LS and everything was on "Allow" for SABnzbd. And no connection was possible with sabnzbd.
But you mentioned in your previous post "Little snitch AND *one* Mac", which got me thinking and made me unplugging the external drive with CarbonCopyClone (I thought maybe this would be equivalent to one mac) and reboot the iMac again. When I went then into Rules from LS I saw now all of a sudden 2 sets of sabnzbd connection rules, one from the external drive (which was now highlighted in red, because LS saw it as faulty or obsolete) and one from the main HD, which was not working. This rule was on "Deny outgoing connection", ....so no wonder.
But peculiar, that LS could not distinguish the sets of sabnzbd rules before unplugging the external drive, because only 1 set of rules was visible. The DENY rule was hidden (I swear).

So MAAANY thanks for your patience with the problem and your always speedy replies.
In the end it was a standard problem, which I normally am able to resolve myself. But this way I learned a lot about code lines and how to run them, Python, finding hidden .ini files in hidden folders and that often a different view on things can resolve an issue, which is basically none.

So thanks again and have a great weekend. I am very happy that I can use my favourite usenet .app again.

Best regards,
HoschMosch

Good.

I'll change my quote

To a Windows user I would say "Firewall?".

to

To a Windows and an OSX user I would say "Firewall?".

Fair enough...

hoschmosch wrote:Fair enough...

I wish SABnzbd had a built-in system to check if a firewall is 1) blocking binding SABnzbd to a port/socket and/or 2) blocking outgoing traffic.

sander wrote: I wish SABnzbd had a built-in system to check if a firewall is 1) blocking binding SABnzbd to a port/socket and/or 2) blocking outgoing traffic.

Not going to happen, there are too many firewalls.
Also, they're supposed to work transparent, so it would be very hard to determine a definitive cause.