Securing a web server using HTTPS not only gives you encryption but also guarantees that the request reaches the destination without being compromised.
The request crosses over a lot of network paths to reach the destination, and if not secured (using HTTP), its content can be changed or it can be redirected to another server without knowing it.
With a well configured HTTPS server, using a public Web-Of-Trust, you have this assurance.
This post will briefly cover how Letsencrypt works, and how to configure Nginx to handle the ACME challenge protocol. Also, we will see how to tell Nginx to redirect all HTTP traffic to HTTPS, and will use safe SSL/TLS Ciphers parameters.