Is anyone else getting the following error when trying to access any of google's services? SSL_ERROR_RX_RECORD_TOO_LONG This started about an hour ago and is not dependent on browser type but rather geographic location. I have servers on different networks and some can no longer access google.com due to the SSL error. Thanks Mark
I am able to access google.com without any issues.
On 21-Sep-2022, at 20:57, 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 This started about an hour ago and is not dependent on browser type but rather geographic location. I have servers on different networks and some can no longer access google.com due to the SSL error.
Thanks
Mark
Malware bytes is blocking all google properties as of 30 min ago. --- ~Randy (K6RP) On 09/21/2022 8:26 am, Mark Stevens wrote:
Is anyone else getting the following error when trying to access any of google's services? SSL_ERROR_RX_RECORD_TOO_LONG This started about an hour ago and is not dependent on browser type but rather geographic location. I have servers on different networks and some can no longer access google.com due to the SSL error.
Thanks
Mark
That is it, malware bytes is on a few of these server. Thanks to all who chimed in!!! Mark On 9/21/2022 11:31 AM, Randy (K6RP) wrote:
Malware bytes is blocking all google properties as of 30 min ago.
--- ~Randy (K6RP)
On 09/21/2022 8:26 am, Mark Stevens wrote:
Is anyone else getting the following error when trying to access any of google's services? SSL_ERROR_RX_RECORD_TOO_LONG This started about an hour ago and is not dependent on browser type but rather geographic location. I have servers on different networks and some can no longer access google.com due to the SSL error.
Thanks
Mark
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. My money would be a MitM / middlebox / proxy that messed up when your client tried to talk 1.3 to Google, but the middlebox can't talk 1.3 and tried to downgrade or something like that. -Jan
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.
participants (5)
-
Gaurav Kansal
-
Jan Schaumann
-
Mark Stevens
-
Randy (K6RP)
-
Seth David Schoen