Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
ERR_SSL_PROTOCOL_ERROR - Website not working Question Question
SSL set up gives "redirected you too many times." Question Question

Question

How to update Let's Encrypt certification

Posted March 1, 2018 4k views
Let's EncryptUbuntu 16.04

In Ubuntu server 16.04 with LAMP, I had installed Let’s encrypt certification follow this guide!

However, now the command certbot renew --dry-run messed up the server and I had to reboot it in order to get back to normal..

So my question is how can I update my certificate?

Thanks a lot!

Add a comment
yaylitzis
By:
yaylitzis

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
ERR_SSL_PROTOCOL_ERROR - Website not working Question Question
SSL set up gives "redirected you too many times." Question Question
Add a comment
2 comments
  • jasonjpeters March 1, 2018
    Reply Report

    When you do your renewal dry run, do your apache config files become modified or does it just turn apache off for a moment?

  • yaylitzis March 2, 2018
    Reply Report

    I am not sure if any files were modified. I noticed only that the site was not accessible with an error message like “connection is refused” and then I restarted my entire server.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
yaylitzis March 2, 2018
[deleted]
Reply Report
bobbyiliev August 19, 2019

Hello,

What I would suggest in this case is:

  • Schedule a maintenance window for your website and run the renewal again

  • If this takes down Apache again, what you need to do is to check your Apache error log at: /var/log/apache2/error.log and also run a config test with:

apachectl -t

This would point you to the error that is preventing Apache from starting.

If you are not sure you could paste your Apache config here along with some of the errors that you are seeing in the error log and the output of the apachectl -t config test.

Hope that this helps!
Regards,
Bobby

Reply Report

Related

Looking for something else?

Ask a new question Search for more help