HTTPS with Certbot (LetsEncrypt) - Revision history

Lchristopherson at 19:43, 30 May 2022

2022-05-30T19:43:37Z

← Older revision		Revision as of 19:43, 30 May 2022
Line 15:		Line 15:

	== Installation ==		== Installation ==
	To begin, verify that the website that you'd like to open HTTPS is valid and up on the World Wide Web.		To begin, verify that the website that you'd like to open HTTPS is valid and up on the World Wide Web. This just means having a working [[Nginx]] domain set up. You can view how to add a new Nginx Domain/Subdomain [[Adding a New Domain or Subdomain\|here]].

			To install Certbot, you will run the commands <code>sudo apt-get install certbot</code> and <code>sudo apt-get install python-certbot-nginx</code>, to install Certbot for our specific server setup. Once this is done, you will be able to create an HTTPS certificate for any website running.

			== Creating an Nginx HTTPS Certificate ==
			To create a new HTTPS certificate, you may run <code>sudo certbot</code>. This command will bring up a list of all of the available domains on the webserver, and number them, you will choose a number and it will install the certificate. It is as simple as that!

			Another way to install a certificate is to run <code>sudo certbot --nginx -d domain.com</code> where <code>domain.com</code> is the name of the domain that you want to add.

			=== Verification ===
			To verify if the HTTPS domain is valid, run <code>sudo nginx -t</code> to check for any server config file errors. If that test returns successful, navigate to the website in your web browser of choice (Google Chrome), and check for the little lock next to the name of the website, if that has appeared, you have successfully installed Certbot onto that domain.

			== Removing an Nginx HTTPS Certificate ==
			To remove a certificate from a domain, you will run the command <code>sudo certbot delete</code>. Like the command to create a certificate, this will bring up a list of all of the certificates available numbered. You will enter the number of the certificate, and it will be removed, it's that simple.

			=== Verification ===
			To verify you didn't break everything like I (Luke), have done multiple times, you will run <code>sudo nginx -t</code>. If this test returns successful, you may navigate to your web browser of choice (Google Chrome), and check next to the URL for a sign that says "Not Secure". This will complete the deletion of a certificate.

			== Notes ==
			'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''

			'''Extra Note:''' '''All Certbot certificates should auto-renew every 90 days.'''

Lchristopherson at 14:56, 18 May 2022

2022-05-18T14:56:55Z

← Older revision		Revision as of 14:56, 18 May 2022
Line 6:		Line 6:

	By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot provides a very simple way to create and apply these certificates to ensure a secure connection.		By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot provides a very simple way to create and apply these certificates to ensure a secure connection.

			== Pre-requisites ==

			* Linux Ubuntu
			* Working Nginx Webserver
			* Running server block/website on Port 80 (HTTP)
			* Sudo privileges

			== Installation ==
			To begin, verify that the website that you'd like to open HTTPS is valid and up on the World Wide Web.

Lchristopherson at 00:31, 13 May 2022

2022-05-13T00:31:40Z

← Older revision		Revision as of 00:31, 13 May 2022
Line 2:		Line 2:

	== About ==		== About ==
			[[File:Certbot logo.png\|left\|thumb\|231x231px]]
	When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)\|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.		When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)\|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

	By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple		By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot provides a very simple way to create and apply these certificates to ensure a secure connection.

Lchristopherson at 00:24, 13 May 2022

2022-05-13T00:24:44Z

← Older revision		Revision as of 00:24, 13 May 2022
Line 2:		Line 2:

	== About ==		== About ==
	~~[[File:Certbot.png\|left\|thumb\|126x126px]]~~
	When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)\|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.		When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)\|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

	By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple		By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple

Lchristopherson at 00:23, 13 May 2022

2022-05-13T00:23:45Z

← Older revision		Revision as of 00:23, 13 May 2022
Line 1:		Line 1:
	[[Category:Webserver]]		[[Category:Webserver]]

			== About ==
			[[File:Certbot.png\|left\|thumb\|126x126px]]
			When the internet first started, all of the websites ran on an insecure port 80, which is also known as HTTP. There were quite a few issues with this, like when a packet of data would be sent to a server with sensitive information, an outside attacker could listen and take that data. HTTPS uses and encrypted protocol called [[Three Letter Acronym (TLA)\|SSL]] to encrypt data being sent. You can watch this [https://www.youtube.com/watch?v=0PHCAdw6Z8w&ab_channel=SecurityMetrics%2CInc. video] for more information on the subject.

			By default, [[Nginx]] runs on port 80, which is insecure HTTP, this is something that should be fixed before making the site public. To enable HTTPS, every site needs its own certificate, although they can be very hard and tedious to create manually, which is why we utilize the free program Certbot! Certbot is a very simple

Lchristopherson: Created page with "Category:Webserver"

2022-04-12T15:11:19Z

Created page with "Category:Webserver"

New page

[[Category:Webserver]]