Can't Connect to the server ARK Google Cloud

[Kasty123]

Can't Connect to the server, i would need your help with the Ark Server, server is installed and it looks like it is working properly (everything is green and i got a link on ARK server List where i can see these server as ONLINE) but when i try to connect everytime i will get Timed Out and this repeated on Steam or Epic version of game... :(

https://arkservers.net/server/34.90.112.67:27015

Hope dev could help me with that issue :) Have a nice day

[klightspeed]

Is the server on the same network as the machine you're trying to connect from? If the router does not support loopback routing, then you will have difficulty connecting to the server from behind the router.

[Kasty123]

The server is on the Google Cloud server, and i allow needed ports in firewall

[klightspeed]

In my experience, it will time out when the client is initially installing the mods. Do you already have the mods installed on your client?

Edit: though it looks like the server is not responding on port 7778

[Kasty123]

Allowed ports:

[Kasty123]

And i didn't have installed any mods in the ARK, is vanilla from Epic Games

[klightspeed]

If you are able to get a shell into the VM, does netstat -antup show something like:

udp        0      0 0.0.0.0:7778             0.0.0.0:*                           ShooterGameSe

[Kasty123]

When i use this command it show me a lot of things and some of them are below udp 0 0 0.0.0.0:7778 0.0.0.0: 16379/ShooterGameSe udp 0 0 0.0.0.0:7779 0.0.0.0: 16379/ShooterGameSe udp 0 0 0.0.0.0:27015 0.0.0.0: 16379/ShooterGameSe udp 0 0 0.0.0.0:52819 0.0.0.0:

[klightspeed]

I am out of ideas. The server is listening, but either the incoming packets aren't reaching it on port 7778, it is ignoring those packets, or the outgoing responses are being blocked.

[klightspeed]

If you are able to install tcpdump on the vm, try running:

tcpdump -n -i any udp and ip host {your-ip-address}

and then try connecting to the server from your Steam copy of the game.

If you only have the Epic version of the game, make sure you have arkflag_crossplay=true in your arkmanager instance config. In this case, I think it uses an Epic proprietary peer to peer protocol that does not use the Steam ports, using the Epic servers to control connections.

tcpdump options:

• -n: do not resolve addresses
• -i any: monitor all interfaces
• udp and ip host xx.xx.xx.xx: filter capture to UDP traffic between the VM and your IP address

[Kasty123]

It looks like i can found my ip address in that but what it mean ?

14:13:24.186606 IP 85.x.x.x.52963 > 10.164.0.5.27015: UDP, length 9

[klightspeed]

That single line would be the client asking the server what its settings are.

From the Cloud NAT guide https://cloud.google.com/nat/docs/overview#specs-stun-turn:

If Endpoint-Independent Mapping is enabled, Cloud NAT is compatible with common NAT traversal protocols such as STUN and TURN, if you deploy your own STUN or TURN servers:

[Kasty123]

Sorry but i'm not smart from your last comment, what do i do ?

[Kasty123]

And there's more from last command

14:13:02.514802 IP 155.133.248.39.27024 > 10.164.0.5.7779: UDP, length 36 14:13:02.867978 IP 82.74.31.248.62785 > 10.164.0.5.27015: UDP, length 25 14:13:02.876842 IP 10.164.0.5.27015 > 82.74.31.248.62785: UDP, length 249 14:13:02.931427 IP 82.74.31.248.62788 > 10.164.0.5.27015: UDP, length 9 14:13:02.975304 IP 10.164.0.5.27015 > 82.74.31.248.62788: UDP, length 9 14:13:03.616729 IP 127.0.0.1.48513 > 127.0.0.1.27015: UDP, length 25 14:13:03.663914 IP 127.0.0.1.27015 > 127.0.0.1.48513: UDP, length 249 14:13:05.031853 IP 82.74.31.248.62955 > 10.164.0.5.27015: UDP, length 9 14:13:05.041061 IP 10.164.0.5.27015 > 82.74.31.248.62955: UDP, length 9 14:13:05.070779 IP 82.74.31.248.62955 > 10.164.0.5.27015: UDP, length 9 14:13:05.090366 IP 10.164.0.5.27015 > 82.74.31.248.62955: UDP, length 446 14:13:07.700019 IP 127.0.0.1.53718 > 127.0.0.53.53: 10942+ [1au] A? logging.googleapis.com. (51) 14:13:07.700045 IP 127.0.0.1.53718 > 127.0.0.53.53: 16034+ [1au] AAAA? logging.googleapis.com. (51) 14:13:07.700333 IP 10.164.0.5.39831 > 169.254.169.254.53: 58182+ [1au] A? logging.googleapis.com. (51) 14:13:07.700449 IP 10.164.0.5.58155 > 169.254.169.254.53: 48265+ [1au] AAAA? logging.googleapis.com. (51) 14:13:07.924540 IP 169.254.169.254.53 > 10.164.0.5.58155: 48265 1/0/1 AAAA 2a00:1450:4013:c04::5f (79) 14:13:07.924540 IP 169.254.169.254.53 > 10.164.0.5.39831: 58182 1/0/1 A 173.194.79.95 (67) 14:13:07.924777 IP 127.0.0.53.53 > 127.0.0.1.53718: 10942 1/0/1 A 173.194.79.95 (67) 14:13:07.924856 IP 127.0.0.53.53 > 127.0.0.1.53718: 16034 1/0/1 AAAA 2a00:1450:4013:c04::5f (79) 14:13:08.731322 IP 127.0.0.1.57786 > 127.0.0.1.27015: UDP, length 25 14:13:08.778678 IP 127.0.0.1.27015 > 127.0.0.1.57786: UDP, length 249 14:13:11.140056 IP 10.164.0.5.7779 > 155.133.248.39.27024: UDP, length 84 14:13:13.594330 IP 82.74.31.248.56243 > 10.164.0.5.27015: UDP, length 25 14:13:13.599414 IP 10.164.0.5.27015 > 82.74.31.248.56243: UDP, length 249 14:13:13.655569 IP 82.74.31.248.56244 > 10.164.0.5.27015: UDP, length 9 14:13:13.697863 IP 10.164.0.5.27015 > 82.74.31.248.56244: UDP, length 9 14:13:13.846929 IP 127.0.0.1.52603 > 127.0.0.1.27015: UDP, length 25 14:13:13.894691 IP 127.0.0.1.27015 > 127.0.0.1.52603: UDP, length 249 14:13:15.841398 IP 82.74.31.248.56462 > 10.164.0.5.27015: UDP, length 9 14:13:15.862137 IP 10.164.0.5.27015 > 82.74.31.248.56462: UDP, length 9 14:13:18.049611 IP 82.74.31.248.56705 > 10.164.0.5.27015: UDP, length 9 14:13:18.075536 IP 10.164.0.5.27015 > 82.74.31.248.56705: UDP, length 9 14:13:18.961430 IP 127.0.0.1.54002 > 127.0.0.1.27015: UDP, length 25 14:13:19.010121 IP 127.0.0.1.27015 > 127.0.0.1.54002: UDP, length 249 14:13:20.141860 IP 10.164.0.5.7779 > 155.133.248.39.27024: UDP, length 84 14:13:20.204983 IP 82.74.31.248.56901 > 10.164.0.5.27015: UDP, length 9 14:13:20.240242 IP 10.164.0.5.27015 > 82.74.31.248.56901: UDP, length 9 14:13:23.979867 IP 85.x.x.x.52962 > 10.164.0.5.27015: UDP, length 25 14:13:24.027139 IP 10.164.0.5.27015 > 85.x.x.x.52962: UDP, length 249 14:13:24.078073 IP 127.0.0.1.48523 > 127.0.0.1.27015: UDP, length 25 14:13:24.082731 IP 85.x.x.x.52963 > 10.164.0.5.27015: UDP, length 9 14:13:24.125629 IP 127.0.0.1.27015 > 127.0.0.1.48523: UDP, length 249 14:13:24.125724 IP 10.164.0.5.27015 > 85.x.x.x.52963: UDP, length 9 14:13:24.186606 IP 85.x.x.x.52963 > 10.164.0.5.27015: UDP, length 9 14:13:24.224158 IP 10.164.0.5.27015 > 85.x.x.x.52963: UDP, length 446 14:13:28.681938 IP 167.114.64.74.59113 > 10.164.0.5.27015: UDP, length 25 14:13:28.699627 IP 10.164.0.5.27015 > 167.114.64.74.59113: UDP, length 249 14:13:28.788824 IP 167.114.64.74.59113 > 10.164.0.5.27015: UDP, length 15 14:13:28.798079 IP 10.164.0.5.27015 > 167.114.64.74.59113: UDP, length 9 14:13:28.886664 IP 167.114.64.74.59113 > 10.164.0.5.27015: UDP, length 9 14:13:28.896561 IP 10.164.0.5.27015 > 167.114.64.74.59113: UDP, length 6 14:13:28.985261 IP 167.114.64.74.59113 > 10.164.0.5.27015: UDP, length 9 14:13:28.995008 IP 10.164.0.5.27015 > 167.114.64.74.59113: UDP, length 446 14:13:29.142781 IP 10.164.0.5.7779 > 155.133.248.39.27024: UDP, length 84 14:13:29.193747 IP 127.0.0.1.37768 > 127.0.0.1.27015: UDP, length 25 14:13:29.241166 IP 127.0.0.1.27015 > 127.0.0.1.37768: UDP, length 249 14:13:29.514199 IP 155.133.248.39.27024 > 10.164.0.5.7779: UDP, length 36

[klightspeed]

OK - that looks like you ran tcpdump either without any options or only with -i any, so it captured all traffic between your server and everywhere else.

I can see absolutely no traffic on port 7778 in that trace, suggesting something is blocking it before it reaches your server.

One possible option is to change the ark_Port from 7778 to e.g. 27778, and forward port 27778 in your cloud router config.

[Kasty123]

Now i tried to allow all ports incoming or outcoming and with the same output, nowhere to see port 7778

[Kasty123]

I done something in the firewall and it worked for Steam but for the Epic version it didnt work

And is that in the config file written correctly?

[Kasty123]

It is working properly now, setting was correct, the issue was in the Enforcement (it was set to Disabled) setting in the firewall

Thank you so much for help :)