Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Suddenly, *only with Firefox* all computers in the house show (Error code: ssl_error_rx_record_too_long) when trying to access any Google product.

  • 121 Mbohovái
  • 312 oguereko ko apañuãi
  • 2054 Hecha
  • Mbohovái ipaháva shawssl2

more options

Today, all laptops in the house (latest ver of FF) began throwing the error:

(Error code: ssl_error_rx_record_too_long)

When trying to access any Google products: gmail, Google+, analytics, Google website, etc

Today, all laptops in the house (latest ver of FF) began throwing the error: (Error code: ssl_error_rx_record_too_long) When trying to access any Google products: gmail, Google+, analytics, Google website, etc

Ñemoĩporã poravopyre

Make sure to reset the security.tls.version.max pref to 1 if you have previously changed this pref to 0 to disable TLS 1.0

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 6

Opaite Mbohovái (1)

more options

My question is why are TLS connections affected? What is Shaw up to? Inspecting, manipulating traffic? I'm a little concerned....

A little post mortem would be fantastic. Of course ISPs at this level will never release this kind of information.

This has been an interesting experience. You can tell very easily which websites configured their SSL properly.

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7