Start with the server’s Overview, Console, and Incidents areas. Check the status after each start, stop, or restart and wait for the current operation to finish before starting another one.

Server will not start

1. Wait for installation or update work to finish.
2. Check Console for the current startup output and Incidents for a reported failure.
3. If you recently changed settings, return to Settings and check the world name, player count, mode, season, and platform choices.
4. If the problem began after a mod change, stop the server and disable or remove the last changed mod.
5. If the world or settings may be damaged, create a backup of the current state if possible before restoring an earlier one.

If Console remains empty or the status does not match the running server process, save the time of the attempt and contact support. Do not paste credentials or raw configuration files into a ticket.

Friends cannot join

• Confirm the server is running and use the current direct address and port shown by the owner’s account.
• For a direct connection, check the direct-connect password and the selected PC platform restriction.
• Paste the owner’s direct join code into Core Keeper’s Join Game via IP field. It includes the public address, allocated public port, and direct-connect password.
• A generated Steam Game ID works only for Steam clients, but its presence does not confirm that Steam relay joining is reachable. If joining by ID fails, use the direct join code.
• Core Keeper does not support PC-to-console cross-play.
• Confirm every player has the same game version and, if the server is modded, compatible matching client mods.

See Join and Invite Friends for connection steps.

Settings did not take effect

Settings apply on the next start or restart. Seed affects a new world only. World mode should be chosen before creating a new world; switching between Creative and a non-Creative mode after world creation is not supported. Save the setting, restart, and check it again before making another change.

A modded server fails

Stop the server, disable the newest mod, and try again. Check the mod manifest and dependency warnings, then confirm the mod version matches the server and each player’s client. Make a backup before restoring because restore replaces newer server data.

Core Keeper mod runtime compatibility has not yet been verified against the current server build. If the package manager reports a successful upload but the game does not load the mod, retain the ZIP and report the mod name, version, and non-sensitive Console output.

World or restore problem

Do not edit, rename, or upload individual files in the configured Core Keeper world-data folder. Create or preserve a full-server backup, then contact support with the backup time and the operation that preceded the problem.

The dashboard does not yet provide a Core Keeper world-only import/export workflow. See World Management and Backups and Restore.