Open garrett opened 4 years ago
@elhananjair found the anti-virus issue in #14448 and pointed out that Firefox worked still, even when Edge (Chromium-based) didn't.
Note 1 (Firefox): After a bit of digging around, I found that Firefox has its own certificate store and does not normally use the system-wide Windows certificate store. (There are, of course, settings to override this and use Windows' own cert store too. But it's not enabled by default — and only intended for corporate usage.) So a quick test, under most circumstances, is to see what Firefox does if Edge is having issues like this.
Note 2 (Chrome): Here's how Chrome does it: https://www.chromium.org/Home/chromium-security/root-ca-policy (TL;DR: they apparently have their own cert storage, but also reference the system cert storage.)
@garrett in my case I was trying with self signed certificate, is this problem persist on official certifications too?
https://cockpit-project.org/faq.html#login has some info about that now, but we don't yet link to it from the failure page.
Our certificate issue page is confusing.
It's the page which displays when:
wss://
from working (that is: secure websockets).To solve these issues in Cockpit we need to: