-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Private Key Not Generated When Using ACME for Wildcard Certificate with ECC Encryption #6255
Comments
Please upgrade to the latest code and try again first. Maybe it's already fixed. |
To ensure that openssl is problem free. I tested my own signature openssl ecparam -name secp384r1 -genkey -out my_folder/1.keys |
Oh… fine, but it is too hard. I need to cut it into two pieces. acme.sh --issue --dns dns_tencent -d my.domain -d .my.domain --force --debug 2 [Fri 28 Feb 2025 10:59:33 PM CST] d='*.my.domain' [Fri 28 Feb 2025 10:59:35 PM CST] Let's check each DNS record now. Sleeping for 20 seconds first. |
[Fri 28 Feb 2025 11:02:48 PM CST] Let's wait for 10 seconds and check again.
[Fri 28 Feb 2025 11:03:44 PM CST] Cert success. |
umm......I don't know what happened, but when I remove work dir /myuser/.acme.sh/my.domain and reissue cert.it says:at 01 Mar 2025 12:55:34 PM CST] Creating domain key |
I have been using ACME to apply for a wildcard certificate with ECC encryption and updating local certificates with install-cert for a year now, and it has been stable. However, I encountered an issue within the last month (I renew once a month). The problem occurred when I tried to restart Nginx, and I found that my private key was mysteriously missing. I attempted to reissue the certificate, but the private key was still not generated. Strangely, when I used debug 2 to check all the data, everything appeared normal except for two issues related to my DNS server not being able to resolve my domain. My server is located in mainland China, so there might be issues accessing Cloudflare. However, I ultimately obtained the correct DNS resolution data, successfully authenticated, and received the correct certificate. Yet, there was still no private key, and there were no error messages. It seems as if the private key file simply cannot be generated. I am at a loss on how to proceed with troubleshooting. I couldn't find anyone with the same issue in existing issues. How can I resolve this problem? Or what is the process that ACME uses to generate the private key? Understanding this might help me identify the issue.
The data has been sanitized, and parts that I believe might contain sensitive hash data have been replaced with asterisks (***). My domain and IP have been replaced. If you need more data, please let me know, and I will provide it promptly.
debian:~# acme.sh --version
https://github.com/acmesh-official/acme.sh
v3.1.0
and my log.it is too long, so I update it
upda_err.txt
Thank you very much if you can provide any assistance.
The text was updated successfully, but these errors were encountered: