Start with the server status and its latest messages before changing settings or restoring a backup. Open My Servers, select the Project Zomboid server, and check its status.

The server will not start

• If its status is Stopped, choose Start from the server actions.
• If setup or startup is still in progress, wait for it to finish.
• Open the Console tab and review the latest messages in the Console & Logs panel. Use Follow logs, Refresh Now, or Load Earlier Logs to find the first reported error.
• If you recently added or updated a Workshop item, see mod troubleshooting. Stop the server before disabling or removing a downloaded item.
• If the same error continues, contact support with your server ID and the non-sensitive error text.

The server is not reachable or does not appear

• Confirm the server is running and copy the Game address from its card in My Servers.
• If the game has separate IP and Port fields, enter the host and port separately.
• Try the direct address even if the public server browser is enabled. In Settings, check Show in public browser if you expect a listing.
• If the game reports a UDP 16262 or direct-connection warning, keep the exact message and ask support to check the connection. The game's default ports do not confirm that every hosted UDP path is reachable. See connection details.

Do not guess a new port or change the server's address to troubleshoot a warning.

Version or password mismatch

• If the game reports a version mismatch, note the versions for the client and server. Update the client through Steam and retry after the server has finished starting. If the versions still differ, contact support with the exact message.
• If a password is rejected, check whether the prompt is for your player password or the optional server-wide New join password. The Administrator password from creation is not the password for ordinary player accounts.
• If a friend cannot create a player account, check Allow new player accounts in Settings. When it is off, only existing accounts can join.

A Workshop item prevents startup

• Check Mods for pending downloads, detected dependencies, and warnings.
• Confirm that the Workshop item supports the server's installed game version and a dedicated Linux server.
• Stop the server, create a backup if you have not already, then disable or remove the most recent item.
• Start the server and check the Console tab again. MaximusHost does not automatically verify compatibility.

A change did not take effect or the world has a problem

For Settings changes, check the confirmation message and reopen the form to verify the saved value. Stop the server before saving basic or advanced settings, then start it manually to apply them.

If the world is damaged or progress is missing, avoid deleting files or restoring immediately. A restore replaces current server data and may discard later progress. Compare backup dates first; if you are unsure, contact support before restoring.

Performance feels poor

Check the resource readings on the server management page during a busy session. Concurrent players, world activity, and Workshop items can all affect resource needs. Consider lowering the configured player limit or reverting a recent mod change before increasing resources. The player limit is not a promise of supported capacity.

Contact support

Open a MaximusHost support ticket or contact support on Discord if the server repeatedly fails to start, the displayed address does not work, a UDP warning persists, or a restore or settings change does not complete. Include your server ID, approximate time, what you tried, and the exact non-sensitive error. Do not include passwords or account credentials.

For more detail, see create a server, connect to a server, and backups and restoration.