Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Valheim’s “Failed to connect” message is usually caused by one of six conditions: the server never finished starting, it is using the wrong backend for the players’ platforms, Steam-mode ports are not reachable, a Crossplay player is using a local address, a Join code has expired after a restart, or the client and server are on different game versions.
Playing with friends? Godlike.Host runs hosted Valheim servers from 10 data-center locations, with free DDoS protection.
Start at the server console, not the player’s connection screen. Wait for the exact line “Game server connected.” Then identify whether the server was started with -crossplay, use the matching address method, refresh the Join code after every restart, and bring every client and the server to the same patch version.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse this diagnosis order first
- Watch the dedicated-server console until it prints “Game server connected.” If that line never appears, inspect the host log and startup configuration before changing anything on a player’s computer.
- Check the launch mode. A server without
-crossplayuses Steam networking; one started with-crossplayuses the PlayFab Crossplay backend. - For Steam mode, make the configured port and the next port reachable from the Internet, and allow the server process through the host operating-system firewall. Iron Gate’s documented default range is 2456–2457.
- For Crossplay mode, use a current Join code, the server list, or a supported public address. A local or loopback address cannot be used to join a Crossplay server from outside the host.
- Check the patch number in the lower-right corner of every game’s main menu and update the server and clients together.
- Confirm that the platform mix is permitted. Xbox and Microsoft Store players require Crossplay on the server; an Xbox console cannot run the dedicated-server application.
The sections below explain what each check proves and what to do when it fails.
Confirm that the server is actually ready
A process window being open does not mean Valheim is accepting connections. Iron Gate’s dedicated-server guide defines the readiness test: the console must display the exact message “Game server connected.” That line is the boundary between a server-startup problem and a client/network problem.
If “Game server connected” never appears
- Read the host log around startup for an error or a repeated retry.
- Review the launch configuration, including the world name, server name, selected backend, and port setting.
- Keep players from repeatedly trying to join while the process is still initializing; a failed attempt at this stage does not test Internet reachability.
- Restart only after recording the last visible log lines. A restart also creates a new Join code for a dedicated server.
Once the readiness message is present, leave the console running while you test. If the message appears and players still cannot connect, continue with the backend check rather than reinstalling the game.
Identify the backend before changing router settings
The launch argument determines both platform compatibility and the network path. The following comparison uses the behavior documented by Iron Gate.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Backend | How it is selected | Who can join | Network requirement | Address methods |
|---|---|---|---|---|
| Steam | Start the server without -crossplay. |
Steam users only. | The configured port range must be reachable from the Internet; the documented default is 2456–2457. Forward it to the host and permit the server through the operating-system firewall. | Use the server’s externally reachable Steam address and port. |
| Crossplay | Start the server with -crossplay. |
Players from different supported platforms, including Xbox and Microsoft Store players when their clients also use Crossplay. | Traffic is sent through the PlayFab relay, so outside players do not need router port forwarding to reach the server. | Use a current Join code, the server list, or a supported public IP and port. Local and loopback IP addresses are not valid for outside players. |
Do not try to solve a backend mismatch by opening more ports. A Steam-only server will not become available to Xbox or Microsoft Store players merely because its firewall rules were changed; it must be run with Crossplay.
Fix Steam-backend connection failures
Iron Gate describes Internet reachability as the most important Steam-backend requirement. Valheim uses the configured port and the immediately following port. For a default installation, that is 2456 and 2457; the figures are the default documented by Iron Gate Studios in 2024, not a guarantee that every server uses those numbers.
Forward the correct range
- Find the port value in the server’s startup configuration.
- On the router, create forwarding entries for that port and port+1 to the local IP address of the computer running the dedicated server.
- If the configuration uses a nondefault port, forward that chosen port and its next port instead of blindly forwarding 2456–2457.
- Ensure the address and port supplied to players match the externally reachable endpoint associated with the forwarding rule.
Forwarding the wrong computer, forwarding only one of the two ports, or leaving the server on a different configured port produces the same symptom as a dead server: players may see no server or receive “Failed to connect.”
Rank #2
- Viking Game laminated laptop stickers All approx 3"-4" in length
- Laminated, Not UV Proof. Will fade in sun. Best used indoors.
- Great for Laptops, Phones, Computers, Tablets and more!
- Handmade by a Stay at Home Small Business Mama!
Allow the process through the host firewall
Port forwarding ends at the host computer. The operating-system firewall must also allow the Valheim dedicated-server process to receive traffic on the configured range. Add or enable the rule while the server is stopped if your firewall requires an executable selection, then start the server again and wait for “Game server connected.” A router rule cannot override a host firewall rule that still blocks the process.
Recommended Free Tools
When a Steam player can join locally but friends cannot
A successful connection from the same home network proves only that the server process is running and that local routing works. It does not prove that the Internet-facing address, forwarding rule, and firewall are correct. Test from a player outside the host’s local network after confirming both ports and the firewall rule.
Fix Crossplay address and relay problems
Crossplay changes the test you should perform. Iron Gate states that the Crossplay backend transmits data through a relay server and therefore does not require port forwarding for access from outside the local network. Opening Steam-mode ports is not the remedy for a Crossplay failure.
Do not use a local or loopback IP
A Crossplay server cannot be joined with a local address such as an address assigned only inside the host’s home network, nor with a loopback address that points back to the joining device. A local-IP test can fail even when the relay and server are working normally. Use one of the supported methods instead:
- the current Join code;
- the server listing; or
- the supported public IP and port shown for the server.
Check the relay path without changing the router
Leave the server running, obtain a fresh Join code, and try from the intended platform. If the server is visible in the list but joining fails, compare the client version and platform eligibility before editing firewall or port settings. Those settings belong to the Steam path, not the Crossplay relay path.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Refresh the Join code after every dedicated-server restart
Iron Gate’s Crossplay FAQ, republished 7 February 2025, says that a Join code appears in the pause menu when a server is started through the game or as a dedicated server. To use it, copy the code from the pause menu and paste it under Join Game > Add server.
The code is not permanent. Steam patch notes dated 4 October 2022 state that the Join code is regenerated whenever the dedicated server restarts. An old code can therefore fail even when the server has reached “Game server connected.” Ask every player to discard the previous code and enter the one displayed by the current server process.
Join-code checklist
- Read the code from the running server, not from an old message or screenshot.
- Paste it under Join Game > Add server, rather than treating it as a normal IP address.
- Repeat the process after every dedicated-server restart.
- If the current code still fails, verify Crossplay mode and patch parity before troubleshooting unrelated network hardware.
Bring the server and every client to the same version
Valheim’s Crossplay patch notes warn: “As always, make sure your game has the same patch version as your friends’, or else connecting to each other might not work.” Check the version number printed in the lower-right corner of the main menu on each player’s device, and check the version used by the dedicated server.
What to do after an update
- Stop the dedicated server cleanly.
- Update the server installation to the same patch as the clients.
- Update or verify each client through its platform.
- Start the server and wait for “Game server connected.”
- Generate and distribute a new Join code if the server uses Crossplay.
Do not use a previously working code as proof that versions match. A code can be current while a client is still on an older build, and the resulting connection failure can look identical to a networking problem.
Check Xbox, Microsoft Store, and Steam eligibility
An Xbox console can join a dedicated server only when Crossplay is enabled on both the Xbox client and the server. The console cannot run the Valheim dedicated-server application itself. The server must run on a separate supported host, and it must use the Crossplay backend.
Rank #4
- Valheim Boar Loves You quote. A perfect design for fans of the best selling Viking game.
- An amazing and unique design which is also perfect as a gift.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
- Steam-only server: suitable for Steam clients; it is not a route for Xbox or Microsoft Store players.
- Crossplay server: can support players from different platforms when each client is using the compatible Crossplay build and the server was started with
-crossplay. - Mixed group: choose Crossplay before distributing the address or Join code, then make sure every player’s game is updated to the same patch.
If a Steam friend can join but an Xbox friend cannot, first verify the launch argument and Crossplay status. Do not assume that a successful Steam connection proves cross-platform eligibility.
A complete step-by-step troubleshooting procedure
Use this sequence when the cause is not obvious. Stop as soon as the failed check identifies the problem.
- Capture the symptom. Record whether the server is invisible, visible but refuses the join, or accepts the player and then disconnects. Note the exact wording of the error.
- Check readiness. On the host, confirm the console says “Game server connected.” If not, stay in the server log and startup configuration; client-side testing is premature.
- Read the launch mode. Confirm whether
-crossplayis present. This determines whether the Steam or PlayFab Crossplay path is being tested. - Match the platform group. If any intended player is on Xbox or Microsoft Store, the server and those clients must use Crossplay.
- Choose the proper address. Steam players need the externally reachable Steam endpoint. Crossplay players should use the server list, a fresh Join code, or the supported public address; never use a local or loopback address for an outside player.
- Apply the network check appropriate to the backend. For Steam, verify forwarding of the configured port and port+1 and the host firewall rule. For Crossplay, do not add port forwarding as a substitute for a current code or correct platform mode.
- Check versions. Compare the lower-right main-menu version on each client and the server build. Update all sides to the same patch.
- Regenerate access data. After any dedicated-server restart, obtain and distribute the new Join code.
- Retest from the correct location. A local test and an outside-network test answer different questions. Use an outside player to validate Internet reachability for Steam mode.
Match the symptom to the likely cause
The server never appears in the list
- The process may not have reached “Game server connected.”
- A Steam server may be using an unreachable or mismatched port range.
- The player may be looking for a Steam server while the host started Crossplay, or vice versa.
- The server and client may be on different patches.
Start with the host console, then confirm backend and version before changing client settings.
The server appears, but joining returns “Failed to connect”
- For Steam mode, recheck both forwarded ports, the destination host, and the operating-system firewall.
- For Crossplay, replace the old Join code, avoid local/loopback addressing, and confirm the relay-compatible backend is active.
- For any backend, compare the server and client patch numbers.
A Join code worked yesterday but not after maintenance
Dedicated-server restarts regenerate the code. Copy the current code from the pause menu and enter it through Join Game > Add server.
Steam players connect, but an Xbox player cannot
The server is likely running Steam mode or Crossplay is not enabled on both sides. An Xbox console cannot host the dedicated-server application, and a Steam-only backend does not provide a path for Xbox or Microsoft Store clients.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
A local-IP test fails on Crossplay
That result is expected for an outside player because Crossplay does not accept local or loopback addressing. Test with the server list, a fresh code, or the supported public endpoint instead.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Account for restart, save, and backup behavior
Connection troubleshooting often involves restarting the dedicated server, so protect the world before doing repeated tests. Iron Gate’s 2024 dedicated-server documentation lists a default world save interval of 1,800 seconds (30 minutes) and four automatic backups: one short-interval backup and three backups at longer intervals. These are defaults, not evidence that a particular installation has retained every recent action.
Before changing startup settings, note the current configuration and copy important world data according to your normal backup procedure. After a restart, wait for the readiness message and issue a new Join code before inviting players back.
When self-hosting is the obstacle
If you cannot control the router, assign a stable host address, or maintain firewall and server updates, managed Valheim dedicated-server hosting is an alternative to operating the network path yourself. Confirm the provider supports the backend and platforms your group needs, gives you access to current server logs, and explains how it handles restarts, updates, saves, and backups. Hosting does not remove the need for version parity or a fresh Crossplay Join code after a restart.
Escalate with evidence instead of repeating guesses
Iron Gate’s FAQ directs bug reports to its support form and asks for as much information as possible. Include a compact evidence package:
- the exact error text and the stage at which it appears;
- each affected player’s platform;
- whether the server uses Steam mode or was started with
-crossplay; - the server log lines around the failed attempt;
- the server version and every client version;
- whether the console ever printed “Game server connected.”;
- the address method used: server list, public endpoint, or Join code; and
- for Steam mode, the configured port and confirmation that forwarding and the host firewall rule target the same computer.
This information separates a startup defect, backend mismatch, stale Join code, version mismatch, and reachability problem far more effectively than repeated reinstallations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
