---
title: Valheim server not showing up? -public 1, the query port and crossplay explained
description: Valheim 1.0 brought a new wave of dedicated servers, and the same three problems with them: the server isn't in the community list, friends can't find it, or a status tool says it's offline while you're playing on it. Almost all of it comes down to -public, port + 1 and crossplay. Here's how each works, how to check your server from outside, and how to know when the world is really down.
canonical: https://watchfor.io/blog/valheim-server-not-showing-up
---

# Valheim server not showing up? -public 1, the query port and crossplay explained

2026-11-16 · WatchFor Team · Game servers · game-servers, valheim, networking

Valheim 1.0 brought a new wave of dedicated servers, and the same three problems with them: the server isn't in the community list, friends can't find it, or a status tool says it's offline while you're playing on it. Almost all of it comes down to -public, port + 1 and crossplay. Here's how each works, how to check your server from outside, and how to know when the world is really down.

Valheim left early access with **1.0 on September 9, 2026**, and arrived on
PlayStation 5 and Nintendo Switch 2 at the same time, with crossplay
([Steam announcement](https://store.steampowered.com/news/app/892970/view/1834602721196984)).
A lot of groups rented a server for the occasion, and a lot of Discord
threads since then start the same way: *"the server isn't in the list"*,
*"I can't find it to join"*, *"the status bot says it's offline but I'm
literally in it"*.

Valheim's dedicated server is simple, but three of its settings decide
whether anyone outside can see it. Get them right and the list, your friends
and your monitoring all agree.

## The launch line that matters

The dedicated server (Steam app 896660) ships with a start script.
Stripped to what affects visibility:

```bash
./valheim_server.x86_64 \
  -name "Our Viking World" \
  -port 2456 \
  -world "Dedicated" \
  -password "longer-than-5" \
  -public 1
```

| Flag | What it does for visibility |
| --- | --- |
| `-port 2456` | The game port. The server also uses the next port, 2457, for the Steam query. |
| `-public 1` | Lists the server in the community list **and** makes it answer queries. `-public 0` = invisible to everything outside. |
| `-password` | At least five characters, and not part of the server name, or the server refuses to start. |
| `-crossplay` | Routes connections through PlayFab so console and Microsoft Store players can join; changes what queries can see (below). |

Iron Gate's [dedicated server guide](https://www.valheimgame.com/support/a-guide-to-dedicated-servers/)
puts the port rule plainly: the server uses the specified port and port + 1.

## Problem 1: the server isn't in the community list

Work through these in order:

1. **`-public 1`?** A private server never registers, so it can't be listed.
   This is the most common cause by far, because many hosting templates
   default to private.
2. **UDP 2456 and 2457 forwarded?** Forwarding only the game port lets
   friends join by IP but keeps the server out of the list: the list fills
   its rows by querying 2457.
3. **Did you change `-port`?** Then the query port moved too. `-port 2500`
   means the query answers on **2501**.
4. **Give it a few minutes.** The community list is large and refreshes
   slowly; search by exact name rather than scrolling.

If it still isn't there, test it as the list would (next section). A server
that answers the query but isn't listed is a list problem; one that doesn't
answer is your problem.

## Problem 2: a status tool says offline, you're playing on it

Almost always one of:

- **The tool asks 2456.** The game port doesn't answer status queries. Point
  the tool at **2457** (game port + 1).
- **The server is private.** With `-public 0` Valheim answers no queries, so
  every outside tool sees silence. That's by design.
- **The tool asks from somewhere your firewall blocks.** If your host or
  router filters UDP by source, home connections may get through while data
  centres don't.

To check by hand from another network, any Steam query tool works, for
example [python-a2s](https://github.com/Yepoleb/python-a2s):

```python
import a2s
info = a2s.info(("203.0.113.10", 2457), timeout=5)   # game port + 1
print(info.server_name, f"{info.player_count}/{info.max_players}", info.version)
```

A reply with your server's name means the query side is fine. A timeout on
2457 with `-public 1` set means the port isn't reachable from where you
asked.

## Problem 3: crossplay changes the picture

`-crossplay` lets PS5, Xbox, Switch 2 and Microsoft Store players join a PC
server. It also changes how the server is reached: connections go through
PlayFab, players join with a **join code**, and port forwarding stops being
required for them.

For outside observers that has two consequences:

- **Population from the Steam query is unreliable.** Server-query projects
  have documented crossplay Valheim servers reporting **0 players** to the
  Steam query ([GameDig's notes](https://github.com/gamedig/node-gamedig/blob/master/GAMES_LIST.md)).
  The server can be full and still say 0.
- **"Not showing join code"** is its own failure: the server is running but
  couldn't register with PlayFab. Restarting the server is the usual fix;
  check its log for the backend connection.

If your group is PC-only, you don't need `-crossplay`. If you need it, keep
in mind that outside checks can confirm the server answers, but shouldn't be
trusted for player counts.

## After an update: everyone gets "incompatible version"

Valheim clients and servers must run the same version. When Steam updates
the game and your host hasn't updated the server yet, nobody can join, and
the server looks perfectly healthy. The version string in the query reply
tells you which build the server runs; compare it with the game's current
version after every patch. With 1.0 out, patches are less frequent than in
early access, which makes them easier to forget.

## Knowing when the world is really down

A Valheim server is usually a friends' world on a rented box, and the first
sign of trouble is someone who can't join after work. A check from outside
catches it first.

A WatchFor **Game server** monitor with the **Valheim** preset queries the
server on the game port + 1 (2457 by default) over UDP, the same question
the community list asks, from the regions you choose. Every check records
the server's name, players and slots, version and latency. If the server
runs without `-public 1`, the error says so instead of a bare "timeout".

- **Confirmed before anyone hears about it.** One lost UDP packet isn't an
  outage: a failed check is repeated before an incident opens, from the
  monitor's other locations when it has several (how many depends on your
  plan).
- **Your Discord, no bot.** Alerts go to a channel webhook: which server is
  offline and how many were on it, then a second message when it's back.
- **A page for the group.** A status page shows the server's state, uptime
  and a row with the address to copy, so nobody has to ask "is it up?" every
  evening.

![The Acme Games status page: each game server listed with its uptime bar, players out of slots from the latest check, and a Connect or Copy address button.](/marketing/game/status-page.webp)

Game server monitoring is part of the paid plans from Starter, counted
toward the plan's normal monitor total; see [pricing](/pricing). The
[Valheim page](/game-server-monitoring/valheim) has the ports and what the
monitor reads.

## Checklist

1. `-public 1`, a password of five characters or more, not part of the
   name.
2. Forward UDP on the game port **and** the port after it.
3. Query port = game port + 1. Give status tools that one.
4. PC-only group? Skip `-crossplay`. Crossplay? Don't trust outside player
   counts.
5. After every Valheim patch, check the server's version matches the game.

## Frequently asked questions

### Why is my Valheim server not showing up in the community list?

The usual causes: it runs with `-public 0`, the query port (game port + 1, 2457 by default) isn't forwarded over UDP, or the list hasn't refreshed yet. Start it with `-public 1`, forward UDP 2456 and 2457, and search by name. Players can also add it as a Steam favourite with `your-ip:2457` or join by IP.

### What ports does a Valheim dedicated server use?

The port you set with `-port` and the one after it, UDP 2456 and 2457 by default, according to Iron Gate's dedicated server guide. Players join on 2456; the Steam server query answers on 2457. With `-crossplay`, connections go through PlayFab and no port forwarding is needed for players.

### What does -public 1 do?

It lists the server in the community server list and makes it answer Steam server queries. With `-public 0` the server is private: friends can still join by IP or join code, but it is invisible to the list, to status checkers and to monitors.

### Why does my crossplay Valheim server show 0 players?

Crossplay servers run through PlayFab, and server-query tools have documented that they report 0 players over the Steam query. The server can still be up and full; treat the population number from outside as unreliable for crossplay servers.

### How do I get a Discord message when my Valheim server goes down?

Use a monitor that queries the server on its query port and posts to a Discord channel webhook once the outage is confirmed. No bot is needed: you create the webhook in the channel settings and paste it into the monitor's notification channel.

---

Canonical page: https://watchfor.io/blog/valheim-server-not-showing-up · All articles: https://watchfor.io/blog/all.md · Site guide: https://watchfor.io/llms.txt
