nanog mailing list archives
Re: Google.com SSL cert issues
From: Seth David Schoen <schoen () loyalty org>
Date: Wed, 21 Sep 2022 16:26:38 -0700
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_LONGIsn'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.
Current thread:
- Google.com SSL cert issues Mark Stevens (Sep 21)
- Re: Google.com SSL cert issues Gaurav Kansal (Sep 21)
- Re: Google.com SSL cert issues Randy (K6RP) (Sep 21)
- Re: Google.com SSL cert issues Mark Stevens (Sep 21)
- Re: Google.com SSL cert issues Jan Schaumann via NANOG (Sep 21)
- Re: Google.com SSL cert issues Seth David Schoen (Sep 21)
