Isolate the source of the problem
Deploy a second game server of the same title. Make only minimal changes to the configuration to ensure it can start, but do not configure it further or install any mods.
Does the new game server run?
If it does, the issue is game server related.
If it does not run, the issue is hosting related.
Hosting related issues
If the problem appears to be hosting related, check the following points carefully:
-
Resources
Make sure the host system has enough memory, CPU, and storage available. Running out of any of these can cause the server to crash or fail to start. -
Permissions
The Architect Agent must be allowed to read, write, and execute files in the game server directory. Incorrect permissions can prevent the server from working properly. -
Ports and firewall
Ensure the required network ports are open and not blocked by a firewall. Also verify that no other process is already using the same ports. -
File integrity
If files are missing or corrupted, the server will fail. Redeploy or verify the installation through Architect to restore clean files. -
Operating system environment
Check that the operating system and all required dependencies are installed and up to date. Missing runtime libraries or outdated packages can cause startup issues.
Game server related issues
If a fresh deployment works but your configured one does not, the cause is in your own setup. In that case, review the following:
-
Configuration files
Return to default configuration and apply changes one at a time. Invalid syntax or unsupported settings often prevent servers from launching. -
Mods and plug-ins
Disable all mods and test again. Re-enable them one at a time until the issue appears. A single broken or outdated mod can stop the server. -
File paths
Verify that all mods, keys, and configuration files are in the correct directories. -
Startup parameters
Remove any custom command-line arguments and test again. Incorrect or conflicting parameters can cause immediate startup failure.
