Core Keeper Dedicated Server Connection Troubleshooting

#Direct Answer

If a Core Keeper dedicated server does not appear to work, do not reinstall it or replace the world first. Prove four things in order: the server process stays running, it produces a current game/session ID, the server and client are on matching versions, and one unmodded client can join with that fresh ID. The first failed checkpoint tells you where to work; the world save is rarely the first useful suspect.

#The shortest safe test

1. Stop the server normally and keep a backup of its current world and configuration files.
2. Start it once with the normal launch method and watch the console or log until startup finishes.
3. Copy the session ID from this launch rather than reusing an old message or screenshot.
4. Confirm the joining PC has completed the same Core Keeper update as the server.
5. Try one client with mods disabled and no overlay or VPN change in progress.
6. Leave the server unchanged while that first client tests.

Do not invite the whole group yet. One successful clean join proves the process, world, current ID, and at least one network path work together.

#Read the failure by checkpoint

A console window existing for a few seconds is not proof that the server is ready. Likewise, a correct-looking ID does not prove that it came from the current process. Record the time of the launch beside the ID so the group does not keep circulating stale connection details.

#If the server process closes or restarts

Treat this as a launch failure, not a player connection failure. Read the final lines of the server log and look for the first clear error before the shutdown. Check the launch path, configuration syntax, write permissions, and whether another server process is already using the same resources.

Make only one change, then launch again. If the process now remains ready, stop editing configuration and continue to the ID test. Repeatedly changing ports, saves, launch flags, and firewall rules together destroys the evidence that would identify the original fault.

Do not delete or rename the active world to see whether the server starts. If a blank test world is genuinely required, back up the active save and point the test at a clearly separate location. A connectivity diagnosis should not become a save-recovery job.

#If the ID is rejected or appears invalid

Copy it directly from the latest successful startup. Remove accidental spaces and make sure chat software did not trim or reformat the string. Restarting the server can make an older shared ID useless, so send a new message with the new ID and mark the older one as expired.

If the server never reaches the point where it presents a usable ID, return to launch diagnosis. Router changes cannot fix an application that has not completed startup.

#If the game reports a version mismatch

Update both sides, then fully restart the server process and the client. Checking only the store page is not enough: a queued update, alternate branch, cached server build, or host control panel can leave one side behind.

Record the displayed version from the server log and from the joining game. If they differ, stop all network troubleshooting. A firewall exception or new invite cannot make incompatible builds join each other.

If the versions match but the client uses mods, repeat the test with a clean, unmodded launch. Add mods back only after the base game joins. This does not prove a particular mod is broken; it prevents a modded client from hiding whether the server itself is reachable.

#If one player joins and another cannot

The server has already passed its most important test. Keep its world, configuration, and working ID unchanged. On the failing PC:

1. confirm the same displayed game version
2. paste the known-working current ID
3. disable mods for one test
4. restart the client after any update
5. compare VPN, firewall, or security-software conditions with the working PC

If possible, test the failing account or PC on a different network path. The result tells you more than another server rebuild: success elsewhere points toward the original local network, while failure on multiple networks keeps the focus on that client.

#If nobody outside the host network can join

First prove that the server completes startup and that a local client can use the current ID. Then inspect the host machine's firewall and hosting-provider controls. Create the narrowest applicable rule for the server program or documented traffic rather than turning protection off for the whole machine.

If you use a rented host, check its service console and provider status before changing the world. If you host at home, note whether the failure began after a router restart, ISP change, security update, or server update. That timeline is useful evidence.

Avoid guessing port numbers from unrelated games or old forum posts. Use the current official server documentation and the controls supplied by your host. Provider networking can sit outside the Core Keeper process, so a healthy server log and a failed external join can both be true.

#A clean escalation note

Before asking a host, community helper, or another player to diagnose the server, collect:

• server and client version strings
• launch time and whether the process remains ready
• whether a fresh ID was used
• whether one unmodded client can join
• whether local and external clients behave differently
• the first relevant error line, with private IDs and addresses removed

Do not publish the full server log without checking it for session IDs, file paths, account names, or network details. A short, redacted timeline is safer and usually easier to diagnose.

#Stop conditions

Stop changing the server as soon as one clean client joins. From that point, the remaining problem belongs to a specific client or network path until new evidence says otherwise. Stop editing firewall rules when the server process itself does not stay ready. Stop changing world files during a connection test unless the log specifically identifies a world-loading failure and a backup already exists.

#Next step

Once one clean join works, invite a second player before restoring mods or custom launch options. Add one variable at a time and keep the last working configuration written down. If the host must be online for the group's normal world, read the co-op host offline guide before deciding whether a dedicated server is the right long-term setup.

#FAQ

#Should I make a new world when players cannot connect?

No. First prove server startup, the current ID, matching versions, and one clean client. A new world does not repair a stale ID or a blocked connection and can put the real save at risk.

#Why did yesterday's server ID stop working?

Use the ID from the current successful startup. After a restart, an older copied message may no longer identify the active session.

#Does one successful join prove the server works?

It proves the server, world, current ID, and one client path work together. Keep that configuration fixed and troubleshoot any remaining player separately.

#Sources And Review Notes

The official Core Keeper dedicated server guide is the primary reference for installation and launch behavior. The community dedicated server reference is useful for terminology and operational context. This page's checkpoint order, privacy advice, and stop rules are original editorial troubleshooting guidance.

#Related Guides

• Core Keeper Co-op Host Offline Guide
• Core Keeper Co-op Save Owner Guide
• Core Keeper Mods Baseline Guide