Now you need to concatenate the private and public keys and place them into the httpdocs/ssl directory of the ntopng # cat /etc/letsencrypt/live//privkey.pem /etc/letsencrypt/live//fullchain.pem >.SSLCertificateKeyFile /etc/letsencrypt/live//privkey.pem SSLCertificateFile /etc/letsencrypt/live//fullchain.pem At this point Let’s Encrypt has created the certificate and modified the Apache configuration adding the path of the generated certificates.Select the appropriate number then (press 'c' to cancel): 1Ĭongratulations! You have successfully enabled You can undo thisĬhange by editing your web server's configuration. New sites, or if you're confident your site works on HTTPS. Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.ġ: No redirect - Make no further changes to the webserver configuration.Ģ: Redirect - Make all requests redirect to secure HTTPS access. Plugins selected: Authenticator apache, Installer apacheĬreated an SSL vhost at /etc/apache2/sites-available/nfĭeploying Certificate to VirtualHost /etc/apache2/sites-available/nfĮnabling available site: /etc/apache2/sites-available/nf Saving debug log to /var/log/letsencrypt/letsencrypt.log Then type (as root) “certbot –apache -d ” as shown in the example # certbot -apache -d.Note that this host must have a public IP address and a web server installed such as Apache (with HTTP of course as we’re creating the certificate for HTTPS). Suppose that you want to run ntopng on a server named.
0 Comments
Leave a Reply. |