Enshrouded Server Not Appearing? Query Port & NAT Guide
If your Enshrouded server is missing from the list, Steam Favorites cannot find it, or friends cannot join, split the problem into two parts: discovery and connection.
Discovery can depend on the query port and Steam server browser behavior. A real connection failure usually points to NAT, public IPv4, firewall rules, port forwarding, or the server binding to the wrong address.
First decide where the failure is
A server missing from the Enshrouded list does not always mean the game server is unreachable. First separate discovery failure from real connection failure.
- Server missing from list: check queryPort, Steam Favorites, config, and refresh behavior.
- Friends cannot join: check NAT, public IPv4, forwarding, and OS firewall.
- LAN works but WAN fails: public reachability or router forwarding is the likely layer.
- Random drops: also check server performance, bandwidth, and security software.
If outside connections fail, check NAT and public reachability
Run the test on the same device and network you use for Enshrouded. The result helps separate ISP/router reachability from game, firewall, and platform problems.
| Result | Meaning for hosting or co-op | Next step |
|---|---|---|
| Full Cone / Open | Usually suitable for inbound connections or direct sessions. | Check firewall, ports, server config, and game version. |
| Restricted / Port Restricted | May work, but success can vary by game and peer. | Try UPnP or manual forwarding, then retest. |
| Symmetric NAT | Often unreliable for peer-to-peer or home-hosted sessions. | Disable VPN/proxy tools, change networks, or use hosting/relay. |
| CGNAT / no public IPv4 | The public internet usually cannot reach your home router. | Ask for public IPv4, or use a VPS, hosted server, or relay. |
If outside players can reach the host, apply the game-specific fix
For Enshrouded, the game-specific fix is not just “open ports.” The query port, IP binding, router target, and OS firewall must all match the server process.
queryPort
15637Default query port from official configuration guidance; important for discovery and Steam Favorites checks.
IP binding
IPv4 / 0.0.0.0Official examples emphasize IPv4 and binding; wrong binding can make outside access fail.
- Confirm queryPort does not conflict with another service.
- Confirm the server process is listening on the expected address and port.
- Allow the Enshrouded server process or ports through Windows/Linux firewall.
- Forward router traffic to the server machine static LAN IP.
If direct joining works but the symptom remains, check the next layer
If direct joining works but server discovery does not, the remaining problem is likely the browser, Steam Favorites, query behavior, or server config rather than raw connectivity.
- Check queryPort and confirm it does not conflict with another service.
- Try Steam Favorites as a separate visibility test.
- Confirm server name, config file, refresh behavior, and version compatibility.
- If direct joining fails too, go back to NAT, firewall, forwarding, and binding.
When router changes will not fix it
Stop changing router rules when the upstream path or server layer is the real blocker. Enshrouded issues can also come from server version, config files, Steam server browser behavior, cloud firewall rules, IPv4/IPv6 binding, server performance, and temporary service status.
- Your ISP uses CGNAT or your host has no public IPv4.
- You are on a shared network where you cannot control the upstream router.
- Direct joining works, but only discovery fails.
- The server process is not listening on the expected IPv4 address or query port.