Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Secure Connection Failed An error occurred during a connection to www.google.com. You have received an invalid certificate. Please contact the server admi

  • 3 replies
  • 16 have this problem
  • 897 views
  • Last reply by schro_cat

more options

Hi, I get this every time I try to use Firefox

can you please help with the correct answer


 Secure Connection Failed   An error occurred during a connection
 to www.google.com. You have received an invalid certificate.
 Please contact the server administrator or email correspondent
 and give them the following information: Your certificate contains the
 same serial number as another certificate issued by the certificate authority.
 Please get a new certificate containing a unique serial number.
 (Error code: sec_error_reused_issuer_and_serial)
 The page you are trying to view cannot be shown because the authenticity 
 of the received data could not be verified.'bold text'
 Please contact the website owners to inform them of this problem.

All Replies (3)

more options

Do you use ESET security software? Its feature of scanning your SSL connections has been linked to this particular error code in the past. Do you want to try disabling SSL scanning in ESET and see whether that resolves it: http://kb.eset.com/esetkb/index?page=content&id=SOLN3126 If that works, there might be a problem of duplicate ESET certificates in Firefox's certificate store. It should be fixable.

more options
more options

I was just struggling with the same issue. I do have Avast and found that it created this problem. I used the solution I found on: https://support.mozilla.org/en-US/questions/1028985

I disabled 'https scanning' in the Avast web shield settings. Since changing that setting, the problem has not recurred.

I will note that I have the same software installed on two computers, but the issue only occurred on one. So, there may be other contributing factors (OS, hardware, etc.) but the fix worked.