Connection timed out / CURL error code 28
A player could not reach your server in time. Either their connection, or your ports, or your server being too busy to answer.
Do this first
If nobody can join, check UDP port 30120 is open. If it is one player, it is their network.
What it means
The client sent a request and got no answer in time. Either it never reached the server, or the server was too busy to answer. CURL error 28 is specifically a timeout, not a refusal — a refusal would say so.
What causes it
Ordered by how often it is the answer.
- 1
Ports not forwarded
TCP AND UDP 30120. UDP is the one that gets missed, and a TCP-only forward gives exactly this: the list works, the join times out.
- 2
The server is overloaded
A server pinned at 100% CPU stops answering handshakes. If existing players are also rubber-banding, this is it.
- 3
The player's IP is blocked
By an anticheat, a firewall rule, or a host-level ban list.
- 4
A NAT or gateway problem on the player's side
Double NAT, a VPN, or a carrier-grade NAT.
- 5
Simply distance
A player across an ocean on a bad route can exceed the handshake window.
How to tell which one is yours
Can anyone else join right now? If yes, it is that player's network. If nobody can, check the server's CPU and its firewall. Then confirm the port is actually open from outside — a port checker against 30120 UDP settles it.
Where to look
The firewall and router on the server side; the client's own network on theirs.
How to fix it
Forward both protocols on 30120:
endpoint_add_tcp "0.0.0.0:30120" endpoint_add_udp "0.0.0.0:30120"
Client side: flush DNS, disable a VPN, and try again. If the server is overloaded, that is a performance problem — see the hitch warning entry.
Still stuck on your own code?
This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.
bug_reportOpen Server Fixer