Mark, Daniel,
According to the logs I can confirm that I got the certificate error when
there was no server_name sent in the ClientHello message.
Actually the log shows that the SNI was tried to be set, but failed.
javax.net.ssl|DEBUG|49|Update center installer thread [#1]|2021-11-22
09:15:12.1
> On 19. Nov 2021, at 20:52, Mark Waite wrote:
>
> I thought that certificate could be reported when a request is made to the IP
> address of an HTTP server hosted in Kubernetes. The Kubernetes server needs
> the hostname in order to use the correct SSL certificate (or something like
> tha
On Friday, November 19, 2021 at 12:35:36 PM UTC-7 you wrote:
> Mark,
>
> Thank you for your response.
>
> Yes I'm running Linux. (sorry for missing this information)
>
> I suspected the Let's Encrypt certificates earlier, so I've already added
> ISRG Root X1 (the issuer of Let's Encrypt) to the
Mark,
Thank you for your response.
Yes I'm running Linux. (sorry for missing this information)
I suspected the Let's Encrypt certificates earlier, so I've already added
ISRG Root X1 (the issuer of Let's Encrypt) to the cacerts file.
Nevertheless I just replaced my cacerts file with the one in t
I think that the output
of https://updates.jenkins.io/latest/antisamy-markup-formatter.hpi?mirrorlist
will show that your location may be served by multiple Jenkins mirrors.
You can then check each of the mirrors to identify if one of them is
responding with an incorrect SSL certificate.
It co
