Valheim Server Not Showing in the Server List

A Valheim server that runs fine but never appears in the browser is almost always failing one specific thing, and there are only a handful of candidates. They are below in the order they turn out to be the answer.

First, separate the three failures

Before working through the list, establish which problem you actually have. Check the log first: if the server never finished starting, this is a password or world problem and nothing about the browser matters yet. If it did start, try a direct connect to your address and port from outside your network. If you get in, the server is healthy and the problem is the listing. If you do not, the server is unreachable and the missing listing is a symptom rather than the fault.

Those three lead to different halves of this page, and confusing them costs the most time.

The five causes, in order

1.The query port (2457) is not open

Valheim advertises itself on the game port plus one. Open 2456 and forget 2457 and you get the defining symptom: the server runs, friends who type the address get in, and it never appears in the browser for anyone. This is the single most common cause, and it is worth ruling out before touching anything else.

2.The password breaks one of Valheim's two rules

The server refuses to start at all, which looks like "not showing up" to anyone who has not read the log. A public server needs a password of at least five characters, and the password must NOT appear inside the server name or the world name. That second rule catches groups who name the server after the password so it is easy to remember. Rename one of the three and it boots.

3.The server is set to private

A server started as non-public never registers with the browser by design. It still accepts direct connections and crossplay join codes, so everything works for anyone who has the address. If someone changed this setting to "hide" the server from strangers, that is the setting doing exactly what it says.

4.Crossplay players are looking in the wrong place

The community browser is a Steam-backend list. Xbox and Game Pass players do not find crossplay servers there and are meant to join with a join code or by address instead. If your Steam players see the server and your console players do not, this is usually why. The other candidate is the crossplay port on 2458 not being published.

5.It is listed and you are filtering it out

The in-game browser remembers filters between sessions and hides servers by region, by whether they are full, and by name fragment. Before assuming the listing is broken, clear the filters and search the exact server name, or use a direct connect to confirm the server itself is reachable.

Valheim is UDP only

Worth stating plainly, because it is where a lot of troubleshooting time goes. Valheim uses UDP 2456 for the game, UDP 2457 for the server query and UDP 2458 for crossplay. None of it is TCP. Router UIs default to TCP, and forwarding rules written for TCP look correct in the interface while doing nothing at all for the game.

Reading the log rather than guessing

The server prints the reason on startup in nearly every case where it failed to boot. A password that violates one of the two rules names itself. A world that could not be loaded says so. Open the container log, restart the server, and read the first thirty seconds rather than the last thirty — the cause is almost always in the boot sequence, and anything after it is the consequence.

One thing you will not find is an RCON console. Valheim’s dedicated server has none, so there is no remote command to interrogate a running server with. The log and the query response are the whole diagnostic surface, which is why the query port mattering so much is not an accident.

If it is the query port

The fix is to publish 2457 alongside 2456, and the server returns to the browser within a minute or two of registering. There is no heartbeat interval to wait out and nothing to re-register by hand. If it has not come back after a restart and a few minutes, the cause was not the one you changed — go back to the log.

If you are running crossplay, publish 2458 too. A server missing it behaves in the most confusing way available: entirely normal for Steam players, broken only for everyone else. It is also the port most marketplace specs and host presets forget, so it is worth confirming rather than assuming.

Or start from a server that is already wired

All three UDP ports published, crossplay on, backups running, and a password the game will actually accept. First month free if your Flux account is new.

Frequently asked questions

Why is my Valheim server not in the server list?

Usually the query port or the password. Valheim advertises itself on UDP 2457, the game port plus one, and a server with 2456 open but not 2457 runs perfectly while never being listed. The other common cause is a server marked public with no password, or a password shorter than five characters, which the server refuses to start with at all.

My server works on direct connect but is not listed. Why?

That combination points almost exclusively at the query port. Direct connections use 2456 and succeed; the listing needs 2457 and never happens. Open the second UDP port and the server returns to the browser without any other change.

Does Valheim need TCP as well as UDP?

No. Valheim is UDP only — 2456 for the game, 2457 for the query and 2458 for crossplay. Opening TCP achieves nothing, and time spent on TCP rules is the most common wasted step in diagnosing this.

Why does the server refuse to start at all?

Check the password before anything else. Valheim requires at least five characters for a public server, and it refuses to start if the password appears inside the server name or the world name — a rule that catches people who name the server after the password so their friends remember it.

How long until my server appears after a fix?

A minute or two, once it registers successfully. If it has not returned after a restart and a few minutes, the cause was not the one you changed. Go back to the log and read the startup sequence.

Can a host cause this?

Only by publishing the wrong ports, which is visible to you. What a good host removes is the failure modes it controls: publishing 2456, 2457 and 2458, and refusing to let a server deploy with a password the game will reject.