Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Blocked from searching Google!

  • 1 antwurd
  • 2 hawwe dit probleem
  • 4 werjeftes
  • Lêste antwurd fan philipp

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?

Alle antwurden (1)

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.