[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nanog
Subject:    Re: Google.com SSL cert issues
From:       Seth David Schoen <schoen () loyalty ! org>
Date:       2022-09-21 23:26:38
Message-ID: 20220921232638.GR3430915 () frotz ! zork ! net
[Download RAW message or body]

Jan Schaumann via NANOG writes:

> Mark Stevens <manager@monmouth.com> wrote:
> > Is anyone else getting the following error when trying to access any of
> > google's services?
> > SSL_ERROR_RX_RECORD_TOO_LONG
> 
> Isn't this usually a sign of a protocol mismatch?
> I.e., TLS 1.3 vs TLS 1.2.

The most common protocol mismatch that causes this is speaking HTTPS to
an HTTP port.  For instance, you can see this error at normal times with
URLs like

https://google.com:80/
https://example.com:80/

If you get some misconfiguration where port 443 is speaking HTTP instead
of HTTPS, you'll see the same error.
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic