Add DNS provider for Mittwald #2200
Merged
Conversation
This file contains 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
ldez
added
enhancement
area/dnsprovider
state/need-user-tests
|
@jotimann do you need help to build or test the PR? |
|
Hi @ldez, After checkout and build i run the lego command. But i got an exception about a nil value on this:
This is the full output: The _acme-challenge.DOMAIN.TLD was created and on another run the code complains about [cleaning up failed] the existence of it, because it could not identify the ID of that zone: Please let me know if i can further assist with testing or debugging. |
|
I fixed the problem with the nil |
|
I removed the TXT Record for lego-test.de for "_acme-challenge.lego-test.de" by hand I made a new call for a subdomain (which not exists before) seems successful: Maybe this is helpful? |
|
I have 2 problems:
Currently:
After that, I want to add a TXT record, so I need the zone ID and a TXT record (https://api.mittwald.de/v2/docs/#/Domain/dns-update-record-set). So I tried to create a zone to handle the subdomain, but it seems this was not the right approach. I didn't find how to delete a record, the API documentation doesn't provide clear information about that, so I just tried to delete the zone I created before. Can you help me find the right to use the API? |
How to add a TXT record for a domain without creating a zone:If i understand u correct u wanna create a txt record for e.g. _acme-challenge.test.domain.tld. You only can set a txt record for _acme-challenge.test.domain.tld if you have the a zone for the subdomain. So you first need to create the zone _acme-challenge.test.domain and then set an txt record for it. How to remove a TXT recordto delete a txt record you must use the https://api.mittwald.de/v2/docs/#/Domain/dns-update-record-set and set it to |
This means it is not possible to add several TXT entries and use them as expected.
So, an error will appear when trying to remove TXT records when there are several domains/subdomains (i.e. wildcard), this error will be ignored but it will appear in the logs. I modified the implementation based on your feedback, it should work now. |
|
Here are some testruns, it's confusing... Maybe some leftovers kicked in, but what i found (replicatable) is that it seems to only fail on first runs. second or subsequent runs succeed! Please have a look on the collected logs. On the first run i get: As you can see above, there was a timeout waiting for dns record propagation. And when running the same again: Some time later the same command seems to be succesful: Replicating above error
Do you have an idea why this problem occurs? I could replicate the issue when i delete the 1=> FAIL | 2=> successI tested for subdomains too. The first try fails every time and second or more are successful. (While waiting for dns record propagation i could see the correct created TXT records in the customer-center.) Here are the logs for 3 test-subdomains. test1.lego-test.detest2.lego-test.detest3.lego-test.de |
It's more related to DNS propagation than a number of attempts.
This can be a propagation issue: the 2 TXT records are not propagated when we try to check them.
This means that the domain doesn't exist when checking it. So you need to try increasing the propagation timeout |
|
Ok i see and can confirm: it was the timeout, currently it was 1min. When increasing it to 3min it was successful after 69 seconds 👯 Do you need something else? |
|
I need the logs of a working run with a wildcard as in the issue description ( |
|
Maybe my latest comment was not clear: can you run again the command from the issue description? After that, if it's working, everything will be OK 🎉 |
|
Thank you for your effort on this. I appreciate it! $ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 21:18:24 Please review the TOS at https://letsencrypt.org/documents/LE-SA-v1.4-April-3-2024.pdf
Do you accept the TOS? Y/n
Y
2024/08/27 21:18:26 [INFO] acme: Registering account for [email protected]
!!!! HEADS UP !!!!
Your account credentials have been saved in your Let's Encrypt
configuration directory at "/root/admin-kram/docker/lego/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.
2024/08/27 21:18:26 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 21:18:27 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760865093
2024/08/27 21:18:27 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760865103
2024/08/27 21:18:27 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 21:18:27 [INFO] [lego-test.de] acme: Could not find solver for: tls-alpn-01
2024/08/27 21:18:27 [INFO] [lego-test.de] acme: Could not find solver for: http-01
2024/08/27 21:18:27 [INFO] [lego-test.de] acme: use dns-01 solver
2024/08/27 21:18:27 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:18:28 [INFO] [lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:18:29 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:18:29 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:18:31 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2024/08/27 21:18:31 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:18:33 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
...
2024/08/27 21:20:28 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:20:30 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:20:32 [INFO] [lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:20:32 [INFO] [lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:20:34 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2024/08/27 21:20:41 [INFO] [lego-test.de] The server validated our request
2024/08/27 21:20:41 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:20:42 [INFO] [lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:20:42 [INFO] Deactivating auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760865093
2024/08/27 21:20:42 [INFO] Skipping deactivating of valid auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760865103
2024/08/27 21:20:42 Could not obtain certificates:
error: one or more domains had a problem:
[*.lego-test.de] propagation: time limit exceeded: last error: NS ns01.agenturserver.co. did not return the expected TXT record [fqdn: _acme-challenge.lego-test.de., value: zmXhRUCAPsL_KIVXMDrxVOSzPr_nESskx8OLhfXjSes]: DXYgBpvE-SgkDV7n1MkAsv7mDOhs60aqH8GvKYYFiyY
$ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 21:21:41 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 21:21:42 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760865103
2024/08/27 21:21:42 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13760891523
2024/08/27 21:21:42 [INFO] [lego-test.de] acme: authorization already valid; skipping challenge
2024/08/27 21:21:42 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 21:21:42 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:21:43 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:21:43 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:21:45 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2024/08/27 21:21:49 [INFO] [*.lego-test.de] The server validated our request
2024/08/27 21:21:49 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:21:50 [INFO] [*.lego-test.de, lego-test.de] acme: Validations succeeded; requesting certificates
2024/08/27 21:21:50 [INFO] Wait for certificate [timeout: 30s, interval: 500ms]
2024/08/27 21:21:54 [INFO] [*.lego-test.de] Server responded with a certificate.Here my tests with timeout 20s: $ rm -rf .lego
$ export MITTWALD_PROPAGATION_TIMEOUT=20
$ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 21:42:25 No key found for account [email protected]. Generating a P256 key.
2024/08/27 21:42:25 Saved key to /root/admin-kram/docker/lego/lego/.lego/accounts/acme-staging-v02.api.letsencrypt.org/[email protected]/keys/[email protected]
2024/08/27 21:42:26 Please review the TOS at https://letsencrypt.org/documents/LE-SA-v1.4-April-3-2024.pdf
Do you accept the TOS? Y/n
Y
2024/08/27 21:42:28 [INFO] acme: Registering account for [email protected]
!!!! HEADS UP !!!!
Your account credentials have been saved in your Let's Encrypt
configuration directory at "/root/admin-kram/docker/lego/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.
2024/08/27 21:42:29 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 21:42:30 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761086993
2024/08/27 21:42:30 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761087003
2024/08/27 21:42:30 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 21:42:30 [INFO] [lego-test.de] acme: Could not find solver for: tls-alpn-01
2024/08/27 21:42:30 [INFO] [lego-test.de] acme: Could not find solver for: http-01
2024/08/27 21:42:30 [INFO] [lego-test.de] acme: use dns-01 solver
2024/08/27 21:42:30 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:42:30 [INFO] [lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:42:31 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:42:31 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:42:33 [INFO] Wait for propagation [timeout: 20s, interval: 2s]
2024/08/27 21:42:33 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:35 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:37 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:39 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:41 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:43 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:45 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:47 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:49 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:51 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:42:53 [INFO] [lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:42:53 [INFO] [lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:42:55 [INFO] Wait for propagation [timeout: 20s, interval: 2s]
2024/08/27 21:42:59 [INFO] [lego-test.de] The server validated our request
2024/08/27 21:42:59 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:42:59 [INFO] [lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:42:59 [INFO] Deactivating auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761086993
2024/08/27 21:43:00 [INFO] Skipping deactivating of valid auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761087003
2024/08/27 21:43:00 Could not obtain certificates:
error: one or more domains had a problem:
[*.lego-test.de] propagation: time limit exceeded: last error: NS ns01.agenturserver.co. did not return the expected TXT record [fqdn: _acme-challenge.lego-test.de., value: cmQ4lFQWebqFFKaQkW_lB4hesXiMedbAQWO6LRhiFN4]: ul77NxdZ-7y_h4hlBu0ZvViKILdkJiq3Lr8K1r1iSAs
$ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 21:44:19 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 21:44:19 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761087003
2024/08/27 21:44:19 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761100253
2024/08/27 21:44:19 [INFO] [lego-test.de] acme: authorization already valid; skipping challenge
2024/08/27 21:44:19 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 21:44:19 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:44:20 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:44:20 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:44:22 [INFO] Wait for propagation [timeout: 20s, interval: 2s]
2024/08/27 21:44:27 [INFO] [*.lego-test.de] The server validated our request
2024/08/27 21:44:27 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:44:27 [INFO] [*.lego-test.de, lego-test.de] acme: Validations succeeded; requesting certificates
2024/08/27 21:44:27 [INFO] Wait for certificate [timeout: 30s, interval: 500ms]
2024/08/27 21:44:29 [INFO] [*.lego-test.de] Server responded with a certificate.As mentioned before i could replicate that by deleting .lego folder. $ rm -rf .lego
$ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 21:46:48 No key found for account [email protected]. Generating a P256 key.
2024/08/27 21:46:48 Saved key to /root/admin-kram/docker/lego/lego/.lego/accounts/acme-staging-v02.api.letsencrypt.org/[email protected]/keys/[email protected]
2024/08/27 21:46:48 Please review the TOS at https://letsencrypt.org/documents/LE-SA-v1.4-April-3-2024.pdf
Do you accept the TOS? Y/n
Y
2024/08/27 21:46:50 [INFO] acme: Registering account for [email protected]
!!!! HEADS UP !!!!
Your account credentials have been saved in your Let's Encrypt
configuration directory at "/root/admin-kram/docker/lego/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.
2024/08/27 21:46:50 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 21:46:51 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761118203
2024/08/27 21:46:51 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761118213
2024/08/27 21:46:51 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 21:46:51 [INFO] [lego-test.de] acme: Could not find solver for: tls-alpn-01
2024/08/27 21:46:51 [INFO] [lego-test.de] acme: Could not find solver for: http-01
2024/08/27 21:46:51 [INFO] [lego-test.de] acme: use dns-01 solver
2024/08/27 21:46:51 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:46:51 [INFO] [lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 21:46:52 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:46:52 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:46:54 [INFO] Wait for propagation [timeout: 10m0s, interval: 2s]
2024/08/27 21:46:54 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:46:56 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
...
2024/08/27 21:56:50 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:56:52 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/27 21:56:54 [INFO] [lego-test.de] acme: Trying to solve DNS-01
2024/08/27 21:56:54 [INFO] [lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 21:56:56 [INFO] Wait for propagation [timeout: 10m0s, interval: 2s]
2024/08/27 21:57:04 [INFO] [lego-test.de] The server validated our request
2024/08/27 21:57:04 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:57:04 [INFO] [lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 21:57:04 [INFO] Deactivating auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761118203
2024/08/27 21:57:05 [INFO] Skipping deactivating of valid auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761118213
2024/08/27 21:57:05 Could not obtain certificates:
error: one or more domains had a problem:
[*.lego-test.de] propagation: time limit exceeded: last error: NS ns01.agenturserver.co. did not return the expected TXT record [fqdn: _acme-challenge.lego-test.de., value: qD_8RvY6JUaTdEV6cCFTmu8RygPDf2TjfaUqKM_3nSM]: L3befxVjqhagNXolMB6Hf5cabXjP9awyRAFhl_RL-ek
$ ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/27 22:07:39 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/27 22:07:40 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761118213
2024/08/27 22:07:40 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13761297293
2024/08/27 22:07:40 [INFO] [lego-test.de] acme: authorization already valid; skipping challenge
2024/08/27 22:07:40 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/27 22:07:40 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/27 22:07:41 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/27 22:07:41 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/27 22:07:43 [INFO] Wait for propagation [timeout: 10m0s, interval: 2s]
2024/08/27 22:07:49 [INFO] [*.lego-test.de] The server validated our request
2024/08/27 22:07:49 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/27 22:07:50 [INFO] [*.lego-test.de, lego-test.de] acme: Validations succeeded; requesting certificates
2024/08/27 22:07:50 [INFO] Wait for certificate [timeout: 30s, interval: 500ms]
2024/08/27 22:07:52 [INFO] [*.lego-test.de] Server responded with a certificate.If this is the expected behavior it's ok. Where can i assist you? If you want a demo we can make a videochat. |
|
Can you try to set the env var If this doesn't work, I will change the challenge to a sequential approach to see if this can improve the behavior. |
|
I tried with the env var, but nothing changed. Still 2 runs needed. |
|
before switching to the sequential approach, can you try the latest commit? |
You mean this 2e0d934 one? I tried it, didn't work for me. Behavior still the same. 2 runs needed. With the latest commit c8b0487 i got an error I changed the code to a sequential approach and it works: Here the changes i made: providers/dns/dns_providers.go providers/dns/mittwald/mittwald.go providers/dns/mittwald/mittwald.toml |
|
I updated the code with the sequential approach, can you run it again and give me the output? |
|
Thank you very much. As you can see it works now. $ make build
BIN_OUTPUT: dist/lego
rm -rf dist/ builds/ cover.out
Version: cf13ebea8c5b71ab7ff20d56bc0dfb486f2b7678
go build -trimpath -ldflags '-X "main.version=cf13ebea8c5b71ab7ff20d56bc0dfb486f2b7678"' -o dist/lego ./cmd/lego/
root@Server-Office:~/admin-kram/docker/lego/lego# export MITTWALD_TOKEN="REDACTED"
root@Server-Office:~/admin-kram/docker/lego/lego# ./dist/lego -m [email protected] --dns mittwald -d *.lego-test.de -d lego-test.de -s https://acme-staging-v02.api.letsencrypt.org/directory run
2024/08/30 13:07:14 No key found for account [email protected]. Generating a P256 key.
2024/08/30 13:07:14 Saved key to /root/admin-kram/docker/lego/lego/.lego/accounts/acme-staging-v02.api.letsencrypt.org/[email protected]/keys/[email protected]
2024/08/30 13:07:15 Please review the TOS at https://letsencrypt.org/documents/LE-SA-v1.4-April-3-2024.pdf
Do you accept the TOS? Y/n
Y
2024/08/30 13:07:16 [INFO] acme: Registering account for [email protected]
!!!! HEADS UP !!!!
Your account credentials have been saved in your Let's Encrypt
configuration directory at "/root/admin-kram/docker/lego/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.
2024/08/30 13:07:17 [INFO] [*.lego-test.de, lego-test.de] acme: Obtaining bundled SAN certificate
2024/08/30 13:07:17 [INFO] [*.lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13797909343
2024/08/30 13:07:17 [INFO] [lego-test.de] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/13797909353
2024/08/30 13:07:17 [INFO] [*.lego-test.de] acme: use dns-01 solver
2024/08/30 13:07:17 [INFO] [lego-test.de] acme: Could not find solver for: tls-alpn-01
2024/08/30 13:07:17 [INFO] [lego-test.de] acme: Could not find solver for: http-01
2024/08/30 13:07:17 [INFO] [lego-test.de] acme: use dns-01 solver
2024/08/30 13:07:17 [INFO] [*.lego-test.de] acme: Preparing to solve DNS-01
2024/08/30 13:07:18 [INFO] [*.lego-test.de] acme: Trying to solve DNS-01
2024/08/30 13:07:19 [INFO] [*.lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/30 13:07:29 [INFO] Wait for propagation [timeout: 2m0s, interval: 10s]
2024/08/30 13:07:29 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:07:39 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:07:49 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:07:59 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:08:09 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:08:19 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:08:29 [INFO] [*.lego-test.de] acme: Waiting for DNS record propagation.
2024/08/30 13:08:44 [INFO] [*.lego-test.de] The server validated our request
2024/08/30 13:08:44 [INFO] [*.lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/30 13:08:44 [INFO] sequence: wait for 2m0s
2024/08/30 13:10:44 [INFO] [lego-test.de] acme: Preparing to solve DNS-01
2024/08/30 13:10:45 [INFO] [lego-test.de] acme: Trying to solve DNS-01
2024/08/30 13:10:45 [INFO] [lego-test.de] acme: Checking DNS record propagation. [nameservers=127.0.0.53:53]
2024/08/30 13:10:55 [INFO] Wait for propagation [timeout: 2m0s, interval: 10s]
2024/08/30 13:11:00 [INFO] [lego-test.de] The server validated our request
2024/08/30 13:11:00 [INFO] [lego-test.de] acme: Cleaning DNS-01 challenge
2024/08/30 13:11:00 [INFO] [*.lego-test.de, lego-test.de] acme: Validations succeeded; requesting certificates
2024/08/30 13:11:00 [INFO] Wait for certificate [timeout: 30s, interval: 500ms]
2024/08/30 13:11:03 [INFO] [*.lego-test.de] Server responded with a certificate. |
|
I hope you enjoyed my work, please consider donating or asking your company to do so. |
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 @jotimann, can you run the command (with your domain, email, and credentials)?
-> #2200 (comment)
Closes #2177