[1.1.0RC3] HTTPS broken on Firefox 48

Questions and bug reports for Beta releases should be posted here.
Forum rules
Help us help you:
  • 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
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

[1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

It works with it off, but when turned on I receive: An error occurred during a connection to 127.0.0.1:9090. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
User avatar
safihre
Administrator
Administrator
Posts: 5339
Joined: April 30th, 2015, 7:35 am
Contact:

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by safihre »

Can you confirm that if you switch back to RC2 there is no error?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

Same thing with RC2.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by shypike »

Clean Firefox's cache.
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

No change.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by sander »

I would try this:

stop SABnzbd
in the directory .sabnzbd/admin (or what it is on your OS): move server.cert and server.key to another place
start SABnzbd

... does that solve it?
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

Tried several times with RC2 and with RC3 with no change.

Edit: FWIW I'm using Windows 10 x64, Firefox 48 x64
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by sander »

What do Chrome and IE/Edge say?
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

This site can’t provide a secure connection

127.0.0.1 sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by sander »

ambiance wrote:This site can’t provide a secure connection

127.0.0.1 sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
Please read https://aboutssl.org/fix-google-chrome- ... ocol_error
ambiance
Newbie
Newbie
Posts: 19
Joined: January 16th, 2015, 12:23 am

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by ambiance »

I tried deleting sabnzbd.ini and sure enough it works without issue.
shlub
Newbie
Newbie
Posts: 1
Joined: September 25th, 2016, 12:10 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by shlub »

ambiance wrote:I tried deleting sabnzbd.ini and sure enough it works without issue.
Confirmed for 1.1 GA, delete (or move and merge contents later) sabnzbd.ini file under \AppData\Local\sabnzbd and it will operate normally. If you do not merge SELECT ini file contents later, you will need to go through setup again.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: [1.1.0RC3] HTTPS broken on Firefox 48

Post by sander »

If you mix up HTTP and HTTPS, Chrome will say:
This site can’t provide a secure connection

127.0.0.1 sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
So, good (default ports):
http://127.0.0.1:8080/sabnzbd/
https://127.0.0.1:9090/sabnzbd/


You get the above error if you try to use this mixed up, incorrect URLs:
https://127.0.0.1:8080/sabnzbd/
http://127.0.0.1:9090/sabnzbd/

In other words: If you get the error above, re-check your URL: HTTP/HTTPS and port.
Post Reply