You have set up your dedicated server, the game is running, but it does not appear in the server browser. This is one of the most common issues new server operators encounter, and it almost always comes down to a small number of root causes: firewall rules, port configuration, or game server settings. This guide covers every reason a dedicated server might not show up and the exact steps to fix each one. If you have not yet configured your server's firewall, start with our dedicated server firewall guide before working through the steps below.
⚡ Difficulty: Beginner to Intermediate
🎮 Applies to: Ark Survival Evolved, Palworld, Minecraft, Rust, 7 Days to Die, and most dedicated game servers
Key Takeaways
- The most common reason a dedicated server is not showing in the server browser is a missing or incorrect firewall rule blocking the query port.
- Game servers use two types of ports: the gameplay port (for player connections) and the query port (for the server browser). Both must be open.
- For Ark Survival Evolved, the server browser uses UDP port 27015. For Palworld, UDP 27015 is also the default query port. Always check the game's documentation for the exact ports.
- If the server appears when connected directly by IP but not in the browser list, the query port is blocked or misconfigured.
Why Is My Dedicated Server Not Showing in the Server Browser?
The server browser (the in-game or Steam server list) works differently from a direct connection. When you connect directly, you target a specific IP and port. When the server browser scans for servers, it sends a query to a specific port to request server information. If that query port is blocked or returning incorrect data, the server will not appear in the list even if the game itself is running fine.
Here are the most common causes:
1. Query port not open in firewall
Every game server has a gameplay port and a query port. The gameplay port is what players use to connect. The query port is what the Steam server browser (or in-game browser) uses to request server information. These are often different ports. If you only opened the gameplay port, the server will not appear in browser listings.
Common query ports by game: Ark Survival Evolved UDP 27015; Palworld UDP 27015; Minecraft Java TCP 25565 (same port for both); Rust UDP 28015 (gameplay), 28016 (RCON), 28017 (query); 7 Days to Die UDP 26900.
Open the query port (example for Ark)
sudo ufw allow 27015/udp2. Server not registered with Steam backend
Steam-based game servers need to register with the Steam master server list to appear in the browser. This requires: an active internet connection from the server, the correct query port open and reachable, and the server software running with the correct SteamCMD app ID. If registration fails, the server runs but does not appear publicly.
3. Incorrect server configuration file settings
Some games have configuration options that control whether the server is listed publicly. For Ark Survival Evolved, check that the server launch parameters do not include ?PreventDownloadSurvivors or similar flags that restrict visibility. For Minecraft, check server.properties: the line 'online-mode=true' is required for the server to appear in the official multiplayer browser.
4. Server still starting up
After restarting a game server, it takes time to register with the master server list and appear in the browser. Depending on the game, this can take 2 to 15 minutes. Wait a few minutes after starting the server before checking the browser list.
5. The server is on a LAN tab, not the internet tab
If you are testing from the same network as the server (on your local network), the server may appear under the 'LAN' tab in the server browser rather than the internet list. Test from a different network or use an external connection checker to verify public visibility.
How to Check Server Visibility: Step-by-Step Diagnostic
Step 1: Verify the server is running
sudo systemctl status gameserverIf the service is inactive or failed, start it and review the logs:
sudo systemctl start gameserver
sudo journalctl -u gameserver -n 50Step 2: Check which ports are open on the server
sudo ss -tlnup
sudo ss -ulnup # UDP portsConfirm your game server is listening on its expected port. If the port does not appear, the server is not running correctly.
Step 3: Check firewall rules
sudo ufw status verboseEnsure both the gameplay port AND the query port are listed as allowed. If not, add them:
sudo ufw allow PORT/udpStep 4: Test port reachability from outside
Use an online port checker (portchecker.co) to verify that the query port is reachable from the public internet. Enter your server's public IP and the query port. If the port shows as closed despite being open in UFW, check whether your hosting panel has an additional network-level rule or whether the game server process is actually listening on that port.
Step 5: Check the server browser directly
In Steam, go to View > Game Servers > Search. Filter by game and search for your server by name or IP. If it appears here but not in the in-game browser, the issue is with the game client's built-in browser, not the server. Try connecting directly via IP.
How Long Does It Take for a Server to Show Up?
After starting a game server, expect 2 to 10 minutes before it appears in the Steam server browser or in-game list. Some games take longer for initial registration. If the server has not appeared after 15 minutes and all ports are confirmed open and the service is running, check the server logs for errors related to Steam backend connectivity or master server registration.
Common Game-Specific Fixes
Ark Survival Evolved not showing
Ensure UDP ports 7777 (gameplay) and 27015 (query) are both open. Check that the server map name in the launch parameters matches exactly (case-sensitive). Verify the server is launched with the ?listen parameter. If using Ark Survival Ascended, the default query port is still 27015 UDP.
Palworld dedicated server not showing
Open UDP 8211 (gameplay) and UDP 27015 (query). Verify that PublicIP is set correctly in PalWorldSettings.ini if the server is behind NAT. The server browser password field must be left blank if the server has no password; a mismatch will prevent it from appearing in filtered searches.
Minecraft server not showing
For Java Edition, TCP 25565 must be open. Confirm the server is set to online-mode=true in server.properties for the public multiplayer browser. For Bedrock Edition, UDP 19132 must be open. If using a non-standard port, players must search by IP:port directly.
How Do I Access a Dedicated Server Directly?
If the server does not appear in the browser but you want to connect directly, use the 'Direct Connect' or 'Add by IP' option in the game client. Enter your server's public IP address and the gameplay port (e.g., 192.168.1.100:7777 for Ark). Direct connection bypasses the server browser entirely and is a useful diagnostic step to confirm the server is reachable even if browser listing is not working yet.
FAQ
Why is my dedicated server not showing up in Steam server browser?
The most likely cause is a blocked query port. Verify that the Steam query port (typically UDP 27015 for most games) is open in your firewall. Also confirm that the server software is running and has had time to register with Steam's master servers (allow 5 to 10 minutes after starting).
What settings affect server listing visibility?
The key settings are: firewall rules for the query port, the server's public IP configuration, whether the server is set to list publicly in its configuration file, and whether the server has registered with the game's master server backend. For games with password protection, servers may be hidden from search results by default.
How do I fix a server that appears in browser but cannot be connected to?
If the server appears in the browser but connection attempts fail or time out, the gameplay port is blocked or the server is overloaded. Check that the gameplay port (different from the query port) is open in your firewall. For more on connection timeouts, see our dedicated server timeout guide.
Conclusion
A dedicated server not showing in the server browser almost always comes down to a missing query port rule in the firewall, a startup delay, or a misconfigured server option. Working through the five diagnostic steps in this guide resolves the vast majority of visibility issues within minutes. Make sure both the gameplay port and the query port are open, give the server time to register with the master server list, and verify from an external connection. For a solid foundation on server setup, see our guide on how to host a dedicated server.
Host your game server with Kimsufi Dedicated servers from $11.10/month. Full root access, unmetered bandwidth, and built-in DDoS protection. Browse KS and SYS ranges.