ARK: Survival Ascended Server Shows Online But Players Can't Join
Last verified: June 2026.
This is the single most frustrating ARK: Survival Ascended self-host failure: the dedicated server boots cleanly, it shows up as online in the server browser, the player count and ping look normal, but when anyone clicks Join they get a connection timeout, an endless loading screen, or a "lost connection to host" message. The world is fine. The process is fine. The listing is fine. What is broken is the path that carries the actual gameplay traffic.
If your server does not appear in the browser at all, that is a different problem - see ASA "No Sessions Found". If only console players time out while PC players join, see the ASA Crossplay Timeout Fix. This page is specifically for the case where the server is clearly visible and reporting healthy, but the connection itself never completes.
Why "Online" and "Joinable" Are Two Different Things
A dedicated server has to do two completely separate network jobs, and they travel over different ports:
- Advertise itself so it shows up in the in-game browser. This is the listing or discovery path. On ARK: Survival Ascended the server registers with the platform's online service over outbound HTTPS, and the browser/query exposure tells the list it is alive.
- Carry the live game session once a player clicks Join. This is the RAW UDP gameplay traffic on the game port, and it has to be reachable inbound from the player's machine all the way to the server.
The trap is that the first job can succeed while the second fails. The listing path is mostly outbound and lightweight, so it works even when your inbound game port is closed. The result: a server that proudly advertises itself to the whole world and then refuses every single join. Browser visibility is never proof that gameplay networking is healthy.
The ASA Port Model
These are the default ports for an ARK: Survival Ascended dedicated server. Confirm your own values against your launch arguments and INI - admins routinely change them, especially when stacking multiple maps on one box.
Game Port: 7777/UDP (the live game/RAW traffic - MUST be reachable to join)
Peer Port: 7778/UDP (often required alongside 7777 - open it too)
Query Port: 27015/UDP (Steam-style server browser/query exposure)
RCON Port: 27020/TCP (remote admin console - optional, not needed to join)| Port | Job | If it is closed |
|---|---|---|
| 7777/UDP (Game) | Carries the actual gameplay session | Server is visible but every join times out - this is the page you are on |
| 7778/UDP (Peer) | Paired with the game port on many builds | Intermittent or total join failures even though 7777 is open |
| 27015/UDP (Query) | Browser/query visibility | Server may not appear or appears with wrong info (a "no sessions" symptom, not this one) |
| 27020/TCP (RCON) | Remote admin only | You lose remote console - players can still join normally |
The one rule that fixes most cases: the game port (7777/UDP) and its peer port (7778/UDP) must be open inbound. Forwarding only the query port - or forwarding the game port for TCP but not UDP - leaves you exactly in the "online but unjoinable" state.
Most Common Causes, In Order
- Only the query/listing port was forwarded. Admins see the server appear in the list, assume networking is done, and never open 7777/7778 inbound. The listing works; joins do not.
- The game port is forwarded for the wrong protocol. ARK gameplay is UDP. A TCP-only rule (or a UDP rule that quietly got dropped) lets the listing succeed and blocks the session.
- The peer port (7778/UDP) is missing. Many builds need the game port and the very next port open together. Open the pair, not just 7777.
- Host firewall is blocking inbound UDP. The router forward is correct but the operating system firewall on the host machine still drops the game port. Both layers have to allow it.
- CGNAT / double NAT. If your ISP puts you behind Carrier-Grade NAT, inbound traffic never reaches your router at all, no matter how perfectly you forward. The listing still works because it is outbound. Compare the WAN IP in your router admin against an external "what is my IP" check - if they differ, you are behind CGNAT and port forwarding cannot help.
- Wrong public IP or port advertised. If the server advertises a LAN IP, a stale public IP, or a different port than the one actually open, the browser entry points players at an address that drops them.
- Port collision in a cluster. Two maps on the same host reusing the same game port. One registers and serves; the second appears online but its traffic lands on the wrong process and joins fail.
Diagnostic Checklist
Work top to bottom. Each step removes a whole class of cause.
1. Confirm the server is actually listening on the game port
On the host, check that the process is bound to the UDP game port. On Linux:
ss -lunp | grep 7777
# or
netstat -anu | grep 7777On Windows, use netstat -an -p UDP | findstr 7777. If nothing is listening on 7777/UDP, the problem is the launch line or a port the server failed to bind - fix that before touching the router.
2. Verify each port from outside the host
From a machine on a different network (or a phone on mobile data), test whether the game port is reachable from the public internet. UDP is connectionless so a simple ping will not prove it, but an external port checker that supports UDP, or a teammate trying open PUBLIC_IP:7777 from the ARK console, tells you fast. If the listing shows the server but open by direct IP also times out, inbound 7777/UDP is not getting through.
3. Check what the server is advertising
Make sure the address and port shown in the browser entry match the public IP and the game port you actually opened. A server advertising a LAN address (192.168.x.x or 10.x.x.x) is online to you on the same network but unreachable to outside players.
4. Open the game port pair on both layers
- Router: forward
7777/UDPand7778/UDPto the host's internal IP. - Host firewall: allow inbound UDP on the same ports.
- Reboot the router after changing forwards - some only apply the rule on restart.
5. Rule out CGNAT
Router WAN IP vs external IP check. If they do not match, contact your ISP for a public/static IP or move the server to a host that is not behind CGNAT. No port-forwarding change fixes CGNAT.
When It Is a Cluster Port-Offset Issue
If you run more than one ASA map on a single machine, every map needs its own clean, non-overlapping set of ports. The usual pattern is to increment by a fixed offset so nothing collides:
Map 1: -Port=7777 -QueryPort=27015 -RCONPort=27020
Map 2: -Port=7779 -QueryPort=27017 -RCONPort=27021
Map 3: -Port=7781 -QueryPort=27019 -RCONPort=27022Leave a gap on the game port (jump 7777 to 7779, not 7778) so the peer port of map 1 does not collide with the game port of map 2. Then forward and firewall-allow every game and peer port in the cluster. A classic cluster symptom is that one map is perfectly joinable while another shows online but times out - that is almost always a reused or un-forwarded game port on the second instance, not a save problem.
Do not chase the save or reinstall first. "Online but can't join" is a networking fingerprint. Validating files, rolling back the world, or wiping mods will waste hours when the real fix is opening one UDP port pair. Only suspect the world after the game port is confirmed reachable and joins still fail.
How Managed Hosting Removes This Entirely
Every cause on this page traces back to one thing: inbound game traffic not reaching the server. On a self-host that means router forwards, host firewall rules, ISP CGNAT, and per-map port math - any one of which silently leaves you advertising a server nobody can join. On managed hosting the game port, peer port, and query port are pre-opened and routed for you on a public address with no CGNAT in front of it, so a server that shows online is a server players can actually join. Clusters get clean non-colliding port sets assigned automatically instead of hand-incremented launch arguments.
Want a server where "online" means "joinable" without touching a single router rule? Launch an ARK: Survival Ascended server on Supercraft with the full port set pre-opened on a public IP.
Looking for managed ARK: Survival Evolved server hosting? Supercraft runs ARK: Survival Evolved dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.