[HELP] No Traffic to 30120/udp on Hetzner

Hey guys,

so we´ve decided to setup a new FXServer Project on its own Dedicated at Hetzner.
I did set it up with Ubuntu 20.04 LTS mini and SSH, FTP, OLS+Cyberpanel are running fine,
the server is also reachable over the standard ports after pointing different domains to it,
only unfortunately we have massive problems with the accessibility of our FiveM server e.g. on the FiveM.Standard port 30120.

We have already carried out various tests for this, among other things with setting up/disabling the (HW-)Firewall in Robot, setting up ufw with corresponding port-rules for tcp/udp,
as well as accessibility tests via Telnet. None of them were successful.

No matter what we do, the server is not reachable from outside via port 30120,
even if lsof -i -P -n | grep LISTEN shows the corresponding port as listening.

The FiveM server is starting up correctly and sucessfully auths and sends Heartbeats to the License Server, but no signal reaches our Server back.

I’m really at my wit’s end and could use your advice. Thanks.

Does anyone else here host at Hetzner?

I recall something unusual being the case with ufw’s base netfilter rules really long ago, but it’s been a while since hearing this kind of issue.

What happens to the server’s functioning if you temporarily remove ufw’s rules by stopping it?

Even if the Hardware Firewall for the Server AND ufw are both disabled, it still wont work.

Trying to connect in FiveM via console gives me a 28 CURL timeout,
a Telnet test to that Port on our Server wont connect either.

My thought was, that since DDoS attacks to FiveM Servers are carried out via udp floods on 30120, they might have a standard zero routing on that port on udp, but I asked the support and they said that everything is working fine.

I host on VPSDime, i’ve never had to do any additional setup for iptables and port fowarding. Have you tried creating a support ticket with your hosting provider?

Do you try to create a support ticket with your hosting provider?

Yes, Support wont help, like I already wrote :tired_face:

Hey Guys,

its working fine now after installing Debian 10.5,
so the problem must have been within Ubuntu LTS 18.04./20.04,
even though ufw was completely disabled in both attempts.

I really would like to identify the problem, because I like Ubuntu
and hope someone can help on this one.