CloudInsidr

Cyber security, infotech

  • Subscribe!
  • Privacy Policy
  • Legal
  • Contact Us

Join us on Twitter: @CloudInsidr

Follow us on Twitter: @cloudinsidr
  • news & alerts
    • events
    • industry analysis
    • industry gossip
    • people
  • cloud, edge & co.
    • AWS
    • administration & orchestration
      • web servers in the cloud
      • mail servers
      • databases
  • cybersec & warfare
    • encryption
  • blockchain
Home cloud, edge and everything in between administration and orchestration How to renew a Letsencrypt certificate
How to renew a Letsencrypt certificate

Anna E Kobylinska 2016-02-21 Leave a Comment

How to renew a Letsencrypt certificate

In a post titled How to Set Up Letsencrypt, the SSL-Certificate Engine for the Cloud Era of Hyperscale, on AWS EC2, we have introduced you to this free, open, and fully automated Certificate Authority backed by the likes of Facebook (a gold sponsor), and discussed a manual setup for adventurers in How to Use Letsencrypt across Servers in the Manual Configuration Mode with a CSR.

Now is the time to discuss how to extend the validity of a Letsencrypt certificate for up to another 90 days of blissful happiness.

So long as you keep the host names unchanged when renewing the certificate, your new certificate will be saved in the same location with a new version number, so that the previous certificate can be retained while a symlink makes sure that your server software will find it once it reloads its configuration files.

How to renew a Letsencrypt certificate without changing domains

Follow these steps to renew your Letsencrypt certificate.

Step 1. Stop your Web server

You must stop your web server to allow Letsencrypt to bind to port 80.

systemctl stop nginx
Step 2. Launch the Letsencrypt wizard

There are several ways to go about this. Here is the simplest of them all:

certbot renew

or you can also enforce the renewal if you like:

certbot renew --force-renewal

That’s it.

Renew Letsencrypt certificate
Renewing Letsencrypt certificate
Step 3. Verify the output and adjust configuration files in your server software if necessary

Pay close attention to the output this command generates. If the path differs from that of your old certificate, you web and mail servers will need some help in finding the new certificate.

Step 4. Start your web server and reload the config file of other applications

Start your web server, for example like this:

systemctl start nginx

Make sure that your server’s configuration file point to the correct location of your Letsencrypt certificate.

How to renew a Letsencrypt certificate with a new set of domains

If you need to change the set of domains when renewing your Letsencrypt certificate, follow all steps except Step 2 above. In Step 2, use the full command as follows:

letsencrypt certonly --server https://acme-v02.api.letsencrypt.org/directory -d host1.domain1.tld -d domain1.tld -d ...

Letsencrypt may remind you of your weekly allotment. Select option 2 to proceed.

Renewing a Letsencrypt certificate
Renewing a Letsencrypt certificate

Filed Under: administration and orchestration, cloud, edge and everything in between, cybersecurity and cyber warfare, encryption, mail servers, web servers in the cloud Tagged With: certificate, letsencrypt, SSL

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Subscribe

SSL/TLS Certificate Square (250 x 250)

Pearson Education (InformIT)

SSL/TLS Certificate Medium Rectangle (300 x 250)

Recent Posts

  • Upgrading from CentOS 6 to CentOS 7 and Beyond?
  • How To Figure Out Who is Signing In To Dovecot to Send or Retrieve Email
  • OpenSSH 9.9 Introduces Enhanced Quantum-Resistant Algorithms
  • OpenSSL 3.3 Final Release is now live!
  • How to Activate HTTP/2 with TLS 1.3 Encryption in NGINX for Secure Connections without a Performance Penalty
  • Is AWS sucking your budget dry? Strip it down to the nitty-gritty (without breaking stuff)
  • How to attach and mount an NVMe EBS volume on EC2
  • SELinux security contexts: correcting SELinux labels on a file system
  • Intel gobbling up Israeli Tower Semiconductor, Stock Goes Through The Roof
  • NGINX on AWS EC2: setting up a web server from scratch on a domain of your choice
  • Log4j RCE and mitigation techniques
  • Set up logrotate for Postfix

Symantec

Categories

  • administration and orchestration
  • alerts
  • AWS
  • Bitcoin
  • cloud, edge and everything in between
  • cryptocurrencies
  • cybersecurity and cyber warfare
  • databases
  • DNS
  • encryption
  • events
  • FinTech and InsurTech
  • homeland security
  • HTTP Security Headers
  • industries
  • industry analysis
  • industry gossip
  • Java
  • Linux
  • mail servers
  • networking
  • news
  • NGINX
  • people
  • php-fpm
  • reviews
  • SELinux
  • tips and tricks
  • Uncategorized
  • web servers in the cloud

Tags

AMI AWS AWS EBS Azure certificate cipher suites cryptography cyber defense cybersecurity cyber security Diffie-Hellman DNS DNS over HTTPS Dovecot EBS EC2 email encryption Fedora HTTP/2 HTTPS IBM letsencrypt Linux logs MariaDB MFA MySQL NGINX OpenSSL permissions php-fpm PHP 7 postfix RegEx Route 53 RSA SELinux SQL SSH SSL TLS TLS 1.3 TLS vulnerabilities WordPress

Archives

  • January 2025
  • November 2024
  • October 2024
  • May 2024
  • January 2023
  • March 2022
  • February 2022
  • December 2021
  • December 2020
  • November 2020
  • September 2020
  • January 2020
  • November 2019
  • August 2019
  • July 2019
  • April 2019
  • December 2018
  • October 2018
  • September 2018
  • August 2018
  • June 2018
  • May 2018
  • April 2018
  • February 2018
  • December 2017
  • November 2017
  • October 2017
  • August 2017
  • April 2017
  • February 2017
  • January 2017
  • November 2016
  • September 2016
  • August 2016
  • July 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • July 2015
  • February 2015

Recent Comments

    Wicked fast Networking (With a Government Clearance to Boot)

    ©2022 CybrAnalytiqa OÜ

    • Content purchasing and syndication