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

[stockmind]

certbot/certbot#5405

Just to let you know, I get this error when I try to obtain a Let's Encrypt certificate using your container.

Due to latest changes in Let's Encrypt bot the command that worked for me to get a certificate was (inside the container):

certbot --authenticator standalone --installer apache -d <domain.tld> -d <www.domain.tld> --pre-hook "apachectl stop" --post-hook "apachectl start"

Be sure to launch container with -e APACHE_ENABLE_PORT_80=true and -p 80:80 or the challenge will fail

[greyltc]

Thanks for the heads up

I'll work on changing the documentation to reflect this

[greyltc]

BTW, did you see this issue when following the instructions in the wiki https://github.com/greyltc/docker-LAMP/wiki/Using-the-built-in-certbot-client-to-fetch-proper-ssl-certificate-files-from-Let's-Encrypt ?

[stockmind]

Thank you, i've seen that but if the HTTP ports are busy you cannot use certbot for the first certificate retrieve and you need the port 80 enabled to let the challenge complete.. also i'm not using this container anymore, i've switched to that piece of cake of Caddy, auto let's encrypt, virtual host idiot-proof, xss protection, cors everything out-of-the box and easily configurable with a footprint in ram of 40mb.. it's heaven

[jorgeas80]

@stockmind that sounds amazing. Could you provide a link, please?

I guess you're talking about this --> https://github.com/mholt/caddy, but not sure

[stockmind]

Yeah, you are right! https://caddyserver.com/

There Is a nice docker
https://github.com/abiosoft/caddy-docker