🎮 Game Error Codes What it means & how to fix it

Empyrion: Galactic Survival Can't Join a Server? Here's the Fix

When Empyrion can't join — the dedicated server won't appear, the connection drops, or telnet admin fails — it's usually the full 30000-30004 port range not being forwarded for both protocols, or edits lost on a game update. Forward the whole range and protect your config.

Exact details for Empyrion: Galactic Survival

Ports to forward (UDP + TCP)
30000-30004 (full range, both protocols)
Config file
dedicated.yaml — copy to MyDedicatedConfig.yaml to survive updates
Telnet admin port
30004 (use Raw connection type, not Telnet)
Common cause of 'can't connect'
Only 30000 forwarded — the whole 30000-30004 range must be open on UDP and TCP

Error codes

Can't connect to dedicated server The client never reaches the server

Cause: Only port 30000 forwarded, not the full range.

Fix:
  1. Forward the whole range 30000-30004 for BOTH UDP and TCP.
  2. Confirm SrvPort: 30000 in your dedicated.yaml matches the forwarded base port.
  3. Allow EmpyrionDedicated / EmpyrionLauncher through Windows Firewall.
  4. Restart the router and use a wired connection to the host.
Server not listed / can't be found The server runs but isn't discoverable

Cause: Query/steam ports in the range blocked.

Fix:
  1. Open every port 30000 through 30004, not just the game port.
  2. Join directly by public IP:30000 if the browser won't show it.
  3. Check the server is set to public visibility in dedicated.yaml.
  4. Verify no other service is already using ports in that range.
Settings reset after update / telnet fails Config lost or admin console won't connect

Cause: Editing dedicated.yaml directly, or wrong telnet mode.

Fix:
  1. Copy dedicated.yaml to MyDedicatedConfig.yaml so updates don't overwrite your settings.
  2. Use telnet port 30004 with the Raw connection type (Telnet mode causes password failures).
  3. Set Tel_Enabled and Tel_Port in the config before connecting.
  4. Restart the server after any config change.

Fixes that work for most Empyrion: Galactic Survival errors

  1. Forward the full range 30000-30004 for both UDP and TCP.
  2. Match SrvPort in dedicated.yaml to the forwarded base port.
  3. Copy config to MyDedicatedConfig.yaml so game updates don't wipe it.
  4. Use telnet 30004 in Raw mode for admin.
  5. Allow Empyrion through Windows Firewall (Private + Public).
  6. Join directly by public IP:30000 if it won't list.

FAQ

What ports does an Empyrion dedicated server need?

The range 30000 to 30004, forwarded for both UDP and TCP. Port 30000 is the game port set in dedicated.yaml, and 30004 is the default telnet admin port.

Why do my Empyrion server settings reset after an update?

Because you edited dedicated.yaml directly. Copy it to MyDedicatedConfig.yaml and point the launcher at that file — your settings then survive game updates.

Why does telnet admin keep rejecting my password?

Use the Raw connection type on port 30004, not the Telnet type. The Telnet mode causes the first password entry to always fail on Empyrion's console.

Other games