Skip to content

Loading…

[Firefox] chrismatic.io Untrusted Connection #1227

Closed
5t3f4n opened this Issue · 11 comments

4 participants

@5t3f4n

This is not an issue with uBlock so I apologize in advance, but I don't know where else to post.
https://chrismatic.io/ reports This Connection is Untrusted in Firefox. It works fine in Safari.

image

System: OS X 10.10.3 (14D131)
Browser: Firefox 37.0.1 running in "safe mode"

@SW1FT

Certificate problems. Do you have Kaspersky Internet Security by any chance?

@5t3f4n

No I do not have any kind of security software. Note that it works fine in Safari.
Shouldn't a certificate issue affect all browsers? And all people?

@SW1FT

Certificate issues affect single browsers. I was talking about KIS because I had a similar issue with Firefox only and it was a certificate that I needed from Kaspersky to access some websites.
Regarding your issue, I suggest deleting cert8.db file located in \AppData\Roaming\Mozilla\Firefox\Profiles\PROFILE-NAME or simply resetting Firefox.

@chrisaljoudi

Probably have the old certificate in cache. Can you try force reloading/emptying cache?

@5t3f4n

@SW1FT I don't have an \AppData\ because I'm not on Windows, which is evident from my original post. Appreciate the effort, but please at least read the whole post. It's not that long. I did, however, remove cert8.db from where my Firefox profile is actually located but it did not help.

@chrisaljoudi Yes I've tried reloading without cache and manually clearing everything as well. No difference.

Is there anything else I can do to troubleshoot short of starting with a fresh Firefox install/profile? It worked fine just a few days ago. The issue may or may not have surfaced after updating to 10.10.3.

@gitarra

The server doesnt include intermediate certificates in the certificate chain.

You can see the issue here:
https://www.ssllabs.com/ssltest/analyze.html?d=chrismatic.io

It isnt an issue on your end.

Edit: Actually removing the cert database of Firefox would cause this issue, as you wouldnt have those intermediate certificates cached anymore. The reason we can connect to the site is that we have those missing certificates already cached in Firefox.

@chrisaljoudi chrisaljoudi added the fixing label
@chrisaljoudi

Oops. Fixing.

@chrisaljoudi

Fixed.

@chrisaljoudi chrisaljoudi removed the fixing label
@chrisaljoudi

Thanks for pointing this out!

@5t3f4n

Can confirm it's working as expected now.

gitarra: thanks for explaining.
chrisaljoudi: thanks for fixing.

@gitarra

No problem :+1:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.