最近又遇到一个用 CF 的 IP 但是不能替换的情况 #497

Journalist-HK · 2024-02-01T17:26:41Z

Journalist-HK
Feb 1, 2024

给 DNS 加了替换规则后出现了证书续签问题，发现这个地址换了 IP 就会出错

[opc@s1 ~]$ curl --resolve acme-v02.api.letsencrypt.org:443:172.65.32.248 https://acme-v02.api.letsencrypt.org/
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Boulder: The Let's Encrypt CA</title>

  <style type="text/css">
    header { display: flex; max-height: 30vh; flex-wrap: wrap; margin-bottom: 10vh; }
    header img { display: flex; max-height: 20vh; align-content: flex-end; margin-right: 20px; }
  </style>
</head>

<body>
  <header>
    <section>
      <img src="/static/images/LE-Logo-LockOnly.svg"/>
    </section>
    <section>
      <h1>Boulder<br>
      <small>The Let's Encrypt CA</small></h1>
    </section>
  </header>

  <section>
    <p>This is an <a href="https://tools.ietf.org/html/rfc8555">ACME</a> Certificate Authority running <a href="https://github.com/letsencrypt/boulder">Boulder</a>.</p>
    <p>This is a <em>programmatic</em> endpoint, an API for a computer to talk to. You should probably be using a specialized client to utilize the service, and not your web browser. See <a href="https://letsencrypt.org/docs"><tt>https://letsencrypt.org/docs</tt></a> for help.</p>
    <p>If you're trying to use this service, note that the starting point, <em>the directory</em>, is available at this URL: <a href="https://acme-v02.api.letsencrypt.org/directory"><tt>https://acme-v02.api.letsencrypt.org/directory</a></tt>.</p>
  </section>

  <footer>
      <p>
        <a href="https://letsencrypt.status.io" title="Status">Service Status (letsencrypt.status.io)</a> |
        <a href="https://twitter.com/letsencrypt" title="Twitter">Let's Encrypt Twitter</a>
      </p>
  </footer>

</body>
</html>
[opc@s1 ~]$ curl --resolve acme-v02.api.letsencrypt.org:443:104.17.7.198 https://acme-v02.api.letsencrypt.org/
curl: (35) error:0A000410:SSL routines::sslv3 alert handshake failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

最近又遇到一个用 CF 的 IP 但是不能替换的情况 #497

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

最近又遇到一个用 CF 的 IP 但是不能替换的情况 #497

Uh oh!

Journalist-HK Feb 1, 2024

Replies: 0 comments

Journalist-HK
Feb 1, 2024