Core Keeper Server Connection Troubleshooting
If a Core Keeper player types a generated server password or ID and “nothing happens,” start by checking the supported Join Game + Game ID flow. The official FAQ does not describe a generic browser password workflow for the dedicated-server tool. Work through this order so you can tell an invalid join method from a stopped process, version mismatch, or network restriction.
Last verified: September 1, 2026. Pugstorm's official FAQ says to install the Dedicated Server from Steam Tools, copy its Game ID, and enter that ID from Core Keeper's Join Game menu.
Fast triage
| Symptom | First check | Next action |
|---|---|---|
| Nothing changes after typing the value | Is the player in Join Game and entering the current Game ID? | Restart Core Keeper and the server tool, copy the newly printed ID, and retry. |
| Join starts, then stalls | Do client and server have the same game build? | Update Steam Tools and restart every client before testing mods. |
| Friends cannot join from another network | Is the host behind a firewall, VPN, school/work network, or CGNAT? | Test locally and externally; capture the exact point of failure rather than adding random ports. |
| PC player and console player cannot join together | Platform mix | The FAQ says cross-platform crossplay is not supported. PC storefronts can play together; console generations support cross-generation play. |
| Join broke after a mod/update | Does the vanilla copy still join? | Restore the backup, disable the newest mod, and add changes one at a time. |
1. Confirm the server process and ID
- Launch Core Keeper Dedicated Server from Steam > Tools.
- Choose Launch Dedicated Server and press Play.
- Wait for the command window to print a Game ID. Press Enter once if it has not prompted yet.
- Leave that process running while the client joins. Pressing
qends the server cleanly.
A new restart produces a new value. Do not reuse an old screenshot or a value copied before the process finished initializing.
2. Separate version and platform problems
- Update the game and Dedicated Server tool, then restart Steam on both sides.
- Test an unmodded world before diagnosing Workshop or community mods.
- Keep PC storefronts together (Steam, Epic, or GOG). A PC/console group cannot use cross-platform crossplay under the current FAQ.
3. Check the network boundary
Pugstorm's dedicated-server announcement says the supported flow no longer requires port forwarding. A local firewall, VPN, CGNAT, or filtered network can still prevent a particular player from reaching the service. Compare:
- the host joining locally;
- a friend on a different connection (for example, mobile hotspot);
- the same test with VPNs, overlays, and aggressive firewall rules temporarily out of the path.
Recent Core Keeper community discussion shows that CGNAT and no-port-forwarding workarounds are recurring questions. Treat those posts as troubleshooting leads and keep the official Game ID flow as the baseline.
4. Protect the world while testing
Back up the dedicated-server worlds directory before deleting files, changing mods, or moving a save. The setup guide lists the Windows and Linux paths from the official FAQ. If the clean backup joins, the failure is in the changed copy—not proof that the world needs to be regenerated.
When to escalate
Record the game/server build, platform pair, fresh Game ID timestamp, client log, server log, and whether local versus external joining differs. Include that evidence in a bug report or support request. “It does nothing” is much easier to diagnose when the join menu, ID age, and network boundary are known.
Related Core Keeper guides
- Dedicated server setup and Game ID onboarding
- General server and save troubleshooting
- Workshop mods and compatibility checks
- Core Keeper server cost and sizing
If the group needs an always-on process with backups, managed Core Keeper server hosting removes the sleeping-host and home-network variables while keeping the same game-side join concepts.