Ubuntu Server remote web access using HTTPS from Windows 7/Firefox. Error.

[whiskeytango]

I have SABnzbdplus 0.5.0 RC6 installed on Ubuntu Server 9.10 (64-bit)
I had it working for awhile but after awhile it stopped connecting from my home computer to the server and I can't figure out where I went wrong. I'm kind of a linux noob so bare with me here.

This is the error I'm getting:
Secure Connection Failed

An error occurred during a connection to x.x.x.x:9090.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)

in the ini file for hosts I have tried my servers ip, 0.0.0.0, and the host name (mediaserver) but get the same error for all three. For port I have been trying 9090. I connected before using ssl so I don't know what went wrong. Any suggestions? Thanks.

[shypike]

SABnzbd relies on a bunch of Ubuntu packages over which we have no control,
like PyOpenSSL, OpenSSL etc,
Does this happen persistently?
Does it help to restart SABnzbd? The system?

[jcfp]

An error occurred during a connection to x.x.x.x:9090.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)

Trying to establish a https connection on a port serving normal http?

[whiskeytango]

Yes it happens persistently. jcfp might be on to something. I was under the impression that port 9090 was already defined as an ssl port (if that makes any sense) For my windows desktop SABnzbd I just set the port to 9090 and was able to connect via https right away with no further tweaking. How can I define port 9090 as an ssl port on my Ubuntu Server? Hopefully this makes a little sense. My knowledge of linux servers is limited. I just thought setting the port to 9090 for ssl would automatically be recognized because it seemed to work that way on my desktop setup.

[shypike]

You set the port in Config->General.
After a restart it will start listening on 8080 for http and 9090 for https.
Or whatever else you configure.

[whiskeytango]

You set the port in Config->General.
After a restart it will start listening on 8080 for http and 9090 for https.
Or whatever else you configure.

Yes, I did that. I checked Enable HTTPS box and set the HTTPS port to 9090 but I always get the error message I posted above.  
It connects if I erase the s from http (http + port 9090) but https + port 9090 gives me the error message. I assume http + 9090 is not giving me a ssl connection.
By the way, I get the same results trying to connect to sabnzbd+ web interface from my server firefox and my home pc firefox.

[shypike]

The protocol and the port need to match.
This is the same for every website in the world that uses https.
You browser silently uses port 443 when you use https.
While http uses 80.

[bas r]

I had the same problem, and fixed it according to my post here:
http://ubuntu-virginia.ubuntuforums.org ... ostcount=3

[jdevlin]

sweet thanks