\uc0ac\uc6a9\uae30\uac04\uc774 \uc81c\ud55c\ub41c \ubb34\ub8cc \uc0c1\uc5c5\uc6a9 ssl \uc778\uc99d\uc11c\ub97c \uc0ac\uc6a9\ud558\uac70\ub098 Self \uc778\uc99d\uc11c\ub97c \uc0ac\uc6a9\ud558\uc5ec \ubcf4\uc558\uc9c0\ub9cc \ubb34\ub8cc \uae30\uac04\uc774 \uc9c0\ub098\uba74 \uc0ac\uc6a9\ud558\uc9c0 \ubabb\ud558\uace0 \uc0ac\uc124 \uc778\uc99d\uc11c\ub294 \ube0c\ub77c\uc6b0\uc800\uc5d0\uc11c \uc81c\ub300\ub85c \uc0ac\uc6a9\ud558\uae30\uac00 \uc5b4\ub824\uc6e0\ub2e4.<\/p>\n\n\n\n
\ud574\uacb0 \ubc29\ubc95\uc744 \ucc3e\ub2e4\uac00 CertBot\uc744 \uc774\uc6a9\ud558\uc5ec \uc790\ub3d9\uc73c\ub85c \uac31\uc2e0\uae4c\uc9c0 \ud574\uc900\ub2e4\ub294 \ub0b4\uc6a9\uc744 \ubcf4\uace0 \uc801\uc6a9\ud574\ubcf4\uc558\ub2e4. \uadf8\ub7f0\ub370 \ub73b\ubc16\uc5d0\ub3c4 \ud06c\ub86c \ube0c\ub77c\uc6b0\uc800\uc5d0\uc11c \ubcc4\ub3c4\uc758 \uacbd\uace0 \uba54\uc2dc\uc9c0\ub3c4 \uc5c6\uc774 https \ub85c \ubc14\ub85c \uc870\ud68c\uac00 \ub41c\ub2e4.<\/p>\n\n\n\n
\ub9c8\uce58 \ud6a1\uc7ac\ub97c \ud55c \uae30\ubd84\uc73c\ub85c \ucc38\uc870\ud55c \uc0ac\uc774\ud2b8\ub97c \uc18c\uac1c\ud55c\ub2e4. \uc544\ub798 url link\uac00 \ucc38\uc870\ud55c \uc6d0\ubcf8 \uc0ac\uc774\ud2b8 \uc774\ub2e4. \uac00\ub054 \uc0ac\uc774\ud2b8\uac00 \uc0ac\ub77c\uc9c0\uac70\ub098 \ub2eb\ud788\ub294 \uacbd\uc6b0\uac00 \uc788\uc5b4 \ud398\uc774\uc9c0\uc758 \ub0b4\uc6a9\uc744 \ubcf5\uc0ac\ud574 \ub193\ub294\ub2e4. \uc774 \ub0b4\uc6a9\uc744 \ucc38\uc870\ud558\uace0\uc790 \ud55c\ub2e4\uba74 \uc544\ub798 \ub9c1\ud06c\ub97c \ud074\ub9ad\ud574\uc11c \uc6d0\ubcf8\uc744 \ucc38\uc870\ud558\uae30 \ubc14\ub780\ub2e4.
\uc544\ub798 \ubcf5\uc0ac\ud55c \ub0b4\uc6a9\uc740 \ubc31\uc5c5\uc744 \uc704\ud558\uc5ec \ubcf5\uc0ac\ud55c \uac83\uc73c\ub85c \ud3ec\ub9f7\ub3c4 \ubd88\ub7c9\uc774\uace0 \uc6d0\ubcf8 \ubcf4\ub2e4 \ubcf4\uae30\uac00 \uc88b\uc9c0 \uc54a\ub2e4.<\/p>\n\n\n\n
https:\/\/www.digitalocean.com\/community\/tutorials\/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-20-04<\/a><\/p>\n\n\n\n Let\u2019s Encrypt is a Certificate Authority (CA) that facilitates obtaining and installing free TLS\/SSL certificates<\/a>, 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.<\/p>\n\n\n\n In this guide, we\u2019ll use Certbot<\/a> to obtain a free SSL certificate for Apache on Ubuntu 20.04, and make sure this certificate is set up to renew automatically.<\/p>\n\n\n\n This tutorial uses a separate virtual host file instead of Apache\u2019s default configuration file for setting up the website that will be secured by Let\u2019s Encrypt. We recommend<\/a> creating new Apache virtual host files for each domain hosted in a server, because it helps to avoid common mistakes and maintains the default configuration files as a fallback setup.<\/p>\n\n\n\n To follow this tutorial, you will need:<\/p>\n\n\n\n In order to obtain an SSL certificate with Let\u2019s Encrypt, we\u2019ll first need to install the Certbot software on your server. We\u2019ll use the default Ubuntu package repositories for that.<\/p>\n\n\n\n We need two packages: Copy<\/p>\n\n\n\n You will be prompted to confirm the installation by pressing Certbot is now installed on your server. In the next step, we\u2019ll verify Apache\u2019s configuration to make sure your virtual host is set appropriately. This will ensure that the In order to be able to automatically obtain and configure SSL for your web server, Certbot needs to find the correct virtual host within your Apache configuration files. Your server domain name(s) will be retrieved from the If you followed the virtual host setup step in the Apache installation tutorial<\/a>, you should have a VirtualHost block set up for your domain at To check this up, open the virtual host file for your domain using Copy<\/p>\n\n\n\n Find the existing Copy<\/p>\n\n\n\n If you already have your If your current virtual host configuration doesn\u2019t match the example, update it accordingly. When you\u2019re done, save the file and quit the editor. Then, run the following command to validate your changes:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n You should get a Copy<\/p>\n\n\n\n With these changes, Certbot will be able to find the correct VirtualHost block and update it.<\/p>\n\n\n\n Next, we\u2019ll update the firewall to allow HTTPS traffic.<\/p>\n\n\n\n If you have the UFW firewall enabled, as recommended by the prerequisite guides, you\u2019ll need to adjust the settings to allow HTTPS traffic. Upon installation, Apache registers a few different UFW application profiles. We can leverage the Apache Full<\/strong> profile to allow both HTTP and HTTPS traffic on your server.<\/p>\n\n\n\n To verify what kind of traffic is currently allowed on your server, you can use:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n If you have followed one of our Apache installation guides, your output should look something like this, meaning that only HTTP traffic on port To additionally let in HTTPS traffic, allow the \u201cApache Full\u201d profile and delete the redundant \u201cApache\u201d profile:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n Your status will now look like this:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n You are now ready to run Certbot and obtain your certificates.<\/p>\n\n\n\n Certbot provides a variety of ways to obtain SSL certificates through plugins. The Apache plugin will take care of reconfiguring Apache and reloading the configuration whenever necessary. To use this plugin, type the following:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n This script will prompt you to answer a series of questions in order to configure your SSL certificate. First, it will ask you for a valid e-mail address. This email will be used for renewal notifications and security notices:<\/p>\n\n\n\n After providing a valid e-mail address, hit Next, you\u2019ll be asked if you would like to share your email with the Electronic Frontier Foundation to receive news and other information. If you do not want to subscribe to their content, type The next step will prompt you to inform Certbot of which domains you\u2019d like to activate HTTPS for. The listed domain names are automatically obtained from your Apache virtual host configuration, that\u2019s why it\u2019s important to make sure you have the correct You\u2019ll see output like this:<\/p>\n\n\n\n Next, you\u2019ll be prompted to select whether or not you want HTTP traffic redirected to HTTPS. In practice, that means when someone visits your website through unencrypted channels (HTTP), they will be automatically redirected to the HTTPS address of your website. Choose After this step, Certbot\u2019s configuration is finished, and you will be presented with the final remarks about your new certificate, where to locate the generated files, and how to test your configuration using an external tool that analyzes your certificate\u2019s authenticity:<\/p>\n\n\n\n Your certificate is now installed and loaded into Apache\u2019s configuration. Try reloading your website using You can use the SSL Labs Server Test<\/a> to verify your certificate\u2019s grade and obtain detailed information about it, from the perspective of an external service.<\/p>\n\n\n\n In the next and final step, we\u2019ll test the auto-renewal feature of Certbot, which guarantees that your certificate will be renewed automatically before the expiration date.<\/p>\n\n\n\n Let\u2019s Encrypt\u2019s certificates are only valid for ninety days. This is to encourage users to automate their certificate renewal process, as well as to ensure that misused certificates or stolen keys will expire sooner rather than later.<\/p>\n\n\n\n The To check the status of this service and make sure it\u2019s active and running, you can use:<\/p>\n\n\n\n Copy<\/p>\n\n\n\n You\u2019ll get output similar to this:<\/p>\n\n\n\n To test the renewal process, you can do a dry run with Copy<\/p>\n\n\n\n If you see no errors, you\u2019re all set. When necessary, Certbot will renew your certificates and reload Apache to pick up the changes. If the automated renewal process ever fails, Let\u2019s Encrypt will send a message to the email you specified, warning you when your certificate is about to expire.<\/p>\n\n\n\n In this tutorial, you\u2019ve installed the Let\u2019s Encrypt client \uc0ac\uc6a9\uae30\uac04\uc774 \uc81c\ud55c\ub41c \ubb34\ub8cc \uc0c1\uc5c5\uc6a9 ssl \uc778\uc99d\uc11c\ub97c \uc0ac\uc6a9\ud558\uac70\ub098 Self \uc778\uc99d\uc11c\ub97c \uc0ac\uc6a9\ud558\uc5ec \ubcf4\uc558\uc9c0\ub9cc \ubb34\ub8cc \uae30\uac04\uc774 \uc9c0\ub098\uba74 \uc0ac\uc6a9\ud558\uc9c0 \ubabb\ud558\uace0 \uc0ac\uc124 \uc778\uc99d\uc11c\ub294 \ube0c\ub77c\uc6b0\uc800\uc5d0\uc11c \uc81c\ub300\ub85c \uc0ac\uc6a9\ud558\uae30\uac00 \uc5b4\ub824\uc6e0\ub2e4. \ud574\uacb0 \ubc29\ubc95\uc744 \ucc3e\ub2e4\uac00 CertBot\uc744 \uc774\uc6a9\ud558\uc5ec \uc790\ub3d9\uc73c\ub85c \uac31\uc2e0\uae4c\uc9c0 \ud574\uc900\ub2e4\ub294 \ub0b4\uc6a9\uc744 \ubcf4\uace0 \uc801\uc6a9\ud574\ubcf4\uc558\ub2e4. \uadf8\ub7f0\ub370 \ub73b\ubc16\uc5d0\ub3c4 \ud06c\ub86c \ube0c\ub77c\uc6b0\uc800\uc5d0\uc11c \ubcc4\ub3c4\uc758 \uacbd\uace0 \uba54\uc2dc\uc9c0\ub3c4 … Continue reading Introduction<\/h3>\n\n\n\n
Prerequisites<\/h2>\n\n\n\n
your_domain<\/code> pointing to your server\u2019s public IP address.<\/li>www.your_domain<\/code> pointing to your server\u2019s public IP address.<\/li><\/ul><\/li>\/etc\/apache2\/sites-available\/your_domain.conf<\/code> as an example.<\/li><\/ul>\n\n\n\nStep 1 \u2014 Installing Certbot<\/h2>\n\n\n\n
certbot<\/code>, and python3-certbot-apache<\/code>. The latter is a plugin that integrates Certbot with Apache, making it possible to automate obtaining a certificate and configuring HTTPS within your web server with a single command.<\/p>\n\n\n\nsudo apt install certbot python3-certbot-apache\n<\/pre>\n\n\n\n
Y<\/code>, then ENTER<\/code>.<\/p>\n\n\n\ncertbot<\/code> client script will be able to detect your domains and reconfigure your web server to use your newly generated SSL certificate automatically.<\/p>\n\n\n\nStep 2 \u2014 Checking your Apache Virtual Host Configuration<\/h2>\n\n\n\n
ServerName<\/code> and ServerAlias<\/code> directives defined within your VirtualHost<\/code> configuration block.<\/p>\n\n\n\n\/etc\/apache2\/sites-available\/your_domain.conf<\/code> with the ServerName<\/code> and also the ServerAlias<\/code> directives already set appropriately.<\/p>\n\n\n\nnano<\/code> or your preferred text editor:<\/p>\n\n\n\nsudo nano \/etc\/apache2\/sites-available\/your_domain.conf\n<\/pre>\n\n\n\n
ServerName<\/code> and ServerAlias<\/code> lines. They should look like this:\/etc\/apache2\/sites-available\/your_domain.conf<\/p>\n\n\n\n...\nServerName your_domain\nServerAlias www.your_domain\n...<\/pre>\n\n\n\n
ServerName<\/code> and ServerAlias<\/code> set up like this, you can exit your text editor and move on to the next step. If you\u2019re using nano<\/code>, you can exit by typing CTRL+X<\/code>, then Y<\/code> and ENTER<\/code> to confirm.<\/p>\n\n\n\nsudo apache2ctl configtest\n<\/pre>\n\n\n\n
Syntax OK<\/code> as a response. If you get an error, reopen the virtual host file and check for any typos or missing characters. Once your configuration file\u2019s syntax is correct, reload Apache so that the changes take effect:<\/p>\n\n\n\nsudo systemctl reload apache2\n<\/pre>\n\n\n\n
Step 3 \u2014 Allowing HTTPS Through the Firewall<\/h2>\n\n\n\n
sudo ufw status\n<\/pre>\n\n\n\n
80<\/code> is currently allowed:<\/p>\n\n\n\nOutputStatus: active\n\nTo Action From\n-- ------ ----\nOpenSSH ALLOW Anywhere \nApache ALLOW Anywhere \nOpenSSH (v6) ALLOW Anywhere (v6) \nApache (v6) ALLOW Anywhere (v6)\n<\/pre>\n\n\n\n
sudo ufw allow 'Apache Full'\nsudo ufw delete allow 'Apache'\n<\/pre>\n\n\n\n
sudo ufw status\n<\/pre>\n\n\n\n
OutputStatus: active\n\nTo Action From\n-- ------ ----\nOpenSSH ALLOW Anywhere \nApache Full ALLOW Anywhere \nOpenSSH (v6) ALLOW Anywhere (v6) \nApache Full (v6) ALLOW Anywhere (v6) \n<\/pre>\n\n\n\n
Step 4 \u2014 Obtaining an SSL Certificate<\/h2>\n\n\n\n
sudo certbot --apache\n<\/pre>\n\n\n\n
OutputSaving debug log to \/var\/log\/letsencrypt\/letsencrypt.log\nPlugins selected: Authenticator apache, Installer apache\nEnter email address (used for urgent renewal and security notices) (Enter 'c' to\ncancel): you@your_domain\n<\/pre>\n\n\n\n
ENTER<\/code> to proceed to the next step. You will then be prompted to confirm if you agree to Let\u2019s Encrypt terms of service. You can confirm by pressing A<\/code> and then ENTER<\/code>:<\/p>\n\n\n\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nPlease read the Terms of Service at\nhttps:\/\/letsencrypt.org\/documents\/LE-SA-v1.2-November-15-2017.pdf. You must\nagree in order to register with the ACME server at\nhttps:\/\/acme-v02.api.letsencrypt.org\/directory\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n(A)gree\/(C)ancel: A\n<\/pre>\n\n\n\n
N<\/code>. Otherwise, type Y<\/code>. Then, hit ENTER<\/code> to proceed to the next step.<\/p>\n\n\n\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nWould you be willing to share your email address with the Electronic Frontier\nFoundation, a founding partner of the Let's Encrypt project and the non-profit\norganization that develops Certbot? We'd like to send you email about our work\nencrypting the web, EFF news, campaigns, and ways to support digital freedom.\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n(Y)es\/(N)o: N\n<\/pre>\n\n\n\n
ServerName<\/code> and ServerAlias<\/code> settings configured in your virtual host. If you\u2019d like to enable HTTPS for all listed domain names (recommended), you can leave the prompt blank and hit ENTER<\/code> to proceed. Otherwise, select the domains you want to enable HTTPS for by listing each appropriate number, separated by commas and\/ or spaces, then hit ENTER<\/code>.<\/p>\n\n\n\nWhich names would you like to activate HTTPS for?\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n1: your_domain\n2: www.your_domain\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nSelect the appropriate numbers separated by commas and\/or spaces, or leave input\nblank to select all options shown (Enter 'c' to cancel): \n<\/pre>\n\n\n\n
Obtaining a new certificate\nPerforming the following challenges:\nhttp-01 challenge for your_domain\nhttp-01 challenge for www.your_domain\nEnabled Apache rewrite module\nWaiting for verification...\nCleaning up challenges\nCreated an SSL vhost at \/etc\/apache2\/sites-available\/your_domain-le-ssl.conf\nEnabled Apache socache_shmcb module\nEnabled Apache ssl module\nDeploying Certificate to VirtualHost \/etc\/apache2\/sites-available\/your_domain-le-ssl.conf\nEnabling available site: \/etc\/apache2\/sites-available\/your_domain-le-ssl.conf\nDeploying Certificate to VirtualHost \/etc\/apache2\/sites-available\/your_domain-le-ssl.conf\n<\/pre>\n\n\n\n
2<\/code> to enable the redirection, or 1<\/code> if you want to keep both HTTP and HTTPS as separate methods of accessing your website.<\/p>\n\n\n\nPlease choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n1: No redirect - Make no further changes to the webserver configuration.\n2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for\nnew sites, or if you're confident your site works on HTTPS. You can undo this\nchange by editing your web server's configuration.\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nSelect the appropriate number [1-2] then [enter] (press 'c' to cancel): 2\n\n<\/pre>\n\n\n\n
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\nCongratulations! You have successfully enabled https:\/\/your_domain and\nhttps:\/\/www.your_domain\n\nYou should test your configuration at:\nhttps:\/\/www.ssllabs.com\/ssltest\/analyze.html?d=your_domain\nhttps:\/\/www.ssllabs.com\/ssltest\/analyze.html?d=www.your_domain\n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -\n\nIMPORTANT NOTES:\n - Congratulations! Your certificate and chain have been saved at:\n \/etc\/letsencrypt\/live\/your_domain\/fullchain.pem\n Your key file has been saved at:\n \/etc\/letsencrypt\/live\/your_domain\/privkey.pem\n Your cert will expire on 2020-07-27. To obtain a new or tweaked\n version of this certificate in the future, simply run certbot again\n with the \"certonly\" option. To non-interactively renew *all* of\n your certificates, run \"certbot renew\"\n - Your account credentials have been saved in your Certbot\n configuration directory at \/etc\/letsencrypt. You should make a\n secure backup of this folder now. This configuration directory will\n also contain certificates and private keys obtained by Certbot so\n making regular backups of this folder is ideal.\n - If you like Certbot, please consider supporting our work by:\n\n Donating to ISRG \/ Let's Encrypt: https:\/\/letsencrypt.org\/donate\n Donating to EFF: https:\/\/eff.org\/donate-le\n\n<\/pre>\n\n\n\n
https:\/\/<\/code> and notice your browser\u2019s security indicator. It should point out that your site is properly secured, typically by including a lock icon in the address bar.<\/p>\n\n\n\nStep 5 \u2014 Verifying Certbot Auto-Renewal<\/h2>\n\n\n\n
certbot<\/code> package we installed takes care of renewals by including a renew script to \/etc\/cron.d<\/code>, which is managed by a systemctl<\/code> service called certbot.timer<\/code>. This script runs twice a day and will automatically renew any certificate that\u2019s within thirty days of expiration.<\/p>\n\n\n\nsudo systemctl status certbot.timer\n<\/pre>\n\n\n\n
Output\u25cf certbot.timer - Run certbot twice daily\n Loaded: loaded (\/lib\/systemd\/system\/certbot.timer; enabled; vendor preset: enabled)\n Active: active (waiting) since Tue 2020-04-28 17:57:48 UTC; 17h ago\n Trigger: Wed 2020-04-29 23:50:31 UTC; 12h left\n Triggers: \u25cf certbot.service\n\nApr 28 17:57:48 fine-turtle systemd[1]: Started Run certbot twice daily.\n<\/pre>\n\n\n\n
certbot<\/code>:<\/p>\n\n\n\nsudo certbot renew --dry-run\n<\/pre>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
certbot<\/code>, configured and installed an SSL certificate for your domain, and confirmed that Certbot\u2019s automatic renewal service is active within systemctl<\/code>. If you have further questions about using Certbot, their documentation<\/a> is a good place to start.<\/p>\n","protected":false},"excerpt":{"rendered":"