again… sorry for the confusion
again… sorry for the confusion
Very timely. That was exactly my problem. I’ll wait.
I appreciate there is a straightforward work around, and I also understand the security vulnerability as well as the importance of maintaining your ability to issue certificates.
However we’ve already deployed certbot with auto renewal across dozens of environments and hundreds of sites – do you recommend we switch everything over now or is there going to be an anticipated fix to restore original functionality?
Thank you for all your work?
A post was split to a new topic: Question about Certbot Apache autoconfiguration
It would be good if TLS-SNI were to be re-enabled at least on staging…
6 posts were split to a new topic: TLS-SNI disabled and only port 443 available
2 posts were split to a new topic: Problem with Certbot standalone plugin
To make this clear for me.
This means the letsencrypt/certbots apache module is now dead?
I can’t use --apache in the future?
Or is there a way that I can use the apache module with HTTP-01 challanges?
The standalone and the webroot modules have both downsides (server needs to be stopped or customer .htaccess can destroy the webroot way).
There is surely a way around this, but the apache module solves many problems for me in a good way.
Hi, I am little confused here … can anyone please suggest me correct solution on this?
I have following cron being executed on weekly basis:
sudo /opt/letsencrypt/certbot-auto renew --renew-hook “service apache2 reload” >> /var/log/certbot-renew.log && sudo service postfix restart && sudo service dovecot restart
But now it started returning me this error:
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
Attempting to renew cert (somedomain.cz) from /etc/letsencrypt/renewal/somedomain.cz.conf produced an unexpected error: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA… Skipping.
Additional error displayed is:
All renewal attempts failed. The following certs could not be renewed:
_ /etc/letsencrypt/live/somedomain.cz/fullchain.pem (failure)_
Should I update my cron command somehow or it is needed to call some command for each domain on server separately to resolve this issue?
Thank you very much for any help.
Work is in progress: Help test Certbot Apache and Nginx fixes for TLS-SNI-01 outage
Well… If you wait until the next Certbot release, this might be managed easily, or at least with less effort.
Otherwise, the primary way to change renewal options is, yes, to run the command you used to create each certificate, modified with the new options.
You can try to edit Certbot’s configuration files, but they’re undocumented and you have to be careful.
Thank you for reply, I have additional question related to:
…modified with the new options.
You can try to edit Certbot’s configuration file…
Does exist any guide for this, how it should be modified or what additional options should be added into my cron call?
The first post in this thread has examples of what Certbot commands to use.
For example, if you used “
certbot --apache -d example.com -d www.example.com” before, you might use “
certbot --authenticator webroot --installer apache --webroot-path /var/www/example.com/public_html -d example.com -d www.example.com”, if that’s how your web server is configured.
We can’t say anything precise without knowing more about how the web server is configured and what commands were used before.
There isn’t a guide for editing the files, no. I don’t recommend it, especially in a thread with thousands of views.
Just to say that this worked for me for apache (centos 7 variety):
The example above shows a regular domain, a domain with the www, and a sub-domain in the command.
Please replace yourdomain.com with the domain you plan on using.
Thank you community.
I am in the process of setting up Let’s Encrypt docker for unraid to be able to access my other dockers remotely.
I am relatively new to setting up the docker and unraid and am learning as I go along.
Question I have is where do I run these commands. Do i need to add them to a config file somewhere and if so which file is it and where would I find it.
Thanks in advance.
For this, update your docker, and there should be a variable called HTTPVAL under advanced set to false (if it isn’t create it… Add path port or variable) set this variable to true and restart the docker.
This should set the linuxserver.io letsencrypt docker to use http-01 instead of TLS-SNI-01.
Awesome thanks, very helpful.
Here’s what I did for a apache vhost in case someone wonders:
sudo certbot --authenticator webroot --webroot-path /var/www/example.com/public_html --installer apache -d example.com
Thank you very much for your help! Doing the above got rid of the error.
However, I am now getting the following errors:
certbot: error: argument --cert-path: No such file or directory
It then tries to generate a nw certificate but gets the following warning:
Failed authorization procedure. .duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://.duckdns.org/.well-known/acme-challenge/3_oQRrYeXN7Wuuz280qP2hErIiQoCgKlo2FSE2Kagmg: Timeout
And is then followed by this error:
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
Any further suggestions on how to resolve this?
I am using a different local port then port 80.
I have already setup port forwarding on my router.
Any help would be much appreciated.