Empyrion Connection Timeout Fix
Work from the outside in: can the process listen, can the assigned port reach the host, and can the client and scenario accept the same world? Changing YAML values before answering those questions makes diagnosis harder.
Connection checklist
- Read the server log after startup and confirm it stayed running.
- Copy the game and query ports from the panel or current launcher output.
- Check host firewall and router forwarding for those exact ports.
- Try one direct connection from outside the host's LAN.
- Compare client/server build and scenario version.
- Check password and server visibility only after the network path works.
Interpret the result
| Result | Meaning |
|---|---|
| LAN join works, outside join times out | Forwarding, firewall or public address problem. |
| Browser works, direct join times out | Wrong direct port or a stale connection value. |
| Join reaches loading then fails | Build, scenario or save compatibility problem. |
A TCP port checker cannot prove that an Empyrion UDP game path works. Test with a real client and the assigned values.
For managed ports and node networking, see Empyrion server hosting. If the world itself is wrong after joining, use the save restore checklist.