I fixed the problem from the nginx conf (reverse proxy that connects to the container) giving the correct ip, with the most relevant as like:
proxy_redirect off; proxy_pass https://example.com:25655; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Request-Start "t=${msec}"; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; #proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-NginX-Proxy true; proxy_read_timeout 90; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";
About the existing users I don’t remember if was they fixed, but there were just a few users while the site was in construction, what I can say is that using this conf for nginx-reverse proxy makes it working properly ![]()