Help! SSL received a record that exceeded the maximum ...

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • 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
vertuarts
Newbie
Newbie
Posts: 1
Joined: October 18th, 2014, 12:32 pm

Help! SSL received a record that exceeded the maximum ...

Post by vertuarts »

Updated NZB, now I see this:

Secure Connection Failed

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

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

What to do?
User avatar
sander
Release Testers
Release Testers
Posts: 8830
Joined: January 22nd, 2008, 2:22 pm

Re: Help! SSL received a record that exceeded the maximum ..

Post by sander »

vertuarts wrote:What to do?
Well ... how about this:
* tell us which browser you use.
* what if you use another browser
* which OS, which SABnzbd version
* what did you find and do when you googled the error message?
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Help! SSL received a record that exceeded the maximum ..

Post by shypike »

This usually happens when you switch from http to https
while using the same port.
I mean: until now you were using SABnzbd in http mode
on (e.g.) port 8080.
Then you decide to set SABnzbd to https mode, also on port 8080.
Or vice versa.
Chrome cannot handle that.

Tell Chrome to clear its cache and then restart it.
Post Reply