Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

why are conservative websites blocked with Error code: NS_ERROR_NET_INADEQUATE_SECURITY

  • 1 одговор
  • 1 има овај проблем
  • 13 прегледа
  • Последњи одговор послао cor-el

goodsales23
goodsales23
more options

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!!

Сви одговори (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

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