Enshrouded Server Not Showing or Not Connecting

If an Enshrouded server is not showing, first confirm the server reached Host_Online, then test it by IP and query port, verify UDP port 15637 through the host firewall and router, and confirm the host has a public IPv4 address.

Fast diagnostic order

1. Read the server log. A healthy start includes HostOnline and a transition to Host_Online.
2. Check the JSON. Confirm valid JSON syntax, the intended queryPort, and a slot count from 1-16.
3. Test on the host PC. If the server itself cannot see or join it, fix the process or configuration before changing the router.
4. Test from the local network. This separates server/firewall problems from internet-routing problems.
5. Test from outside the home network. A phone hotspot is useful; testing your own public address from inside can fail on routers without NAT loopback even when external access works.
6. Add it in Steam by IP. Use PUBLIC_IP:15637 under View > Game Servers > Favorites.

Server starts, but nobody can find it

• Enable Show dedicated server in Enshrouded's server filter.
• Add the IP and query port through Steam Favorites.
• Verify the name in enshrouded_server.json.
• Confirm Windows Firewall allows the executable or UDP query port.
• Confirm the router forwards the same UDP query port to the correct local IPv4 address.
• Reserve that local address in DHCP so the forwarding rule does not point to another device later.

Local players connect, internet players cannot

This usually points to the router, firewall, or ISP:

• Compare the router's WAN address with the public IPv4 address reported by a reputable IP-check service.
• If they differ, or the WAN address falls in a private/shared range, the ISP may use carrier-grade NAT.
• Ask the ISP whether a public IPv4 address is available.
• Avoid disabling the firewall or exposing the entire computer through DMZ.

Enshrouded currently uses IPv4 for multiplayer according to Keen's network guide.

Server fails after editing the JSON

An invalid text value can prevent the server from booting. Check:

• Missing commas, braces, or quotation marks
• A slot count outside 1-16
• A misspelled preset
• Custom gameplay values outside their accepted type

Keen notes that older configuration files can update incorrectly. After making a backup, one recovery option is to move the old config aside and let the server generate a fresh enshrouded_server.json on its next start, then reapply only needed values.

Random drops or an empty server browser

Keen recommends clearing Steam's download cache, flushing DNS with ipconfig /flushdns, trying a wired connection, and checking Steam privacy settings for peer-to-peer sessions. For a dedicated server, investigate packet loss, host upload saturation, and server CPU load before changing DNS.

Still stuck?

Collect the server log, current config with passwords removed, public/private test results, and the exact error. Then compare against the official network troubleshooting guide or submit a request to Keen Games.

Next: Backups and migration.