Add `account_activation_required` to /api/v1/instance
[akkoma] / installation / pleroma.nginx
1 # default nginx site config for Pleroma
2 #
3 # Simple installation instructions:
4 # 1. Install your TLS certificate, possibly using Let's Encrypt.
5 # 2. Replace 'example.tld' with your instance's domain wherever it appears.
6 # 3. Copy this file to /etc/nginx/sites-available/ and then add a symlink to it
7 # in /etc/nginx/sites-enabled/ and run 'nginx -s reload' or restart nginx.
8
9 proxy_cache_path /tmp/pleroma-media-cache levels=1:2 keys_zone=pleroma_media_cache:10m max_size=10g
10 inactive=720m use_temp_path=off;
11
12 server {
13 server_name example.tld;
14
15 listen 80;
16 listen [::]:80;
17
18 # Uncomment this if you need to use the 'webroot' method with certbot. Make sure
19 # that the directory exists and that it is accessible by the webserver. If you followed
20 # the guide, you already ran 'mkdir -p /var/lib/letsencrypt' to create the folder.
21 # You may need to load this file with the ssl server block commented out, run certbot
22 # to get the certificate, and then uncomment it.
23 #
24 # location ~ /\.well-known/acme-challenge {
25 # root /var/lib/letsencrypt/;
26 # }
27 location / {
28 return 301 https://$server_name$request_uri;
29 }
30 }
31
32 # Enable SSL session caching for improved performance
33 ssl_session_cache shared:ssl_session_cache:10m;
34
35 server {
36 server_name example.tld;
37
38 listen 443 ssl http2;
39 listen [::]:443 ssl http2;
40 ssl_session_timeout 5m;
41
42 ssl_trusted_certificate /etc/letsencrypt/live/example.tld/chain.pem;
43 ssl_certificate /etc/letsencrypt/live/example.tld/fullchain.pem;
44 ssl_certificate_key /etc/letsencrypt/live/example.tld/privkey.pem;
45
46 # Add TLSv1.0 to support older devices
47 ssl_protocols TLSv1.2;
48 # Uncomment line below if you want to support older devices (Before Android 4.4.2, IE 8, etc.)
49 # ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES";
50 ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";
51 ssl_prefer_server_ciphers on;
52 # In case of an old server with an OpenSSL version of 1.0.2 or below,
53 # leave only prime256v1 or comment out the following line.
54 ssl_ecdh_curve X25519:prime256v1:secp384r1:secp521r1;
55 ssl_stapling on;
56 ssl_stapling_verify on;
57
58 gzip_vary on;
59 gzip_proxied any;
60 gzip_comp_level 6;
61 gzip_buffers 16 8k;
62 gzip_http_version 1.1;
63 gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript application/activity+json application/atom+xml;
64
65 # the nginx default is 1m, not enough for large media uploads
66 client_max_body_size 16m;
67
68 location / {
69 proxy_http_version 1.1;
70 proxy_set_header Upgrade $http_upgrade;
71 proxy_set_header Connection "upgrade";
72 proxy_set_header Host $http_host;
73 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
74
75 # this is explicitly IPv4 since Pleroma.Web.Endpoint binds on IPv4 only
76 # and `localhost.` resolves to [::0] on some systems: see issue #930
77 proxy_pass http://127.0.0.1:4000;
78
79 client_max_body_size 16m;
80 }
81
82 location ~ ^/(media|proxy) {
83 proxy_cache pleroma_media_cache;
84 slice 1m;
85 proxy_cache_key $host$uri$is_args$args$slice_range;
86 proxy_set_header Range $slice_range;
87 proxy_http_version 1.1;
88 proxy_cache_valid 200 206 301 304 1h;
89 proxy_cache_lock on;
90 proxy_ignore_client_abort on;
91 proxy_buffering on;
92 chunked_transfer_encoding on;
93 proxy_pass http://127.0.0.1:4000;
94 }
95 }