I played a bit with the nginx configuration and managed to do it a bit more simply, using a single "input" port:
NGINX:
server {
server_name example.com;
location /login {
proxy_pass http://localhost:5000;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
location /game {
proxy_pass http://localhost:5001;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
listen [::]:443 ssl; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
and further as in the example post, i.e. two screens with the websockify commands:
Code:
websockify -v 5000 1.2.3.4:7171
websockify -v 5001 1.2.3.4:7172
This way, in the client you can use
example.com/login with port 443, and in the response as the server address (or hardcode in the client in Lua)
example.com/game, which by default will also connect to port 443.
