TrumpetX

What are you using for a reverse proxy? There’s some nginx websocket settings I had to do before things worked properly. I use cloudflare, but just for the DNS/cdn stuff, not their zero trust things.

server {
  server_name my.domain.com;
  client_max_body_size 2048M;

  location / {
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_pass http://10.10.10.30:13378/;  # My Wireguard Tunnel up to the VPS
    # proxy_cache_bypass  $http_upgrade; # This was added by Certbot
    # WebSocket support
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
  }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/my.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/my.domain.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

}
server {
    if ($host = my.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

  listen 80;
  listen [::]:80;

  server_name my.domain.com;
    return 404; # managed by Certbot
}

I don’t disagree with you, but for a single server hosting multiple projects with differing system dependencies, docker is amazing. I’ve come around to using it for this practical reason.

Using docker over direct installation always feels like an unnecessary interface layer that just complicates things and introduces points of failure.

This feels 1000% like a chatgpt prompt copy and pasted into a webpage.