Nginx reverse proxy with Tomcat - WebSocet connection not being served correctly

Heya,

Based on your description and configuration, I have some suggestions to improve your Nginx configuration.

• Use alias instead of root for the /static/ location block. This is because alias is used when the URL path and the file system path don’t match exactly.

• Add a trailing slash to the proxy_pass directive for the /api/ and /ws/ location blocks. This helps in avoiding any potential routing issues.

• Add the X-Forwarded-For header to pass along the client’s IP address to the Tomcat application. This can be helpful for logging and debugging purposes.

• Add proxy_http_version 1.1; to the /ws/ location block to ensure that the WebSocket connection uses HTTP/1.1.

Now, I haven’t exactly tested it just because it’s hard to recreate your setup exactly but I think this should do the trick:

http {
    upstream tomcat_server {
        server domain1.com:8080;
    }

    server {
        listen 80;
        server_name domain1.com;

        location /static/ {
            alias /path/to/static/files;
        }

        location / {
            proxy_pass http://tomcat_server;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }

        location /api/ {
            proxy_pass http://tomcat_server/api/;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }
    }

    server {
        listen 80;
        server_name domain2.com;

        location /ws/ {
            proxy_pass http://tomcat_server/ws/;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_http_version 1.1;
        }
    }
}

If you still encounter any issues, please provide more details about the specific errors or problems you’re facing, and we can further help you troubleshoot the issue.