Replies: 1 comment
-
@zombibly can you share your implementation details please ? I am trying to do the same with traefik |
Beta Was this translation helpful? Give feedback.
-
@zombibly can you share your implementation details please ? I am trying to do the same with traefik |
Beta Was this translation helpful? Give feedback.
-
hey everyone, in preparation for the 1.0 launch I've decided to prepare a dedicated server for me and my friends to play on when the game does release. I've got the server running in docker no problem and I'm able to hit it using my internal network IP (192.168.X.X). I was even able to get friends to be able to join when I opened up my router for all ports towards that internal IP. However I don't want to have those ports open all the time and wanted to limit the exposure by using nginx as a reverse proxy on an digital ocean vm.
I know that I've gotten the nginx setup for the most part as when I stop the docker container and run nc on the server for the 15777 port and try to add the server to the server manager using the digital ocean IP I can see that the traffic is making it's way to the server vm. The issue is that if I have the docker container running and try adding the server using the digital ocean IP then I just get a "Server appears to be offline" message. I'm not really sure what could be causing the issue.
TL:DR;
using public vm as a reverse proxy for server.
client -> public proxy -> server
confirmed that traffic is flowing to the server but getting a "server offline" message.
client -> server (using internal IP) OR (using public IP with port forwarding)
server appears online and everyone can connect without issues.
EDIT: I found my issue........ I had
proxy_responses 0;
set in the nginx facepalmBeta Was this translation helpful? Give feedback.
All reactions