Pour SWAG PROXY MANAGER LetsEncrypt Certbot rejette l’enregistrement DNS TXT pour un certificat joker

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:*.xxx.duckdns.org

I ran this command: demande de certificat

It produced this output: Encountered exception during recovery: certbot.errors.PluginError: The TXT value for domain "xxx.duckdns.org" could not be deleted.
Request status code: 200
Request response text: KO
The TXT update "KO" for domain "isJ1NA4QZwITWc5PFciovml_pO4EPB2tt7A_MPXwV3c" could not be set.

My web server is (include version):Linuxserver.io version : 5.8.0-ls495

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:duckdns.org

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

I think you should ask about that on the SWAG support forum.

That error is from the DNS plugin used for a wildcard cert. SWAG uses a program called Certbot to request certs. But, the duckdns DNS plugin comes from a third party. Further, coordinating the configuration of your container, and this plugin, and your server is all done by SWAG.

The error is a result of some configuration error.

This section of the SWAG doc relates to this setup: SWAG - LinuxServer.io

Someone else here may have some experience to share. But, please post your full domain name. It is very difficult to debug these kinds of errors without the full name.

3

Merci pour ton retour :+1:
je suis encore novice dans ce monde informatique
Comme tu le suggère je vais aller sur le forum linuxserver.io.
Mais concernant mon erreur de configuration, j'ai des doutes car tout fonctionnait jusqu'à la semaine dernière lorsque j'ai mis à jour le conteneur swag.