חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

When surfing to a website created by our org hosted/certified by Go Daddy, the user receives a certificate warning. Is Firefox going to start adding Go Daddy as a certificate authority?

  • 3 תגובות
  • 10 have this problem
  • 3 views
  • תגובה אחרונה מאת paulf

more options

Users are able to access site by clicking through warnings, but the site does not appear secure even though it has a certificate thru Go Daddy which is contained w/in IE's list of Certificate Authorities. Prospective clients using Firefox are going to be understandably weary of visiting the site.

Users are able to access site by clicking through warnings, but the site does not appear secure even though it has a certificate thru Go Daddy which is contained w/in IE's list of Certificate Authorities. Prospective clients using Firefox are going to be understandably weary of visiting the site.

כל התגובות (3)

more options

"The Go Daddy Group, Inc." is already included in the certificates list (Tools > Options > Advanced > Encryption > View Certificates).

What is the exact message you are receiving?

more options

Firefox has the Go Daddy certificate build-in (Go Daddy Class 2 Certification Authority), but your server doesn't send the required intermediate certificate (Go Daddy Secure Certification Authority).
If you have ever visited a web server that sends that certificate then Firefox will store it for future use and you won't see an error. If you haven't done that yet then you will get an "This Connection is Untrusted" error.

You can verify that via a SSL check website: http://www.networking4all.com/en/support/tools/site+check/

more options

Connection Untrusted. I can trust the connection by importing the certificate, but noone wants a prospect to be introduced to a product in that manner. After checking on http://www.networking4all.com, there was an error in configuration - 'Unable to get the local issuer of the certificate. The issuer of a locally looked up certificate could not be found. Normally this indicates that not all intermediate certificates are installed on the server.' Checking on that - thanks!