Ja precis det är en sådan harang jag angett i serverblocket.
Men efter lite mer googlande så fann jag detta hos Letsencrypt.
If you are getting this message:
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
It is because Let’s Encrypt has currently disabled the TLS-SNI-01 challenge363 due to a security report. If you need to renew or issue a certificate right now, you should most likely use the HTTP-01 challenge. Certbot developer @bmw provided some helpful instructions1.3k, copied here for convenience:
If you’re serving files for that domain out of a directory on that server, you can run the following command:
sudo certbot --authenticator webroot --webroot-path <path to served directory> --installer nginx -d <domain>
If you’re not serving files out of a directory on the server, you can temporarily stop your server while you obtain the certificate and restart it after Certbot has obtained the certificate. This would look like:
sudo certbot --authenticator standalone --installer nginx -d <domain> --pre-hook "service nginx stop" --post-hook "service nginx start"
These hooks will cause Certbot to automatically stop your server to obtain certificates and then start it again. After running a command like this once, Certbot will remember your settings so certbot renew will work in the future.
For other people who find this issue, this affects some of our other plugins as well such as the Apache plugin. All the advice above is identical except you should replace nginx with apache in the different CLI options.
