mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-26 13:15:55 +03:00
[GH-ISSUE #25] Why doesn't the key on dnspod work? #17
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @suixhxy on GitHub (Sep 13, 2024).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/25
Hello, why didn't my dnspod key work when I configured it?
The error message "Key not found," however, my key was obtained on the dnspod backend and is correct.
Please help to answer, thank you!
The complete log error is as follows:
error: one or more domains had a problem: [.yt.starhaha.com] [.yt.starhaha.com] acme: error presenting token: tencentcloud: failed to get hosted zone: API call failed: [TencentCloudSDKError] Code=AuthFailure.SecretIdNotFound, Message=SecretId不存在，请输入正确的密钥。, RequestId=499e3993-fb4a-4174-9671-f0faf001
@usual2970 commented on GitHub (Sep 13, 2024):
Hello, is your DNSPOD the China site or the international site?
@usual2970 commented on GitHub (Sep 13, 2024):
https://cloud.tencent.com/document/product/1427/56192
Check if there are any spaces before or after the key.
@suixhxy commented on GitHub (Sep 14, 2024):
First of all, thank you for answering my question. Thank you very much
Yes, it is the DNSPOD of China. It's not international.
Also, you mentioned to check the correctness of the key, I have done the check, it is correct. In addition, I used other tools acme.sh to configure this secret key and apply for a free certificate, which can be successfully applied, so the argument that the secret key is incorrect can be excluded.
@suixhxy commented on GitHub (Sep 14, 2024):
The latest error log is as follows:
@suixhxy commented on GitHub (Sep 14, 2024):
Thank you very much for your answer. After your prompt, I analyzed the log and guessed that the machine where my certimate service was located had suspended the proxy.
After viewing the public IP address:
curl ipinfo.io/ip
If the ip address is indeed the IP address after the proxy, cancel the proxy and re-deploy the certificate. The certificate can be successfully applied for.
Thank you very much, must give you a thumbs up!!!