-
-
Couldn't load subscription status.
- Fork 1.1k
Add DNS provider for Yandex 360 #1975
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kllakk83
reviewed
Aug 3, 2023
kllakk83
reviewed
Aug 3, 2023
|
@kllakk83 I updated the PR, can you run again the command and give me the output? |
|
@ldez Thank you, now I got a certificate $ ./dist/lego -m [email protected] --dns yandex360 -d "*.mydomain.com" -d "mydomain.com" run
2023/08/04 12:13:20 No key found for account [email protected]. Generating a P256 key.
2023/08/04 12:13:20 Saved key to /home/sergey/GolandProjects/ldez/lego/.lego/accounts/acme-v02.api.letsencrypt.org/[email protected]/keys/[email protected]
2023/08/04 12:13:21 Please review the TOS at https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf
Do you accept the TOS? Y/n
2023/08/04 12:13:24 [INFO] acme: Registering account for [email protected]
!!!! HEADS UP !!!!
Your account credentials have been saved in your Let's Encrypt
configuration directory at "/home/sergey/GolandProjects/ldez/lego/.lego/accounts".
You should make a secure backup of this folder now. This
configuration directory will also contain certificates and
private keys obtained from Let's Encrypt so making regular
backups of this folder is ideal.
2023/08/04 12:13:25 [INFO] [*.mydomain.com, mydomain.com] acme: Obtaining bundled SAN certificate
2023/08/04 12:13:25 [INFO] [*.mydomain.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/251829755306
2023/08/04 12:13:25 [INFO] [mydomain.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/251829755316
2023/08/04 12:13:25 [INFO] [*.mydomain.com] acme: use dns-01 solver
2023/08/04 12:13:25 [INFO] [mydomain.com] acme: Could not find solver for: tls-alpn-01
2023/08/04 12:13:25 [INFO] [mydomain.com] acme: Could not find solver for: http-01
2023/08/04 12:13:25 [INFO] [mydomain.com] acme: use dns-01 solver
2023/08/04 12:13:25 [INFO] [*.mydomain.com] acme: Preparing to solve DNS-01
2023/08/04 12:13:27 [INFO] [mydomain.com] acme: Preparing to solve DNS-01
2023/08/04 12:13:27 [INFO] [*.mydomain.com] acme: Trying to solve DNS-01
2023/08/04 12:13:27 [INFO] [*.mydomain.com] acme: Checking DNS record propagation using [127.0.0.53:53]
2023/08/04 12:23:27 [INFO] Wait for propagation [timeout: 1h0m0s, interval: 10m0s]
2023/08/04 12:23:27 [INFO] [*.mydomain.com] acme: Waiting for DNS record propagation.
2023/08/04 12:33:28 [INFO] [*.mydomain.com] acme: Waiting for DNS record propagation.
2023/08/04 12:43:28 [INFO] [*.mydomain.com] acme: Waiting for DNS record propagation.
2023/08/04 12:53:29 [INFO] retry due to: acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/chall-v3/251829755306/dpUxww :: urn:ietf:params:acme:error:badNonce :: JWS has an invalid anti-replay nonce: "891F-SQjYOVI-oCnyb1P5AYBf8XC2_58STi8eLfMP31RSo0"
2023/08/04 12:53:33 [INFO] [*.mydomain.com] The server validated our request
2023/08/04 12:53:33 [INFO] [mydomain.com] acme: Trying to solve DNS-01
2023/08/04 12:53:33 [INFO] [mydomain.com] acme: Checking DNS record propagation using [127.0.0.53:53]
2023/08/04 13:03:33 [INFO] Wait for propagation [timeout: 1h0m0s, interval: 10m0s]
2023/08/04 13:03:38 [INFO] [mydomain.com] The server validated our request
2023/08/04 13:03:38 [INFO] [*.mydomain.com] acme: Cleaning DNS-01 challenge
2023/08/04 13:03:39 [INFO] [mydomain.com] acme: Cleaning DNS-01 challenge
2023/08/04 13:03:40 [INFO] [*.mydomain.com, mydomain.com] acme: Validations succeeded; requesting certificates
2023/08/04 13:03:41 [INFO] [*.mydomain.com] Server responded with a certificate. |
dmke
approved these changes
Aug 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
go mod tidyPing @kllakk83, can you run the command (with your domain, email, and credentials)?
Closes #1917