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. https://crt.sh/?q=example.com ), so withholding your domain name here does not increase secr…

As far as dry run working/real run not working goes, this is most likely due to Let’s Encrypt caching a previous successful authorization. You can avoid that by deleting your staging account: mv /etc/letsencrypt/accounts/acme-staging-v02.api.letsencrypt.org \ /etc/letsencrypt/accounts/acme-stagin…

[image] _az: mv /etc/letsencrypt/accounts/acme-staging-v02.api.letsencrypt.org \ /etc/letsencrypt/accounts/acme-staging-v02.api.letsencrypt.org.bak Yes, both are now failing - so, how do I fix things? :smiley:

Hi @dulux-oz , Do you understand the various parts of this command that you're using? [image] dulux-oz: /usr/bin/certbot certonly --agree-tos --force-renewal --standalone --preferred-challenges http --http-01-port 54321 -d www.peregrineit.net in this case this says that you want Certbot to c…

Thanks @_az . In that case, I suspect that the haproxy configuration might be messed up or might be different in some way than it was when this certificate was originally issued.

Dry Run Working, Real Run Not

Help

_az July 14, 2019, 9:39pm 5

From their other thread, I believe OP is proxying through to 54321 from haproxy.

Topic		Replies	Views
Dry run without errors but actual run with errors Help	1	699	August 3, 2018
Dry-run works but real run doesn't Help	3	2365	February 23, 2018
Dry run fails to renew after succesfull generations of certificate Help	2	729	November 28, 2018
Dry run is success but fails on actual run Help	6	1093	April 10, 2020
Cannot renew --dry-run a certificate Help	14	1838	February 15, 2018

Dry Run Working, Real Run Not

Related topics