SABnzbd Forums

I had this problem with version 0.7.4 and also am having it with 0.7.5RC1. When this happens, I get an SSL error something like too long or too many... If I manually change the Port back to 8085 and then enable HTTPS port 9095 and restart sabnzbd, then I can then connect in my web browser to https://localhost:9095/ without a problem...
My configuration:
Linux Mint 13 64-bit Cinnamon (Kernel 3.6.5)

As this is your first post, I want to see you reply before I give a real answer.

So ... post a reply to this post, and I'll help you.

I don't understand your request but here is a reply

I do not understand your first post, but I do recognize your subject: "SABnzbd Port is automatically changing to HTTPS Port"; that does happen whay you access SABnzbd on plain HTTP, but with a non-existing part in URL, so far exmple: http://localhost:8080/adfa/asdf/asdf ... SAB will then redirecto HHTPS (if HTTPS is enabled).

Is that what you mean?

No, I mean in the Config-General the Sabnzbd port is actually changed to the https port, so, 8085 is overwritten with 9095 and then Enable HTTPS is not ticked. I can load the cached page from a previous session and then manually changed the values back to what they should be then restart SABnzbdplus and then I can then connect securely...

I'm looking into this.
I have seen this happen occasionally, but I'm not sure yet why it happens.
It is a problem in SABnzbd. When it happens, I think it's due to another instance running.

The odd behaviour of the browser is actually caused by the browser itself.
Most panic when the host:port goes from http to https or vice versa.
Probably caching issues.