Valheim multiplayer setup and connection fixes

Valheim supports up to ten players. For a small group, one player can host a world from the game. A dedicated server keeps hosting separate from that player's game session. Crossplay lets supported platforms connect, but patch availability can temporarily prevent it.

As of the September 12, 2026 check, Switch 2 could not crossplay with other platforms. Iron Gate's September 11 hotfix note said its update was not yet available. Check the current hotfix notice before changing network settings for this specific problem.

Host a world for friends

Choose your character and world, enable Start Server, set a password and enable Crossplay when guests need it. Start the world, then share its joining details privately. Guests select Join Game and use the appropriate server entry or joining option. For a community server, ask the host for an invitation and password. Appearing in the public list does not make a server open to everyone.

The hosting player must keep the session running. For an existing world, make a complete backup before moving it to another host.

Set up a dedicated server

Install Valheim Dedicated Server from Steam's Tools library. Copy the supplied startup script before editing it, since updates can replace the original. Set the server name, world name and password in your copy, then launch that copy. The supplied Windows script is start_headless_server.bat; Linux uses start_server.sh. The official server guide covers installation and the full settings list.

Wait for Game server connected in the server output before testing a connection.

Admins, permissions and multiple worlds

Permission files live in the server save directory: adminlist.txt grants administration, bannedlist.txt blocks players, and permittedlist.txt restricts entry to listed players. Use each player's exact platform ID from the server log or in-game F2 panel, one per line. A populated permitted list can lock out an otherwise valid guest. Opening the console does not grant admin access; the command reference explains the separate checks.

Keep separate world names, save locations and network settings when running multiple server instances. To move or change a world, preserve its matching files and select its actual name; a seed alone does not transfer buildings or progress. Use the backup and transfer guide. A dedicated host can stay online when you leave, though some gameplay systems still require an active area to update.

Server performance depends on the world, player count and mods. When investigating lag, record CPU and memory use, active players and where the slowdown happens. On Linux, use the installed server's dependency errors to identify missing libraries. An old setup guide may list different requirements.

Hosted panels and cloud machines

Rented hosts use the same vanilla settings, but their panels and file locations differ. Use the instructions for your existing provider:

For other providers, use their current Valheim support page for updates, plugins and save locations. Check which game branch the panel runs and compare it with your client's branch. Copy a backup outside the service before replacing files. For command permissions, use the game's command reference alongside the host's panel instructions.

AWS, Azure, Oracle Cloud, DigitalOcean and similar services provide the host machine. AWS EC2 setup and Azure Linux VM setup explain how to create those machines. You still need a machine that can run the Valheim server. Check the operating system and CPU compatibility, keep save backups outside disposable instances, and apply the Steam or crossplay network rules below. Free credits expire, and a free VM tier may not have enough resources for your world. For automated installation, follow Valve's SteamCMD documentation and your host's deployment instructions. To install by hand, use Steam Tools as described above.

Docker, NAS and ARM hosts

Docker images are community packaging around the dedicated server. The former lloesche/valheim-server-docker repository now redirects to community-valheim-tools. Its instructions map persistent configuration and worlds to /config, and downloaded server files to /opt/valheim. Check the actual host folders behind those mounts before replacing a container. A new container with the wrong empty save mount can look like a lost world.

The project documents Compose, Synology, QNAP and Portainer details, including startup-command changes. Follow those instructions for that image; other images and provider panels can use different paths. Record both the image release tag and the game server version when asking for help.

Before using an ARM machine or Raspberry Pi, check how the server will run on its CPU. The Valheim ARM project targets ARM64 and AMD64 hosts. This is a community option, so check compatibility with your game version and mods. Check that project's current instructions and issues for your CPU and chosen image, then test a disposable world before moving a save.

For BepInEx, VR and client/server plugin requirements, use the mod compatibility guide.

Choose the right connection path

The official server guide distinguishes two backends:

• The Steam backend uses ports 2456 to 2457 by default. Check the host's firewall and router forwarding for the configured ports.
• The crossplay backend uses a relay and does not require port forwarding. Join through the server list, join code or public IP and port. Local IP addresses and loopback addresses do not work for this backend, even when both devices are on the same network.

If a local address fails on a crossplay server, try its join code or public address.

Fix an incompatible-version error

Update the game clients and the dedicated server, then restart them. Check whether someone is using a public test branch or an old server installation. If mods are involved, check the loader and mod versions too.

Displayed version strings do not always need to be identical. The September 11 notes identify Xbox 1.0.11 as identical to 1.0.10 on other platforms, while 1.0.12 was a Steam-specific crossplay fix. Valheim also checks network compatibility when peers connect. Check the developer's patch compatibility notice before treating different version numbers as the cause.

The server is missing, or only one player cannot join

Check the server output first. Confirm it is running, connected and loading the expected world. Confirm its advertised name and whether public listing is enabled. For a crossplay server, try the join code while the host checks the session details.

If other guests can join, record the affected player's platform, release branch, joining method and exact error. If nobody can join, focus on the host's backend and configuration. Server access lists can also restrict entry. The September 11 patch fixed ban/whitelist handling for old and new player-ID formats, so update before diagnosing an old installation's list behavior.

For a client that fails before joining any world, use the installation checks. Keep a copy of server configuration and saves before making changes; deleting a world is not a connection test.