X-Git-Url: http://git.squeep.com/?a=blobdiff_plain;f=installation%2Fpleroma.nginx;h=de380a6ca5efa449f129186d8b872f2afa467e0a;hb=9d487ba57949a4102aa2eb67b26842f1c0ef418c;hp=a3d55e4bff785db6bb9a8b88c5e4af67f1f553e3;hpb=04b1c135543965860029557fc216eb38fd63b6c7;p=akkoma diff --git a/installation/pleroma.nginx b/installation/pleroma.nginx index a3d55e4bf..de380a6ca 100644 --- a/installation/pleroma.nginx +++ b/installation/pleroma.nginx @@ -11,8 +11,9 @@ proxy_cache_path /tmp/pleroma-media-cache levels=1:2 keys_zone=pleroma_media_cac server { server_name example.tld; + listen 80; - return 301 https://$server_name$request_uri; + listen [::]:80; # Uncomment this if you need to use the 'webroot' method with certbot. Make sure # that the directory exists and that it is accessible by the webserver. If you followed @@ -21,18 +22,24 @@ server { # to get the certificate, and then uncomment it. # # location ~ /\.well-known/acme-challenge { - # root /var/lib/letsencrypt/.well-known/acme-challenge; + # root /var/lib/letsencrypt/; # } + location / { + return 301 https://$server_name$request_uri; + } } # Enable SSL session caching for improved performance ssl_session_cache shared:ssl_session_cache:10m; server { + server_name example.tld; + listen 443 ssl http2; + listen [::]:443 ssl http2; ssl_session_timeout 5m; - ssl_trusted_certificate /etc/letsencrypt/live/example.tld/fullchain.pem; + ssl_trusted_certificate /etc/letsencrypt/live/example.tld/chain.pem; ssl_certificate /etc/letsencrypt/live/example.tld/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.tld/privkey.pem; @@ -48,8 +55,6 @@ server { ssl_stapling on; ssl_stapling_verify on; - server_name example.tld; - gzip_vary on; gzip_proxied any; gzip_comp_level 6; @@ -66,7 +71,9 @@ server { proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; - proxy_pass http://localhost:4000; + # this is explicitly IPv4 since Pleroma.Web.Endpoint binds on IPv4 only + # and `localhost.` resolves to [::0] on some systems: see issue #930 + proxy_pass http://127.0.0.1:4000; client_max_body_size 16m; }