Could not get certificate / dedyn.io

[PolkB]

Hi,
after setting up a separte Linux machine with Ubuntu 26.4.1 LTS I tried to setup Nextcloud AIO from the scratch.
As I don't have a domain yet, I have used during configuration the offered way to get a desec.io domain automatically.
Later, I was not able to get access to my Nextcloud instance with an SSL-PROTOCOL_ERROR (connection not safe).
In the CADDY PLUS GEOBLOCKING container I found the following messages:
http.acme_client","msg":"cleaning up solver","identifier":"XXXXXXXXXX.dedyn.io","challenge_type":"dns-01","error":"no memory of presenting a DNS record for "_acme-challenge.XXXXXX.dedyn.io" (usually OK if presenting also failed)"}
2026-09-02T15:15:51.255380567Z {"level":"error","ts":CCCCCCC.YYYYYYYY,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"XXXXXXXXX.dedyn.io","issuer":"acme-v02.api.letsencrypt.org-directory","error":"[XXXXXXXXXX.dedyn.io] solving challenges: presenting for challenge: adding temporary record for zone "XXXXXXXXX.dedyn.io.": retrieving RRSet: unexpected status code 401: {"detail":"Invalid token."} (order=https://acme-v02.api.letsencrypt.org/acme/order/CCCCCCCC/YYYYYYYYYY) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
I have no idea what to do to solve this problem. Search on Gitup gave a lot of hints but no solution.
Is there somebody who could help?

Thanks a lot
Bernd

[szaimen]

Hi, thanks a lot for the report! Looks like we were using an outdated desec plugin in the container. This should be addressed with szaimen/aio-caddy#179. You should be offered a new container update for caddy soon. Then please let me know if that fixes your problem!

[d-studer]

Hi.
I believe I have the same problem. My certificate expires in five days and it wont renew. I have also created my desec account upon setup of the nextcloud instance. I have not changed the password since, if that matters.

[FileStorage:/data/caddy] Lock for 'issue_cert_xxx.dedyn.io' is stale (created: 2026-10-11 12:34:12.126460934 +0200 CEST, last update: 2026-10-11 12:44:30.994685575 +0200 CEST); removing then retrying: /data/caddy/locks/issue_cert_xxx.dedyn.io.lock
2026-10-11T10:46:11.618017999Z {"level":"error","ts":1791715571.6178246,"logger":"http.acme_client","msg":"cleaning up solver","identifier":"xxx.dedyn.io","challenge_type":"dns-01","error":"no memory of presenting a DNS record for \"_acme-challenge.xxx.dedyn.io\" (usually OK if presenting also failed)"}
2026-10-11T10:46:11.826369436Z {"level":"error","ts":1791715571.8260849,"logger":"tls.renew","msg":"could not get certificate from issuer","identifier":"xxx.dedyn.io","issuer":"acme-v02.api.letsencrypt.org-directory","error":"[xxx.dedyn.io] solving challenges: presenting for challenge: adding temporary record for zone \"xxx.dedyn.io.\": retrieving RRSet: unexpected status code 401: {\"detail\":\"Invalid token.\"} (order=https://acme-v02.api.letsencrypt.org/acme/order/xxx) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2026-10-11T10:46:11.826400268Z {"level":"error","ts":1791715571.826123,"logger":"tls.renew","msg":"will retry","error":"[xxx.dedyn.io] Renew: [xxx.dedyn.io] solving challenges: presenting for challenge: adding temporary record for zone \"xxx.dedyn.io.\": retrieving RRSet: unexpected status code 401: {\"detail\":\"Invalid token.\"} (order=https://acme-v02.api.letsencrypt.org/acme/order/xxx) (ca=https://acme-v02.api.letsencrypt.org/directory)","attempt":1,"retrying_in":60,"elapsed":1.295344926,"max_duration":2592000}

Thank you!

[PolkB]

Hi Simon, thanks for your reply. It's working perfectly now . Am Mi., 2. Sept. 2026 um 18:50 Uhr schrieb Simon L. < ***@***.***>:

…

Hi, thanks a lot for the report! Looks like we were using an outdated desec plugin in the container. This should be addressed with szaimen/aio-caddy#179 <szaimen/aio-caddy#179>. You should be offered a new container update for caddy soon. Then please let me know if that fixes your problem! — Reply to this email directly, view it on GitHub <#8663?email_source=notifications&email_token=A77MLSAA56BFOA72LYRUVBL5NBFUPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGUZTIOJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18253499>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A77MLSB4S3DJNMQEIH44Z2L5NBFUPAVCNFSNUABIKJSXA33TNF2G64TZHM2DGMZTHAZTONRWHNCGS43DOVZXG2LPNY5TCMBXGM2TSMBSUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A77MLSBLADI3CD2ZAK6IY7D5NBFUPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGUZTIOJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/A77MLSHUCME6FBDPJIAHPWD5NBFUPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGUZTIOJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[szaimen]

Glad to hear! Thanks! :)