Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

why are conservative websites blocked with Error code: NS_ERROR_NET_INADEQUATE_SECURITY

  • 1 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 24 gösterim
  • Son yanıtı yazan: cor-el

goodsales23
goodsales23

I have read the reason for this as explained by you but when you visit these sites with another browser you do not see this error.

Also checking the SSL which is what would throw this error (NS_ERROR_NET_INADEQUATE_SECURITY) it is clear that the SSL cert is not the issue. Site checked at ssllabs.com. Please be honest with me and tell me this is not censorship, this seems a little Orwellian and is disappointing!!

I have read the reason for this as explained by you but when you visit these sites with another browser you do not see this error. Also checking the SSL which is what would throw this error (NS_ERROR_NET_INADEQUATE_SECURITY) it is clear that the SSL cert is not the issue. Site checked at ssllabs.com. Please be honest with me and tell me this is not censorship, this seems a little Orwellian and is disappointing!!

Tüm Yanıtlar (1)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

NS_ERROR_NET_INADEQUATE_SECURITY indicates that the server initiates a HTTP/2 connection, but Firefox detects an invalid TLS configuration in the server response (server negotiated HTTP/2 with blacklisted cipher suites). This is likely not an issue with the certificate, but this is a problem with the server setup and there are invalid cipher suites for HTTP/2 claimed (INADEQUATE_SECURITY). When HTTP/2 is enabled and used then the requirements are much stricter than with HTTP/1.1