7 Days to Die Server Not Showing: Configuration Checklist
If a 7 Days to Die dedicated server is missing from the server browser, check the configuration file selected by the server's launch command.
If a 7 Days to Die dedicated server is missing from the server browser, check the configuration file selected by the server's launch command.
Check ServerVisibility
The documented values are:
2: public.1: friends only.0: not listed.
Use 2 for a publicly listed server. With ServerVisibility=1, the first player may need to connect manually by IP.
Verify the active configuration file
The -configfile= launch argument identifies the XML file the dedicated server reads. For example, -configfile=myserver.xml selects myserver.xml.
Check the command that starts the server and edit the file named by this argument. The shipped serverconfig.xml is overwritten during updates, so the documentation recommends using a uniquely named configuration file referenced through -configfile=.
Check the server identity and port
In the active XML file, verify:
ServerName: the name displayed in the server browser.Region: the configured server region.Language: the server's primary language.ServerPort: the port on which the server listens.
Search the browser for the configured ServerName. For a direct-IP test, use the configured ServerPort.
Check V3 configuration compatibility
The official V3 release notes state that some legacy options formerly set as individual serverconfig.xml properties were moved to the SandboxCode XML property. When using an older configuration, compare it with the V3 format instead of assuming all legacy properties remain valid.
For another discovery route, browse live game servers on LiveGameServerList.
Sources and verification
- V3.0 "Dead Hot Summer" Release NotesDocuments that some legacy serverconfig.xml options were moved to the SandboxCode XML property for V3.
- Setting Up a Dedicated Server — 7 Days to Die Modding WikiDocuments ServerVisibility values, the friends-only direct-IP behavior, -configfile selection, update-safe custom configuration files, server identity properties, and ServerPort.
