[GH-ISSUE #1923] Server works on Linode, but fails on DigitalOcean #1513

New issue

Closed

opened 2026-02-27 02:57:32 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:57:32 +03:00

Owner

Originally created by @ghost on GitHub (Jun 18, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1923

I have been struggling to host a Project Zomboid server for about a week now with my DigitalOcean droplet. I get to the point where I can see the server in the browser, but get a P2P connection error when anyone tries to join. This is on an 18.04 Ubuntu x64 DigitalOcean droplet.

My friend was able to successfully get it working, to my frustration, on his older 16.04 Ubuntu x64 setup. I tried doing the same on a fresh 16.04 Ubuntu x64 setup to no avail.

I've had a running ticket with DigitalOcean to try all sorts of things, including opening proper ports... or disabling ufw and flushing all iptables rules and accepting all incoming, outgoing and forwarding. Still, the issue persists.

I've created a fresh Linode Ubuntu 18.04 x64 and a DigitalOcean Ubuntu 18.04 x64 droplet and ran them side by side, performing all the same steps. The Linode one always works, the DigitalOcean always fails. that video can be seen here. https://www.youtube.com/watch?v=tTiKMJG3eVg

I'm so very perplexed about this issue, especially since my friend with a DigitalOcean droplet was able to do it on his.

raziaar@hexacow-server:/etc$ sudo ufw status
Status: inactive
raziaar@hexacow-server:/etc$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
raziaar@hexacow-server:/etc$

Originally created by @ghost on GitHub (Jun 18, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1923 I have been struggling to host a Project Zomboid server for about a week now with my DigitalOcean droplet. I get to the point where I can see the server in the browser, but get a P2P connection error when anyone tries to join. This is on an 18.04 Ubuntu x64 DigitalOcean droplet. My friend was able to successfully get it working, to my frustration, on his older 16.04 Ubuntu x64 setup. I tried doing the same on a fresh 16.04 Ubuntu x64 setup to no avail. I've had a running ticket with DigitalOcean to try all sorts of things, including opening proper ports... or disabling ufw and flushing all iptables rules and accepting all incoming, outgoing and forwarding. Still, the issue persists. I've created a fresh Linode Ubuntu 18.04 x64 and a DigitalOcean Ubuntu 18.04 x64 droplet and ran them side by side, performing all the same steps. The Linode one always works, the DigitalOcean always fails. that video can be seen here. https://www.youtube.com/watch?v=tTiKMJG3eVg I'm so very perplexed about this issue, especially since my friend with a DigitalOcean droplet was able to do it on his. ``` raziaar@hexacow-server:/etc$ sudo ufw status Status: inactive raziaar@hexacow-server:/etc$ sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination raziaar@hexacow-server:/etc$ ```

kerem

2026-02-27 02:57:32 +03:00

closed this issue
added the
outcome: wrong forum
label

kerem commented

2026-02-27 02:57:33 +03:00

Author

Owner

@ghost commented on GitHub (Jun 18, 2018):

Note, that I've also gone and opened all the ports for zomboid and steam previously. My goal was to open everything up like the base ubuntu on Linode(no port forwarding steps).

@ghost commented on GitHub (Jun 18, 2018): Note, that I've also gone and opened all the ports for zomboid and steam previously. My goal was to open everything up like the base ubuntu on Linode(no port forwarding steps).

kerem commented

2026-02-27 02:57:33 +03:00

Author

Owner

@ghost commented on GitHub (Jun 18, 2018):

Here is DigitalOcean support basically saying they can't determine anything wrong based on information I've provided them over a fairly lengthy service ticket.

Hello,

Thank you for contacting DigitalOcean!

I am sorry for the trouble caused to you here!

I see no issues with your Droplet or the Platform either. I would recommend you to reach out to the app vendor here:https://linuxgsm.com/support/ or if you have any server application logs, please provide it to us and we can take a look at it. As an un-managed service provider, we have no access to Droplets which means we have no visibility to figure out what happens within the Droplet which also means that we won’t be able to log into your Droplet and perform any actions on your behalf. We rely on the inputs we get from you like server log output, troubleshooting steps you followed, screenshot of configuration file etc.

Please feel free to reach out to us via this ticket if you have further queries or concerns, we will be around to help you out!

LinuxGSM
Support – LinuxGSM
There are various ways to get help and support with LinuxGSM. Including wiki, steam group and discord

@ghost commented on GitHub (Jun 18, 2018): Here is DigitalOcean support basically saying they can't determine anything wrong based on information I've provided them over a fairly lengthy service ticket. > Hello, > > Thank you for contacting DigitalOcean! > > I am sorry for the trouble caused to you here! > > I see no issues with your Droplet or the Platform either. I would recommend you to reach out to the app vendor here:https://linuxgsm.com/support/ or if you have any server application logs, please provide it to us and we can take a look at it. As an un-managed service provider, we have no access to Droplets which means we have no visibility to figure out what happens within the Droplet which also means that we won’t be able to log into your Droplet and perform any actions on your behalf. We rely on the inputs we get from you like server log output, troubleshooting steps you followed, screenshot of configuration file etc. > > Please feel free to reach out to us via this ticket if you have further queries or concerns, we will be around to help you out! <blockquote><img src="http://gameservermanagers.com/wp-content/uploads/2015/08/lgsm-full-dark.png" width="48" align="right"><div>LinuxGSM</div><div><strong><a href="https://linuxgsm.com/support/">Support – LinuxGSM</a></strong></div><div>There are various ways to get help and support with LinuxGSM. Including wiki, steam group and discord</div></blockquote>

kerem commented

2026-02-27 02:57:33 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jun 18, 2018):

Read the link you just posted.
Also don't use too fresh or non final distro.

@UltimateByte commented on GitHub (Jun 18, 2018): Read the link you just posted. Also don't use too fresh or non final distro.

kerem commented

2026-02-27 02:57:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 2, 2021):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Jun 2, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.