PC 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 & 11Crashes, 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 minuteIf your Valheim server is missing from the Community list, first identify which backend it uses. A server started with -crossplay uses PlayFab’s relay-based Crossplay backend and is normally joined with a code; it may not appear in the Steam community browser. A server without -crossplay uses the Steam backend, where browser visibility depends on -public 1, successful registration, firewall access, and correctly forwarded ports.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Valheim servers with free DDoS protection and up to three free backups a day.
Use the checklist below in order. It separates a discovery problem from a connection problem, so you do not waste time changing router settings on a Crossplay server or searching the Steam browser for a server that is intended to be joined by code.
As an Amazon Associate I earn from qualifying purchases.
Start by identifying the server backend
The launch command determines how Valheim advertises and connects to your server. Open the copied start_headless_server.bat file on Windows or the equivalent Linux launch script and look for -crossplay.
- With
-crossplay: the server uses the PlayFab Crossplay backend. Traffic is relayed, outside players do not need a router port-forwarding rule, and the normal invitation method is a Crossplay join code. - Without
-crossplay: the server uses the Steam backend. Community-browser visibility relies on internet-reachable ports, registration with the backend, firewall permission, and the-publicsetting.
These backends have different discovery rules. “Not listed” does not mean the server process is stopped, and a server that accepts an IP connection can still be absent from a browser listing.
| Comparison | Steam backend | Crossplay backend |
|---|---|---|
| How it is selected | Do not include -crossplay in the launch command. |
Include -crossplay. |
| Typical discovery | Community browser, provided the server is public and registered. | Crossplay join code; it may not appear in the Steam community browser. |
| Platform reach | Steam-oriented access. | Cross-platform access through the Crossplay system. |
| Network requirement | Forward the configured server ports to the host and permit the process through the firewall. | PlayFab relay infrastructure handles outside traffic; router port forwarding is not required. |
| Address workflow | Players use the reachable address and configured port, or find the public listing. | Players use the join-code workflow; a local or loopback address is not an outside-hosting solution. |
Fix a Steam-backend server that is missing
1. Make the server public
In the launch script, check the visibility argument. The official dedicated-server guide defines -public 1 as the setting that makes a server visible in the browser and identifies 1 as the default. If the script contains -public 0, the server is deliberately hidden from the browser even if every network setting is correct.
Change the argument to -public 1, save the script, and restart the server program. Make sure you edit the script that is actually being used; changing an unused copy has no effect. If the argument is absent, adding -public 1 makes the intended behavior explicit and avoids confusion when several launch scripts exist.
2. Wait for “Game server connected”
Watch the dedicated-server console during startup. Do not test browser discovery until it displays the exact message “Game server connected.” Iron Gate’s guide defines that message as the point at which the server is up and ready to accept connections.
If the message never appears, treat the issue as startup or registration rather than a browser-search problem. Leave the console open while checking the launch arguments and firewall. A process window existing by itself does not prove that the backend registration succeeded.
3. Approve the Windows firewall prompt
When Windows asks whether to allow the server through the firewall, allow the dedicated-server program on the networks appropriate for your setup. A blocked process can prevent registration or incoming connections even when the router rule is correct.
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!
If the prompt was dismissed earlier, review the Windows firewall rules for the server executable and create or enable the required allow rule. Restart the server after changing the rule, then wait again for “Game server connected.”
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →4. Forward the correct ports
For the Steam backend, Iron Gate’s guide identifies ports 2456–2457 as the default range. Forward the configured range from the router to the computer running the server. The router’s destination must be the host’s current local address, not a different PC or an old DHCP address.
The forwarded range must match the value in the launch script. If the command uses a custom -port, forward that port and the required adjacent port in the configured range rather than blindly forwarding 2456–2457. A mismatch between the script and router is a common reason a server can appear to run locally but fail to register or accept outside traffic.
After saving the router rule, restart the server and wait for the connection message. If the host receives a new local IP address, update the forwarding destination before testing again.
5. Search only after registration and networking are ready
Once the console shows “Game server connected,” -public 1 is set, the firewall permits the program, and the configured ports are forwarded, refresh the Community list. Browser updates can lag behind a restart, so search again after the server has completed registration rather than judging it from the first seconds of startup.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Use Crossplay when you want relay-based access
What changing to Crossplay does
Add -crossplay to the launch command when you want the PlayFab Crossplay backend. The official guide states that Crossplay transmits data through a relay server and therefore does not require port forwarding for access from outside the local network.
That removes the router-forwarding step, but it changes discovery. A Crossplay server may not be shown in the Steam community browser. Searching that list is therefore the wrong test for a server intentionally running on Crossplay.
Give players the join code
Use the code provided by the game/server flow and send it to the players who need to connect. The Crossplay FAQ explains that the code can be copied by clicking it and sent to a friend.
On the joining player’s client, use Join Game → Add server, then paste the Crossplay code into the Add server flow. This is the expected Crossplay discovery path; it does not require the server to appear in the Steam-oriented list.
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 →Repair Windows errors before they cause bigger problemsFix Now →Do not substitute a local address for the code
A local or loopback address identifies the host only inside its local network. It cannot provide outside access to a Crossplay server. For Crossplay, use the supported join-code workflow. For a Steam-backend server, use the reachable public address and configured port or the public browser listing.
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
Choose between Steam and Crossplay deliberately
The right backend depends on how players are distributed and how much network configuration you want to maintain. Use the following decision points before changing a working server.
- Choose Steam backend when Steam community-browser discovery is important and you can forward the configured ports to the host.
- Choose Crossplay when players need cross-platform access or you want to avoid router port forwarding and are comfortable distributing a join code.
- Do not switch solely because the server is absent from the Steam list. If
-crossplayis present, absence from that list is consistent with the backend’s discovery method. - Keep the launch script and player instructions aligned. A Steam server should be advertised as a browser/IP connection; a Crossplay server should be advertised with its code.
Why friends can connect by IP but cannot see the listing
The server is reachable but intentionally hidden
If friends connect directly while the Community list remains empty, check for -public 0. Direct access and browser visibility are separate controls. Setting the server public and restarting is the fix for an intentionally hidden Steam server.
Recommended Free Tools
The browser and the backend do not match
A Crossplay server can be reachable through its join code while remaining absent from the Steam browser. In that case, direct code-based access is evidence that the chosen backend is functioning; it is not a reason to add Steam port-forwarding rules.
The listing is delayed while registration completes
A server that has just started may not be listed until it has registered. Confirm “Game server connected” first. If that message is missing, troubleshoot startup, firewall permission, or backend configuration before repeatedly refreshing the browser.
Check version compatibility before changing networking
Iron Gate’s Crossplay announcement warns that the game version and the versions used by friends should match. A version mismatch can block connection even when the server is configured correctly and the join method is right.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
- Confirm the host’s Valheim installation has finished updating.
- Have each player check that their client is on the same version.
- After an update, restart the dedicated server so it registers with the current game build.
- Test again using the backend’s correct method: browser/IP for Steam or join code for Crossplay.
Do not use successful local access as proof that every remote player has a compatible build. Discovery and version compatibility are separate checks.
A complete troubleshooting sequence
Follow this order to avoid mixing Steam-only fixes with Crossplay settings.
- Open the active launch script. Identify whether
-crossplayis present and note the value of-publicand-port. - Select the matching discovery method. Use the Community list for a public Steam-backend server; use the join code for Crossplay.
- Start or restart the server. Keep the console visible while it initializes.
- Confirm registration. Wait for the exact text “Game server connected.”
- Check firewall permission. Allow the dedicated-server program when Windows prompts, or correct the rule if the prompt was previously denied.
- For Steam only, verify visibility. Set
-public 1; remove or change-public 0if the server should be listed. - For Steam only, verify forwarding. Forward the configured port range to the host and ensure it matches
-port. The default range in the official guide is 2456–2457. - For Crossplay only, obtain a fresh code. Copy the displayed code and send it to the players; do not rely on a local or loopback IP from outside the host’s network.
- Check versions. Make sure the server and every joining client use matching game versions.
- Retest with the correct client path. Refresh the Steam browser only for Steam backend, or use Join Game → Add server for Crossplay.
Symptom-based fixes
“The server is running, but nobody sees it in Community”
First look for -crossplay. If it is present, use the join code instead of the Steam browser. If it is absent, verify -public 1, wait for “Game server connected,” allow the process through the firewall, and check the 2456–2457 default forwarding range or the custom -port range.
“Friends connect by IP, but the name is not listed”
Direct IP access does not automatically make a server public. Check whether -public 0 is hiding the Steam server. If the server uses Crossplay, IP-based access from outside the local network is not the intended workflow; distribute the join code.
“Crossplay works for one player, but another cannot join”
Confirm that the second player is using the Crossplay Add server flow and the current code, then check that the player’s game version matches the server and the other players’ versions. Router port forwarding is not the corrective step for a Crossplay backend.
“The console never says Game server connected”
Do not diagnose this as a browser-cache issue. Recheck the launch arguments, firewall permission, and—if using Steam—the forwarding destination and port range. The server is not confirmed ready until that exact registration message appears.
When managed hosting may be simpler
Running a dedicated server yourself requires maintaining the launch script, choosing the backend, handling firewall prompts, and—on Steam—keeping router forwarding aligned with the configured port. A managed Valheim dedicated-server hosting service can be considered when you do not want to maintain those tasks. The decision is operational rather than a requirement for fixing this particular listing problem: the documented fixes are configuration and connectivity changes, not a special hardware purchase.
Before moving a world, record the current backend choice, launch arguments, world data, and the player connection method. A host that uses Steam discovery will have different instructions from one that uses Crossplay codes.
Quick Recap
What a healthy setup looks like
| Setup | Launch configuration | Player instructions | What to expect in Community |
|---|---|---|---|
| Public Steam server | No -crossplay; -public 1; router forwards the configured -port range; firewall allows the server. |
Find the public server or connect using its reachable address and port. | It can appear after the console reports “Game server connected.” |
| Private Steam server | No -crossplay; -public 0. |
Use the supported direct connection method rather than expecting a public listing. | It is intentionally hidden. |
| Crossplay server | -crossplay; relay-based backend. |
Copy the code and use Join Game → Add server. | It may not appear in the Steam community browser. |
Key facts to keep with your server notes
-crossplayselects PlayFab Crossplay; omitting it selects the Steam backend.-public 1makes a Steam-backend server visible in the browser;-public 0hides it.- The readiness message is exactly “Game server connected.”
- Steam’s documented default ports are 2456–2457, but forwarding must follow the configured
-port. - Crossplay uses relay infrastructure and does not require outside port forwarding.
- Crossplay players should receive the join code and enter it through Join Game → Add server.
- Local and loopback addresses are not substitutes for an outside Crossplay connection.
- The game and joining clients should use matching versions.
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.
