Valheim server not showing up or refusing connections

Confirm that the world finishes loading

Open the server logs. A panel saying Running may only confirm that a process exists. Look for completed world loading and the online service connection. A restart loop during world loading calls for save or mod investigation.

Compare client and server versions, including any test branch. After an update-related incident, finish installation and restart cleanly before changing network settings.

Separate visibility from accessibility

The -public 0 setting deliberately hides the server. Try the direct details from the panel or a crossplay join code. If direct access works, investigate browser filters and visibility rather than reinstalling the server.

Without -crossplay, the server uses the Steam backend. A player from another platform cannot fix that by selecting another port. The join code also does not replace the world password.

Check the network for your backend

For a self-hosted Steam server, check the firewall and configured ports. Valheim uses the selected port and the next one: 2456–2457 by default. Test from another internet connection to distinguish local access from outside access.

Crossplay uses a relay and cannot be joined through local or loopback IP addresses. With rented hosting, retain the provider's assigned ports and request a connectivity check if every client fails.

Collect useful evidence for support

Supply the version, backend, timestamp, exact error and a log excerpt with passwords removed. Say whether a separate fresh test world starts and whether players on different networks fail. Back up first and keep the main world intact.

This evidence helps distinguish a configuration repair, damaged files and a network issue. Paying for more resources becomes relevant when actual saturation has been identified.

Frequently asked questions