Unable to remotely manage SABNZBD

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
laserface
Newbie
Newbie
Posts: 3
Joined: September 5th, 2011, 7:45 am

Unable to remotely manage SABNZBD

Post by laserface »

OS: OSX 10.7.1
SABNZBD version: 0.6.8 .app
problem: I am unable to remotely access my SABNZBD server from other devices within my network. this previously worked fine on my windows installation, and can confirm that my windows installation still works fine (as my old PC now exists as a VM in VMware Fusion)

I can access sickbeard using my iMacs internal IP address from my ipad or iphone, and I have the necessary ports forwarded to do the same externally. SABNZBD does not work, no matter what device I am using, or what ports I forward.

another example is the IOS app MyNZB, which previously worked with my windows installation, however switching to mac (and retaining the same IP address and forwarding rules) I cannot connect.

What I have tried so far:
Disabled API
with/without HTTPS
with/without username and password
using alternative default ports (8081, as i know communication works on this port thanks to sickbeard)
internal/external connection
Enable/disable OSX firewall


Currently, my VM PC running 0.6.8 on Win7 x64 cannot see the OSX installation running on the IP of the iMac. the iMac can see the PC installation on the VMs IP. This leads me to believe there is an issue with the OSX version of the SABNZBD application which has existed since at least the previous version before 0.6.8 (only bought my mac a month before 0.6.8)


Short version: no other device of any kind can access SABNZBD running on my iMac, however a windows VM on the same iMac is accessible everywhere.
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Unable to remotely manage SABNZBD

Post by shypike »

Which host address did you use?
"localhost" isn't going to work for external access.
Your best bet is using 0.0.0.0
laserface
Newbie
Newbie
Posts: 3
Joined: September 5th, 2011, 7:45 am

Re: Unable to remotely manage SABNZBD

Post by laserface »

my set up is as follows

Imac: x.x.x.19
VM: x.x.x.11

both with identical configuration pages (disabled API, localhost as SAB host, no name/password required)

the VM is on the imac and you can access it via ipad.
you cannot access the imac via anything.

tried what you suggested, and gave the imac SAB the full host IP (x.x.x.19) and no luck.

sickbeard works with localhost:8081 set, so in theory, so should SAB.
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Unable to remotely manage SABNZBD

Post by shypike »

It's your VMWare that screws things up.
I had the same issue.
VMWare essentially confiscates the .local space and makes OSX start lying about its true IP address.
Does your Bonjour still work?
In the end I had to remove VMWare's NAT adapter and use only "bridged".
sickbeard works with localhost:8081 set, so in theory, so should SAB.
Nonsense, when SickBeard uses localhost it's not externally accessible (unless they have a huge bug).
laserface
Newbie
Newbie
Posts: 3
Joined: September 5th, 2011, 7:45 am

Re: Unable to remotely manage SABNZBD

Post by laserface »

VMware isnt running 99% of the time, its purely there for testing and windows apps that i still need to use occasionally, so its not the cause.

Sickbeard is currently accessible on the iMac via localhost:8081. of course that doesnt work externally (however with forwarding to my external IP it DOES work).

ive run a port scan on my external IP and its got 8080 and 8081 open. just getting this working locally for now is all i am really concerned with, but I guess once that is done the external access will come naturally.


EDIT:
miraculously, its now working normally internally and externally. nothing has changed. wtf?
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Unable to remotely manage SABNZBD

Post by shypike »

It makes no differnence whether VMWare runs or not.
It installs a number of permanent virtual network interfaces that make
OSX forget what its true IP address is.
The default network interface changes from your physical network interface
to one of the virtual ones and those aren't visible to the outside world.
Post Reply