certbot-dns-schlundtech icon indicating copy to clipboard operation
certbot-dns-schlundtech copied to clipboard

Can't create certificate without 2FA

Open stephan-schuster opened this issue 2 years ago • 4 comments

We created sucessfully a wildcard certificate some months ago without using 2FA. When I try to renew the certificate I get the following message:

Missing property in credentials configuration file /etc/letsencrypt/schlund.ini:
 * Property "dns_schlundtech_token" not found (should be the 2FA token to use, optional).

When I add the missing property with a random value (because we don't use 2FA) Schlundtech reports, that the zone can't be found:

Encountered exception during recovery: certbot.errors.PluginError: Unable to find a SchlundTech zone for example.de
Unable to find a SchlundTech zone for example.de

We used the following command to initialy create the certificate:

certbot certonly --server https://acme-v02.api.letsencrypt.org/directory -a dns-schlundtech --dns-schlundtech-credentials /etc/letsencrypt/schlund.ini --dns-schlundtech-propagation-seconds 60 --domains *.example.de --email [email protected]

I'm wondering, how we could create the certificate initialy with success? Is there a way to renew the certificate without enabling the 2FA at Schlundtech?

stephan-schuster avatar Jul 05 '23 08:07 stephan-schuster

Same issue here, with 2FA enabled and a token provided in th credential file...

DonOtuseGH avatar Jul 28 '23 07:07 DonOtuseGH

Had the same problem. The config variable need to be set, in order to get this to work (yes, the error says it is "optional", but it is not). Set it to "None", so the code ignores it afterward.

dns_schlundtech_token = None

f0086 avatar Dec 11 '24 22:12 f0086

@f0086 unfortunately this didn't do the trick, the error remains the same...

Encountered exception during recovery: certbot.errors.PluginError: Unable to find a SchlundTech zone for domain.de

stephan-schuster avatar Dec 12 '24 08:12 stephan-schuster

it seems to me this is a non-2fa related issue. even with the older version 0.04.0 I'm getting this error :(

update: I got it working with 2FA now at least. not sure what I did wrong, maybe the one off token just expired

an-tex avatar Jan 06 '25 10:01 an-tex