Once they understand their mistake, they then need to reconfigure their web server to send both the server and CA certificate. You need to talk to the server admin and point them in the direction of RFC 5246 Section 7.4.2. However, that certificate was signed by Starfield Secure Certificate Authority - G2 and that certificate also needs to be sent by your server.

Your server seems to be only sending the end-entity (server) certificate. Mac user: Firefox, Chrome, and Safari all not okĪny suggestions about what might be the cause for some users in some browsers?.Mac user: Chrome and Safari ok, Firefox.Mac user: Chrome, Firefox, Safari all ok.Windows user: Chrome and Edge ok, Firefox not.I did have them clear their browser caches.

I am not able to duplicate the problem myself, but the team testing results so far are as follows. Their suggestion was to Google around and see if I could find an answer. I talked to GoDaddy support and they patiently tried testing with all the URLs I gave them and to them they were able to get a secure connection each time and they said the site appears to be fine and the SSL certificate appears to be fine. Most get a secure connection with the green 'secure' lock with all browsers, like I do. One also said they see it in Chrome and Safari. Most of the few users with this problem only see this kind of message in Firefox. To protect your information from being stolen, Firefox has not connected to this website.' The owner of has configured their website improperly. The warning is different for different browsers, but for Firefox it reads, 'Your connection is not secure. Most other members of our team also see the same thing.īut some team members get a warning page instead. I see the 'secure' lock in Chrome, Firefox, and Safari on my Mac.

It opens a page containing only the JPG image mentioned. The media server has an SSL certificate purchased from GoDaddy. I have a server containing just media (images).

Firefox says insecure connection