Hi Jeroen,
You mean that you updated the certificate in the container?
Can you check that when you updated the cert, the CN is corect ? and that the queries are done with that CN ?
If i’m not mistaking the CN contain the name of the host. and as such if that differs now there could be some issues.
I updated the certificate on the host, using the webinterfacem, and then copied the resulting localhost.cert and .key to the conatiner. Since that moment, my AD authentication doesnt work any longer
Is it a letsencrypt cert or did you upload another cert?
I had a problem with a bought cert recently because the chainfile was wrong. Chrome showed it as ok but https://www.sslshopper.com/ssl-checker.html showed me what was wrong…just an idea.
yields an error about an expired certificate … it shows the complete chain tho … could it be that this is a chain issue as @mrmarkuz suggests, and if so, any clue on how to proceed ?
basically the certificate has to be checked against the issues.
Maybe there is no trust certificate to check against?
Or if the issuer is outside like Verisign etc, you need to have a way to contact them, check that the FW is not blocking something…
Just my opinion, I’ve never done a change of cert in NS
The last step can probably be done more elegant, but I am of the ‘reboot to make sure’-school (aka, not entirely sure, lets use a big gun) No other configuration was needed to get this working. Just some documentation to not miss the copy step