Valheim server ports and connection troubleshooting

A server missing from a browser and a server nobody can reach are different problems. Before changing your router, ask one outside player to try the intended direct connection method. Write down the exact result rather than “it doesn’t work.”

Keep three facts together: the backend you launched, the address or code you shared, and the server version. If different friends are using different details, you are debugging several problems at once.

The default game-port pair is 2456–2457. If you changed the starting port, use that value and the following port instead. Match the startup script, router rule, and address you give your friend. A copied tutorial that uses a different port can leave all three looking individually reasonable.

Next, check the router’s forwarding target. It needs to point at the machine actually running the server, rather than an old local address assigned to it last week. Compare the rule with that machine’s current local network configuration.

Check the host firewall separately. Router forwarding does not create an allowance on the computer itself. Keep the scope narrow and use the relevant server executable or documented game traffic. If you are unsure whether your internet connection permits inbound hosting, ask your ISP about public addressing and carrier-grade NAT before buying another router.

Iron Gate documents crossplay as a relayed connection path. Router port forwarding is not required for that backend. Its guide also notes that a local or loopback address cannot be used to connect to a crossplay server.

That distinction matters during testing: a server can be working while a connection method chosen for another backend fails. Confirm the server started with the intended arguments, obtain the current connection details, and have a friend try them exactly as supplied.

Do not switch backends, reinstall the server, and change the world in the same attempt. Change one variable, repeat the same outside connection test, and record whether the result improved.

Read the startup output before trusting a browser listing. Look for the documented ready state, then test the connection route independently. A process existing on the machine does not prove it has reached a usable state.

• Check that the server and players are on compatible versions.
• Confirm the intended script is the one currently running.
• Compare the shared address or join code with the current startup output.
• Test from a different internet connection.
• Preserve the log and exact error if the attempt fails.

If only one person cannot join, compare their connection method with a player who can. If nobody can join, focus on the server and its network path. That split keeps a local client issue from turning into a server rebuild.

A useful support request includes the platform, backend, server version, approximate failure time, join method, and what happened during an outside test. Include relevant log lines, with public identifiers and credentials removed where appropriate.

Avoid posting your admin password, private account details, or full router screenshots. Describe the forwarding rule’s purpose and destination without exposing the rest of your network. If you later solve the issue, add the exact change to your operator note so the next update does not restart the investigation.