- Open the current host or server console file and note its last changing line.
- If downloads are advancing, wait and avoid stopping the process.
- If one Workshop item repeats or fails, record its ID, stop the server cleanly, and repair that download and its dependencies.
- If the log names a port conflict, restore or change the configured ports so each listener is unique.
- If the server starts without mods, re-enable them in batches on a new test world.
- If the log shows no client attempt, confirm the server actually reached its ready state before troubleshooting the connection.
Separate slow from stuck
A large first-time mod download can take much longer than a vanilla start. Use new log lines, network activity, and the current Workshop item as evidence. A fixed timer such as ten minutes cannot distinguish a slow download from a dead process on every system.
Sources
The Indie Stone support: server stuck at initialising — Official log-based troubleshooting.
Steam support: initializing and port configuration — Support case involving ports and mod isolation.
Community initializing report — Community observations; unsafe restart loops are not recommended here.