Permalink
90 lines (75 sloc) 3.57 KB
# This is an example nginx config used to serve your Sandstorm server over SSL/TLS/HTTPS.
#
# Definitions like these should go in the "http" block of your nginx config. Replace "example.com"
# with the domain of your Sandstorm install. On a Debian/Ubuntu system, you can copy this into
# /etc/nginx/sites-enabled/.
# This magic stanza is ESSENTIAL to avoid breaking WebSockets.
#
# Specifically, for WebSocket forwarding, we want to forward the `Connection` header.
# This "map" declaration helps with that.
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
# The following stanza does a HTTP -> HTTPS redirect.
server {
listen 80;
server_name example.com *.example.com;
return 301 https://$host$request_uri$is_args$args;
}
# Configuration for Sandstorm shell and apps, over HTTPS.
server {
listen 443;
server_name example.com *.example.com;
ssl on;
ssl_certificate /etc/nginx/ssl/sandstorm.crt;
ssl_certificate_key /etc/nginx/ssl/sandstorm.key;
ssl_session_timeout 5m;
# Configure SSL with forward secrecy and other goodies.
# Ciphersuite taken from https://wiki.mozilla.org/Security/Server_Side_TLS
# "Intermediate compatibility" as of 2015-06-04
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;
ssl_prefer_server_ciphers on;
# HSTS prevents attackers from tricking you into connecting via HTTP in the
# future, but if you actually intend to access the server via non-SSL in the
# future then you should probably delete this line.
add_header Strict-Transport-Security max-age=31536000;
location / {
proxy_pass http://127.0.0.1:6080;
# Forward the Host header, which is used to route requests for
# static content published from Sandstorm apps.
proxy_set_header Host $http_host;
# Forward WebSocket.
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Real-IP $remote_addr;
}
# Allow large spk uploads from the /install form and allow grains to receive large uploads.
client_max_body_size 1024m;
}
### The following commented-out configuration works for HTTP reverse proxying, if
### for some reason you can't use HTTPS. In that case, remove the HTTP->HTTPS
### redirect config stanza above.
# server {
# listen 80;
# server_name example.com *.example.com;
#
# location / {
# proxy_pass http://127.0.0.1:6080;
#
# # Forward the Host header, which is used to route requests for
# # static content published from Sandstorm apps.
# proxy_set_header Host $http_host;
#
# # Forward WebSocket.
# proxy_http_version 1.1;
# proxy_set_header Upgrade $http_upgrade;
# proxy_set_header Connection $connection_upgrade;
# proxy_set_header X-Real-IP $remote_addr;
# }
#
# # Allow large spk uploads from the /install form and allow grains to receive large uploads.
# client_max_body_size 1024m;
# }