A server can be running perfectly, accepting players who know the address, and be completely absent from every listing and every in-game browser. When that happens the cause is nearly always the same, and it is not the listing's fault.
Two ports, two jobs
A game server listens for players on the game port. It answers questions about itself on the query port — how many players, which map, what version, what name.
Those are separate listeners doing separate things. Everything that shows information about your server without connecting to it uses the second one: listing sites, the in-game server browser, monitoring tools, Discord status bots.
Block the query port, or get its number wrong, and all of them conclude you are offline. Your players see nothing wrong, because they never use it.
Where the number comes from
For Source engine games the query port is usually the game port, and the two share a number. For Minecraft, query is off by default and has to be enabled in server.properties along with its own port. For several other games it is game port plus one, which is a convention rather than a rule.
The convention is where panel-hosted servers break. A panel that hands you two unrelated allocation numbers has given you a game port and a query port that do not stand in the relationship the game expects, and the game will happily listen on both while announcing the wrong one, or listen on the right one while your firewall covers only the other.
This is the most common cause of a server that is up and unlisted, and it is worth checking before concluding anything about why a new listing gets no traffic.
Test it from outside
ss -lun on the box tells you what is bound locally. It says nothing about reachability, because between you and the internet sit your firewall, possibly a container network, and your host's edge — any of which can drop the packet.
Use a machine that is not the server. Query it the way a listing would. If it answers from outside, the listing problem is elsewhere; if it does not, you have found it and nothing else needs investigating yet.
UDP makes this harder than it should be
Query traffic is UDP, which has no handshake and therefore no connection to observe. A blocked TCP port refuses politely; a blocked UDP port is indistinguishable from a server that is switched off.
That silence is why the problem survives so long. There is no error to search for: a poller sends a packet, nothing comes back, and it records a timeout. From your side nothing happened at all, which is the same investigative dead end as any other connection that fails without a message.
The other half: hosting behind NAT
On a home connection, forwarding the game port and forgetting the query port produces exactly this symptom. Friends can join if you send them the address. The server appears nowhere.
Both ports need forwarding, and both need to be the ports the server actually announces. If you are behind carrier-grade NAT no amount of forwarding helps, and that is a different problem with a different answer: it belongs with the decision about where to host at all.
When the port is right and it still does not list
Then the causes narrow quickly:
- The server is announcing a hostname or address that does not resolve from outside.
- The query response is malformed, usually because a plugin rewrites the server name with characters the protocol does not carry.
- The server is genuinely being polled and genuinely empty, and you are looking at a ranking problem rather than a visibility one.
That last one is the most common of the three and the one nobody wants. A server that is listed, reachable and empty has a different job ahead of it, and the work is in what the first ten minutes offer rather than in the network stack.
The check worth doing monthly
Query your own server from outside, the way a stranger's tooling would, and confirm the name, the map and the player count come back correct. It takes a minute.
Servers that quietly fall off listings usually did so weeks before anybody noticed, and the cause was a port that changed during an unrelated migration.
Published · 3 min read