HTTPS issue

[munzbd]

So I have issues gaining HTTPS access from remote devices outside of my local network. There are a few threads in here about it, but no solutions.
Lets see if this information can help as I dont like using unsecure transmission over the internet.

For reference:

• Host is set to 0.0.0.0
• HTTP port is 8080 with portforwarding to 9998
• HTTPS port is 9090 with portforwarding to 9999
• Username and password is set
• I have a dyndns account

From computer:

• dns.dyndns.org:9998 -> WORKS
• http://dns.dyndns.org:9998 -> WORKS
• https://dns.dyndns.org:9998 ->ERROR: Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
• http://dns.dyndns.org:9998/sabnzbd -> WORKS
• dns.dyndns.org:9998/sabnzbd -> WORKS
• dns.dyndns.org:9999 -> WORKS
• http://dns.dyndns.org:9999 -> ERROR: Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to reach the server. URL changes to https://localhost:9090/sabnzbd
• https://dns.dyndns.org:9999 -> WORKS
• https://dns.dyndns.org:9999/sabnzbd -> WORKS
• dns.dyndns.org:9999/sabnzbd -> ERROR: Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection. URL changes to https://localhost:9090/sabnzbd

Now from my GNex

• dns.dyndns.org:9998 -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:8080/sabnzbd
• http://dns.dyndns.org:9998 -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:8080/sabnzbd
• https://dns.dyndns.org:9998 ->ERROR: Couldn't establish a secure connection
• http://dns.dyndns.org:9998/sabnzbd -> WORKS
• dns.dyndns.org:9998/sabnzbd -> WORKS
• dns.dyndns.org:9999 -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:9090/sabnzbd
• http://dns.dyndns.org:9999 -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:8080/sabnzbd
• https://dns.dyndns.org:9999 -> ERROR: Couldn't establish a secure connection
• https://dns.dyndns.org:9999/sabnzbd -> ERROR: Couldn't establish a secure connection
• dns.dyndns.org:9999/sabnzbd -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:9090/sabnzbd

None of the above non working addresses work in mobile apps either
Any ideas?

[shypike]

https://localhost:9090/sabnzbd
The /sabnzbd part is required, leaving it out is not supported, but may sometimes work.
Also, most browsers throw a fit when you switch between http and https on the same port.

[munzbd]

Needs to be done through an external address as I'm trying to remotely access it.

So using localhost won't work.

Replacing localhost with my external IP doesn't work and changing the port to 9999 doesnt

[shypike]

I wasn't referring to the localhost part, but to the fact that "/sabnzbd" is missing from you URLs.
Each time you leave it out, access fails. As seen in your own examples.

[munzbd]

https://dns.dyndns.org:9999/sabnzbd -> ERROR: Couldn't establish a secure connection
dns.dyndns.org:9999/sabnzbd -> ERROR: Couldn't establish a secure connection URL changes to https://localhost:9090/sabnzbd

[shypike]

What happens if you using the same ports?
So external-9090-->internal-9090 and external-8080-->internal-8080.
Possibly either your router or SABnzbd gets confused by the different port numbers.
Should SABnzbd ever need to send an absolute URL, it will use the wrong port
because it's not aware that externally you're using a different port number.

The changing of dyndns to localhost suggests that you have only enabled HTTPS
and trying to access HTTP. The automatic redirection from HTTP-->HTTPS
fails when using an external address. This has to do with shortcoming of
the internal web framework that we use.
I'm not saying that you've set it up incorrectly, but the above is typical behaviour
under the those circumstances. Could be a bug of course.

[sander]

On top of what Shypike says, I would do this:

1) use your public IP address, to rule out dyndns stuff
2) temporarily turn off the login. Less secure, but easier testing.

Furthermore: As a forum admin, I can see the IP address you're posting from. I used that IP address in https://<blabla>:9999/sabnzbd/ and I get the SABnzbd login. So that's good.