We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Blocked from searching Google!

  • 1 回覆
  • 2 有這個問題
  • 4 次檢視
  • 最近回覆由 philipp

Monkeys_uncle
Monkeys_uncle
more options

I'm trying to do what I've done for years - double click a word in another site then "Search Google for....." - and I can't. Secure Connection Failed The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

Secure Connection Failed - what a bloody joke!

This is presumably the latest update to Firefox privacy - and if so then say goodbye to me. What's the use of blocking such sites - sure, block illegal and dangerous sites, but blocking Google - what the heck!

Please explain or otherwise tell me what to do to avoid such problems. Of course, I know what else I can do - I can go elsewhere quite happily but why should I?

I'm trying to do what I've done for years - double click a word in another site then "Search Google for....." - and I can't. Secure Connection Failed The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Secure Connection Failed - what a bloody joke! This is presumably the latest update to Firefox privacy - and if so then say goodbye to me. What's the use of blocking such sites - sure, block illegal and dangerous sites, but blocking Google - what the heck! Please explain or otherwise tell me what to do to avoid such problems. Of course, I know what else I can do - I can go elsewhere quite happily but why should I?

所有回覆 (1)

philipp
philipp
  • Moderator
more options

thanks for reporting the problem, so we have heard about this problem from avast/avg users whose security software is meddling with encrypted connections. firefox 61 introduced the better security protocol tls 1.3 & apparently avast can't cope with that yet.

please try to disable the scanning of https connections as described in https://support.mozilla.org/en-US/kb/troubleshoot-SEC_ERROR_UNKNOWN_ISSUER#w_avast as a workaround.