Match this symptom
enshrouded_server.exe starts and exits, or its log reports a configuration problem before [Session] 'HostOnline' (up)! appears.
The answer first
Do not delete the save. Copy enshrouded_server.json and the complete configured saveDirectory, then validate the JSON locally and read the first invalid-value log entry. Restore a known-good file or regenerate only the JSON reference, and reapply one documented change at a time.
Preserve the world and broken JSON first
The server can regenerate a missing configuration file, but that is not a reason to delete evidence. Prevent an automatic restart, confirm the process has stopped, and copy enshrouded_server.json plus the entire directory named by saveDirectory.
The world set includes hex-named files, _info metadata, numbered generations and index data. Leave it untouched while repairing startup configuration.
- 1Disable the manager's automatic restart for this instance.
- 2Copy the current JSON and complete save directory to a dated folder.
- 3Preserve the current log through the first startup error and redact passwords before sharing it.
Validate JSON structure without exposing role passwords
A missing comma, trailing syntax error, duplicate block or smart quote can keep the server from reading its settings. Check the file with a local JSON-aware editor; do not paste production userGroups passwords into a public web validator.
If the structure cannot be repaired confidently, move—not delete—the broken JSON and let a first run generate a clean current schema. Stop again before copying back documented values.
- Use straight JSON quotes and balanced braces/brackets.
- Keep one value for name, directories, bind, queryPort and slotCount.
- Rotate any password that appeared in a screenshot or shared validator.
Check gameplay presets and role schema
Keen says gameSettingsPreset accepts Default, Relaxed, Hard, Survival or Custom, and individual gameSettings apply with Custom. Invalid text values can prevent boot and should be named in the log.
Current authentication uses userGroups. The old top-level password is migrated to a default group; it should not be combined with copied role examples from an obsolete guide. Start with one least-privileged user group and add more only after readiness.
- 1Set gameSettingsPreset to Default for the isolation start.
- 2Remove only unverified custom settings from the copied repair file.
- 3Define one valid userGroups entry with a new private password.
- 4Add custom gameplay values and additional roles in small, restart-tested batches.
Prove paths and HostOnline under the service account
saveDirectory and logDirectory default to relative paths. A Windows service can use a different working directory from an interactive command prompt, so valid JSON may still point to an unintended empty folder or a location it cannot write.
Start with the same account, executable path and working directory the product will use. Wait for [Session] 'HostOnline' (up)!, join privately, confirm the expected world, then perform the product's validated stop/restart test before reopening access.
- Confirm write access to the resolved save and log directories.
- Confirm queryPort is not already owned by another process.
- Do not mark the server online before the HostOnline readiness state.