remote address redirects to https://localhost:9012/sabnzbd

[the block]

I'm trying to help a friend get set up with usenet and sabnzbd, and I want to basically mirror my setup where I can access it from anywhere. With my setup I've got a dyndns account setup, so I can just punch in my https://host.dyndns.org:9012 and be taken right to my sabnzbd site.

With her case, sabznbd is functional and everything, I just can't access it remotely. Everytime I try to go to the remote address, it redirects to https://localhost:9012/sabnzbd, which obviously does me no good if I'm not on the machine.

Here are my relevant settings in sabnzbd config:
SABnzbd Host: 0.0.0.0
SABnzbd Port: 8080
Enable HTTPS: Checked
HTTPS Port: 9012

She has fios, so I've forwarded the port to her IP in the fios router as follows:
Networked Computer: 192.168.1.4
Applications & Ports Forwarded: Destination Ports 9012. TCP Any -> 9012. UDP Any -> 9012.
WAN Connection Type: All Broadband Devices
Status: Active

I have TWC at home, and use a dd-wrt router, so I can't exactly mirror what I've done with my own setup, but think this should work.

Anyone have any ideas why I keep getting forwarded to localhost?

Thanks

[shypike]

It's better to use https://host.dyndns.org:9012/sabnzbd
Did you tell the software firewall on the PC to allow SABnzbd to accept incoming traffic from "the internet"?

[the block]

It's better to use https://host.dyndns.org:9012/sabnzbd
Did you tell the software firewall on the PC to allow SABnzbd to accept incoming traffic from "the internet"?

Thanks for the quick reply shypike.

Why is it better to use https://host.dyndns.org:9012/sabnzbd? (just curious)

And yes the Windows Firewall allows SABnzbd to accept incoming traffic from the internet.

[shypike]

Because versions have some incorrect backlinks, although this is more
a problem with proxies, in this case it shouldn't make a difference.
Does your ISP block specific ports?
Does your ISP block all incoming trafficv (because they have you already behind a NAT proxy of their own)?
Tell your router to respond to ping-ing and then try to ping it from outside.


Run SABnzbd from a command prompt or terminal window:
Windows:
"c:\program files\SABnzbd\sabnzbd-console.exe" -w1
or
"c:\program files (x86)\SABnzbd\sabnzbd-console.exe" -w1
The try to access it from the outside and see if any http request comes in and if so which URL it uses.

[the block]

Because versions have some incorrect backlinks, although this is more
a problem with proxies, in this case it shouldn't make a difference.
Does your ISP block specific ports?
Does your ISP block all incoming trafficv (because they have you already behind a NAT proxy of their own)?
Tell your router to respond to ping-ing and then try to ping it from outside.


Run SABnzbd from a command prompt or terminal window:
Windows:
"c:\program files\SABnzbd\sabnzbd-console.exe" -w1
or
"c:\program files (x86)\SABnzbd\sabnzbd-console.exe" -w1
The try to access it from the outside and see if any http request comes in and if so which URL it uses.

Well, it started working once I tried running it from a command prompt for whatever reason. I've since closed that, and then started the server normally, and it's still working. Really weird, but glad it's working now. Thanks for the help shypike!

[the block]

Aaaaaaaand it's back to redirecting to localhost. What would have running it in the console have done differently?

[the block]

I've flushed dns, and on the computer I'm on right now, here are my results:
Firefox - redirects to localhost
IE - works fine
Chrome - works fine

Remotely connecting to my computer at home:
Firefox - redirects to locahost
IE - works fine
Chrome - works fine

Maybe I just need to wait for firefox to straighten out and fly right? I don't know why it would be the culprit on two separate machines.

[the block]

Now on a 3rd computer (which I've never attempted to access the site from before): Firefox, IE, & Chrome are all redirected to localhost, so I guess I'm back to square one. It brings me back to my question from earlier (http://forums.sabnzbd.org/viewtopic.php ... 560#p63559), why would it have worked before while sabnzbd was started from the console, vs being started normally?

[sander]

What if you use the IP address in the URL instead of the name / "FQDN"?

If that works, the problem is in/with dyndns.org ...

[the block]

What if you use the IP address in the URL instead of the name / "FQDN"?

If that works, the problem is in/with dyndns.org ...

Also gets redirected to localhost :/

[sander]

What if you use the IP address in the URL instead of the name / "FQDN"?

If that works, the problem is in/with dyndns.org ...

Also gets redirected to localhost :/

Hmmm. Does it also happen when you use a smartphone's web browser?

[bigblip]

I have this exact problem - sab running on my Linux server at home.

Smartphone access works perfectly, laptop redirects to localhost.

[the block]

What if you use the IP address in the URL instead of the name / "FQDN"?

If that works, the problem is in/with dyndns.org ...

Also gets redirected to localhost :/

Hmmm. Does it also happen when you use a smartphone's web browser?

On my smartphone I get webpage not available. In a browser on the computer, it still get's redirected to https://localhost:9012/sabnzbd

[sander]

Does it only happen with HTTPS, or also with HTTP?

I'm out of ideas and I would suggest to run from the command line.

[jas8522]

I have this same problem. It only occurs when connecting via https. Everything works as expected when connecting via http; it does not substitute the hostname for the internal network IP address when using http.

But then, the whole reason to use https (for me, and I'm assuming for just about everyone else) is to ensure remote connections are secure.

Version: 0.6.15
OS: Mac OS X 10.7.4
Install-type: OS X .app
Skin: Plush - gold (default)
Firewall Software: None.
Are you using IPV6? No
Is the issue reproducible? Yes

I've configured my router to forward ports 8080 (http) and 9095 (https). They were defaults when I installed sabnzbd.

The translation at No-IP and the port forwarding at my router must be working since 8080 works fine. My config is exactly the same for 9095.

I even tried setting the host field in the sabnzbd settings to my external no-ip hostname -- no luck.

It looks like whenever an SSL connection is initiated it redirects to the internal IP address no matter what.