Certificate's owner does not match hostname ‘cert.int-x3.letsencrypt.org’


Could it be that it is IPv6 specific?

wget -vS http://cert.int-x3.letsencrypt.org/
--2018-03-09 19:10:45--  http://cert.int-x3.letsencrypt.org/
Resolving cert.int-x3.letsencrypt.org (cert.int-x3.letsencrypt.org)... 2a02:26f0:132:3a6::ce0, 2a02:26f0:132:3bc::ce0,
Connecting to cert.int-x3.letsencrypt.org (cert.int-x3.letsencrypt.org)|2a02:26f0:132:3a6::ce0|:80... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 301 Moved Permanently
  Server: AkamaiGHost
  Content-Length: 0
  Location: https://cert.int-x3.letsencrypt.org/
  Cache-Control: max-age=0
  Expires: Fri, 09 Mar 2018 19:10:45 GMT
  Date: Fri, 09 Mar 2018 19:10:45 GMT
  Connection: keep-alive
Location: https://cert.int-x3.letsencrypt.org/ [following]
--2018-03-09 19:10:45--  https://cert.int-x3.letsencrypt.org/
Connecting to cert.int-x3.letsencrypt.org (cert.int-x3.letsencrypt.org)|2a02:26f0:132:3a6::ce0|:443... connected.
The certificate's owner does not match hostname ‘cert.int-x3.letsencrypt.org’


Hi @szepeviktor,

I believe this is related to an ongoing issue: https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/5aa2c4df1e024002287ebe57


We’re experiencing the same issue using dehydrated:

ERROR: Problem connecting to server (get for http://cert.int-x3.letsencrypt.org/; curl returned with 51)


Yes, this is also caused by the ongoing issue. There is an open Dehydrated issue I replied on as well.

Apologies for the disruption.


@cpu issue cleared up. Thank you.


Thank you for maintenance


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.