Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA

These are four independent commands.
Please run them separately (and show their outputs separately):
ls -l /etc/letsencrypt/certbot.log
ls -l /var/log/letsencrypt/letsencrypt.log
grep -Ei 'fail|error' /etc/letsencrypt/certbot.log
grep -Ei ‘fail|error’ /etc/letsencrypt/letsencrypt.log

# ls -l /etc/letsencrypt/certbot.log -rw-r–r-- 1 root root 1906 Jan 9 2018 /etc/letsencrypt/certbot.log
# ls -l /var/log/letsencrypt/letsencrypt.log -rw-r–r-- 1 root root 190767 Jan 21 17:11 /var/log/letsencrypt/letsencrypt.log

# grep -Ei ‘fail|error’ /etc/letsencrypt/certbot.log raise errors.PluginSelectionError(msg.format(repr(previously), repr(now))) PluginSelectionError: Too many flags setting configurators/installers/authenticators ‘nginx’ -> ‘standalone’
# grep -Ei ‘fail|error’ /etc/letsencrypt/letsencrypt.log sh: 1: error’: not found

And again, for completeness:

grep -Ei ‘fail|error’ /var/log/letsencrypt/letsencrypt.log

2019-01-21 17:10:13,776:DEBUG:certbot.error_handler:Calling registered functions
“type”: “urn:ietf:params:acme:error:malformed”,
2019-01-21 17:10:16,617:DEBUG:acme.client:Error during a POST-as-GET request, your ACME CA may not support it:
urn:ietf:params:acme:error:malformed :: The request message was malformed :: Invalid Content-Type header on POST. Content-Type must be “application/jose+json”
2019-01-21 17:10:29,875:DEBUG:certbot.error_handler:Calling registered functions
“type”: “urn:ietf:params:acme:error:malformed”,
2019-01-21 17:10:34,794:DEBUG:acme.client:Error during a POST-as-GET request, your ACME CA may not support it:
urn:ietf:params:acme:error:malformed :: The request message was malformed :: Invalid Content-Type header on POST. Content-Type must be “application/jose+json”
2019-01-21 17:10:52,410:DEBUG:certbot.error_handler:Calling registered functions
“type”: “urn:ietf:params:acme:error:malformed”,
2019-01-21 17:10:56,146:DEBUG:acme.client:Error during a POST-as-GET request, your ACME CA may not support it:
urn:ietf:params:acme:error:malformed :: The request message was malformed :: Invalid Content-Type header on POST. Content-Type must be “application/jose+json”
2019-01-21 17:11:07,886:DEBUG:certbot.error_handler:Calling registered functions
“type”: “urn:ietf:params:acme:error:malformed”,
2019-01-21 17:11:10,539:DEBUG:acme.client:Error during a POST-as-GET request, your ACME CA may not support it:
urn:ietf:params:acme:error:malformed :: The request message was malformed :: Invalid Content-Type header on POST. Content-Type must be “application/jose+json”
2019-01-21 17:11:12,199:DEBUG:certbot.renewal:no renewal failures

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.