Difference between revisions of "HTTPS with Certbot (LetsEncrypt)"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== About == | == About == | ||
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 | ||
Revision as of 00:24, 13 May 2022
About
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 SSL to encrypt data being sent. You can watch this 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