aboutsummaryrefslogtreecommitdiff
path: root/content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md')
-rw-r--r--content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md b/content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md
index e3075e7..dc77365 100644
--- a/content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md
+++ b/content/weblog/2018-08-12_ssl-with-lets-encrypt/index.md
@@ -34,7 +34,7 @@ configuration on nginx for that. We need to do this so that Let's Encrypt's
server can read the challenge generated by Certbot and verify that we indeed
own the domain(s) for which we want to make the certificate.
-```nginx
+```
server {
listen 80 default_server;
listen [::]:80 default_server;
@@ -74,7 +74,7 @@ redirect plain old insecure http requests to https. You should also put the
correct path for your certificate and public key under `ssl_certificate` and
`ssl_certificate_key` respectively.
-```nginx
+```
server {
listen 80;
listen [::]:80;