Hi, On Jun 18, 2016, at 23:00, Sven Eckelmann <[email protected]> wrote:
> On Saturday 18 June 2016 21:00:59 René Rebe wrote: >> Hm, >> >> I “think” I replaced it with the x3 certificate, but the updated scan does >> not look so different, … ? > > Not sure what you mean by "scan does not look so different". It now shows > that > the X3 intermediate certificate is delivered instead of the incorrect X1 > intermediate certificate. But the number of the certificates is wrong. You > should first send your certificate followed by the X3 certificate. I meant the checker still complaint about the certificate chain and I did not quite understood why, ... > But you are sending right now: > > * your certificate > * your certificate > * Lets Encrypt X3 certificate. Interesting, I did not realize this double certificate. The lets encrypt guide I used said “cat the cert and the intermediate cert”. Guess that was wrong then, and it looks better now with the cert config tweaked yet again. > uscan doesn't seem to have a problem with it (at least it can now detect the > available exactimage versions again) but there might be other HTTPS clients > which choke on it. Just let me know if you find something yet again, and/or if the tweaked cert chain still works for you ;-) -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe exact-image
