Install ssl certificate in linux

How To Secure Nginx with Let’s Encrypt on Ubuntu 20.04

Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free TLS/SSL certificates, thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated on both Apache and Nginx.

In this tutorial, you will use Certbot to obtain a free SSL certificate for Nginx on Ubuntu 20.04 and set up your certificate to renew automatically.

This tutorial will use a separate Nginx server configuration file instead of the default file. We recommend creating new Nginx server block files for each domain because it helps to avoid common mistakes and maintains the default files as a fallback configuration.

Prerequisites

To follow this tutorial, you will need:

• One Ubuntu 20.04 server set up by following this initial server setup for Ubuntu 20.04 tutorial, including a sudo-enabled non-root user and a firewall.
• A registered domain name. This tutorial will use example.com throughout. You can purchase a domain name from Namecheap, get one for free with Freenom, or use the domain registrar of your choice.
• Both of the following DNS records set up for your server. If you are using DigitalOcean, please see our DNS documentation for details on how to add them.
  • An A record with example.com pointing to your server’s public IP address.
  • An A record with www. example.com pointing to your server’s public IP address.

  Step 1 — Installing Certbot

  The first step to using Let’s Encrypt to obtain an SSL certificate is to install the Certbot software on your server.

  Install Certbot and it’s Nginx plugin with apt :

  Certbot is now ready to use, but in order for it to automatically configure SSL for Nginx, we need to verify some of Nginx’s configuration.

  Step 2 — Confirming Nginx’s Configuration

  Certbot needs to be able to find the correct server block in your Nginx configuration for it to be able to automatically configure SSL. Specifically, it does this by looking for a server_name directive that matches the domain you request a certificate for.

  If you followed the server block set up step in the Nginx installation tutorial, you should have a server block for your domain at /etc/nginx/sites-available/ example.com with the server_name directive already set appropriately.

  To check, open the configuration file for your domain using nano or your favorite text editor:

  Find the existing server_name line. It should look like this:

  . server_name example.com www.example.com; . 

  If it does, exit your editor and move on to the next step.

  If it doesn’t, update it to match. Then save the file, quit your editor, and verify the syntax of your configuration edits:

  If you get an error, reopen the server block file and check for any typos or missing characters. Once your configuration file’s syntax is correct, reload Nginx to load the new configuration:

  Certbot can now find the correct server block and update it automatically.

  Next, let’s update the firewall to allow HTTPS traffic.

  Step 3 — Allowing HTTPS Through the Firewall

  If you have the ufw firewall enabled, as recommended by the prerequisite guides, you’ll need to adjust the settings to allow for HTTPS traffic. Luckily, Nginx registers a few profiles with ufw upon installation.

  You can see the current setting by typing:

  It will probably look like this, meaning that only HTTP traffic is allowed to the web server:

  Output
  Status: active To Action From -- ------ ---- OpenSSH ALLOW Anywhere Nginx HTTP ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) Nginx HTTP (v6) ALLOW Anywhere (v6) 

  To additionally let in HTTPS traffic, allow the Nginx Full profile and delete the redundant Nginx HTTP profile allowance:

  Your status should now look like this:

  Output
  Status: active To Action From -- ------ ---- OpenSSH ALLOW Anywhere Nginx Full ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) Nginx Full (v6) ALLOW Anywhere (v6) 

  Next, let’s run Certbot and fetch our certificates.

  Step 4 — Obtaining an SSL Certificate

  Certbot provides a variety of ways to obtain SSL certificates through plugins. The Nginx plugin will take care of reconfiguring Nginx and reloading the config whenever necessary. To use this plugin, type the following:

  This runs certbot with the —nginx plugin, using -d to specify the domain names we’d like the certificate to be valid for.

  If this is your first time running certbot , you will be prompted to enter an email address and agree to the terms of service. After doing so, certbot will communicate with the Let’s Encrypt server, then run a challenge to verify that you control the domain you’re requesting a certificate for.

  If that’s successful, certbot will ask how you’d like to configure your HTTPS settings.

  Output
  Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: No redirect - Make no further changes to the webserver configuration. 2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for new sites, or if you're confident your site works on HTTPS. You can undo this change by editing your web server's configuration. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number 1 then [enter] (press 'c' to cancel): 

  Select your choice then hit ENTER . The configuration will be updated, and Nginx will reload to pick up the new settings. certbot will wrap up with a message telling you the process was successful and where your certificates are stored:

  Output
  IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/example.com/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/example.com/privkey.pem Your cert will expire on 2020-08-18. To obtain a new or tweaked version of this certificate in the future, simply run certbot again with the "certonly" option. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le 

  Your certificates are downloaded, installed, and loaded. Try reloading your website using https:// and notice your browser’s security indicator. It should indicate that the site is properly secured, usually with a lock icon. If you test your server using the SSL Labs Server Test, it will get an A grade.

  Let’s finish by testing the renewal process.

  Step 5 — Verifying Certbot Auto-Renewal

  Let’s Encrypt’s certificates are only valid for ninety days. This is to encourage users to automate their certificate renewal process. The certbot package we installed takes care of this for us by adding a systemd timer that will run twice a day and automatically renew any certificate that’s within thirty days of expiration.

  You can query the status of the timer with systemctl :

  Output
  ● certbot.timer - Run certbot twice daily Loaded: loaded (/lib/systemd/system/certbot.timer; enabled; vendor preset: enabled) Active: active (waiting) since Mon 2020-05-04 20:04:36 UTC; 2 weeks 1 days ago Trigger: Thu 2020-05-21 05:22:32 UTC; 9h left Triggers: ● certbot.service 

  To test the renewal process, you can do a dry run with certbot :

  If you see no errors, you’re all set. When necessary, Certbot will renew your certificates and reload Nginx to pick up the changes. If the automated renewal process ever fails, Let’s Encrypt will send a message to the email you specified, warning you when your certificate is about to expire.

  Conclusion

  In this tutorial, you installed the Let’s Encrypt client certbot , downloaded SSL certificates for your domain, configured Nginx to use these certificates, and set up automatic certificate renewal. If you have further questions about using Certbot, the official documentation is a good place to start.

  Want to easily configure a performant, secure, and stable Nginx server? Try our free open-source Nginx tool.

  Источник

  Classic SysAdmin: How to Install an SSL Certificate on Linux Server

  With Security being the top most priority in the e-commerce world, the importance of SSL Certificates has skyrocketed. Installing an SSL Certificate on an online portal has become the basic foundation of a company’s business structure.

  But the question is ‘How to install an SSL Certificate on a server?’

  It is not necessary that everyone who is into e-commerce has a technical background. E-commerce is all about business and the owners are mostly businessmen. So also the core team of an e-commerce industry is not fully technical. In such a situation it becomes very difficult for people with minimal technical knowledge to grasp concepts even as basic like SSL Certificates or its installation for that matter.

  This article aims at giving a sneak peek into the process of installing an SSL Certificate on Linux server in lay man’s words. This would help the non-technical people also to get a grasp of what it is all about. Of course, every e-commerce company has a core technical team, so they can easily take over from here. But it is always good to have a know-how of the process.

  The installation of SSL Certificates on a Linux server is very easy. It can be done using a Plesk control panel and also without it.

  What is Plesk?

  It is a web hosting platform that has a very simple configuration. This simple configuration helps all web hosting providers to manage a lot of virtual hosts easily and on a single server. Ever since its conception, Plesk has been coming up as a preferred choice for all the web hosting companies.

  How to install an SSL certificate on a Linux Server that has Plesk

  1. First Log into the control panel of Plesk.

  3. The third step implies choosing the domain to be updated.

  4. In the next step click on the ‘Add New Certificate’ icon.

  5. Save the certificate name in the ‘Certificate Name’ box.

  One would have the certificate and key files saved on the local computer. These certificate and key files are provided by the certificate authority and are important for the installation.

  6. The next step is to find these files. Open these in a Notepad or in other similar text formats from where one can copy the text.

  7. Copy the entire text of the files.

  8. Paste them in the correct boxes. Reading through the content and the box name in Plesk will give one an idea where to paste it.

  9. Next, click on the ‘Send Text’ button.

  10. Go to the ‘Hosting Section’. It is on the domain screen.

  11. Click ‘Set-up’ from this section. A drop down list will follow.

  12. The next step is to click on the ‘new certificate’ from the drop down list.

  How to install SSL Certificate on Linux servers that do not have Plesk

  1. The first and foremost step is to upload the certificate and important key files. One can upload the files to the server using – S/FTP.

  2. Login to Server. It is important to log in via SSH. Logging in via SSH will help the user to become the root user.

  4. One can see /etc/httpd/conf/ssl.crt in the following step. Move the certificate file here

  5. Next move key file also to /etc/httpd/conf/ssl.crt

  It is important to ensure the security of the files that has been moved. One can keep the files secure by restricting permission. Using ‘chmod 0400’ will help users to securely restrict permission to the key.

  6. Next Go to etc/httpd/conf.d/ssl.conf. Here the user will find Virtual Host Configuration set up for the domain.

  7. Edit Virtual Host Configuration.

  The technicality of installing an SSL certificate may baffle many non-technical people, but once one gets a hang of it, it becomes easy.

  Ready to continue your Linux journey? Check out our free intro to Linux course!

  Источник

  Читайте также:  Time in seconds linux