[GH-ISSUE #572] [Bug] 证书申请成功但是 TXT 没有正确处理 #376

New issue

Closed

opened 2026-03-03 01:02:51 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:02:51 +03:00

Owner

Originally created by @zhuizhubf on GitHub (Mar 29, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/572

软件版本 / Release Version

docker buiild 部署的 v0.3.6

缺陷描述 / Description

证书申请成功但是 TXT 没有正确处理

复现步骤 / Steps to reproduce

正常使用阿里云的域名

日志 / Logs

开始
[2025-03-29 22:29:04]
ready to start ...
申请
[2025-03-29 22:29:04]
ready to apply ...
[2025-03-29 22:29:04]
re-apply, because the configuration item 'KeyAlgorithm' changed
[2025-03-29 22:29:14]
apply completed
部署
[2025-03-29 22:29:14]
ready to deploy ...
[2025-03-29 22:29:14]
run pre-command
[2025-03-29 22:29:14]
ssl certificate file saved
path:
"/etc/ssl/certs/ssl.crt"
[2025-03-29 22:29:14]
ssl private key file saved
path:
"/etc/ssl/certs/ssl.key"
[2025-03-29 22:29:14]
deploy completed
若前序节点执行成功…
[2025-03-29 22:29:14]
the previous node execution was succeeded

其他 / Miscellaneous

No response

Originally created by @zhuizhubf on GitHub (Mar 29, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/572 ### 软件版本 / Release Version docker buiild 部署的 v0.3.6 ### 缺陷描述 / Description 证书申请成功但是 TXT 没有正确处理 ![Image](https://github.com/user-attachments/assets/eb79ac90-0b0a-4e26-b798-28b13cfda899) ![Image](https://github.com/user-attachments/assets/f5eefb4a-f8b8-48c0-8e2a-1834d186ac8f) ### 复现步骤 / Steps to reproduce 正常使用阿里云的域名 ### 日志 / Logs <details> ```console 开始 [2025-03-29 22:29:04] ready to start ... 申请 [2025-03-29 22:29:04] ready to apply ... [2025-03-29 22:29:04] re-apply, because the configuration item 'KeyAlgorithm' changed [2025-03-29 22:29:14] apply completed 部署 [2025-03-29 22:29:14] ready to deploy ... [2025-03-29 22:29:14] run pre-command [2025-03-29 22:29:14] ssl certificate file saved path: "/etc/ssl/certs/ssl.crt" [2025-03-29 22:29:14] ssl private key file saved path: "/etc/ssl/certs/ssl.key" [2025-03-29 22:29:14] deploy completed 若前序节点执行成功… [2025-03-29 22:29:14] the previous node execution was succeeded ``` ![Image](https://github.com/user-attachments/assets/9711a78e-8df9-467f-920b-9e7cbb90b223) </details> ### 其他 / Miscellaneous _No response_

kerem

2026-03-03 01:02:51 +03:00

closed this issue
added the
bug

declined
labels

kerem commented

2026-03-03 01:02:52 +03:00

Author

Owner

@fudiwei commented on GitHub (Mar 29, 2025):

https://letsencrypt.org/docs/faq/#i-successfully-renewed-a-certificate-but-validation-didn-t-happen-this-time-how-is-that-possible

Once you successfully complete the challenges for a domain, the resulting authorization is cached for your account to use again later. Cached authorizations last for 30 days from the time of validation. If the certificate you requested has all of the necessary authorizations cached then validation will not happen again until the relevant cached authorizations expire.

@fudiwei commented on GitHub (Mar 29, 2025): ![Image](https://github.com/user-attachments/assets/c2dd963b-f3cc-4b25-9504-2633905e5fc2) > https://letsencrypt.org/docs/faq/#i-successfully-renewed-a-certificate-but-validation-didn-t-happen-this-time-how-is-that-possible > > Once you successfully complete the challenges for a domain, the resulting authorization is cached for your account to use again later. **Cached authorizations last for 30 days** from the time of validation. If the certificate you requested has all of the necessary authorizations cached then validation will not happen again until the relevant cached authorizations expire.

kerem referenced this issue

2026-03-03 01:06:54 +03:00

[PR #375] [MERGED] feat: new UI #932