Vintage Story: Can't connect to a server
Fix a Vintage Story connection. Match the exact game version, sync required mods, add the server in Multiplayer, open TCP and UDP on port 42420, then check the default whitelist and password.
If Vintage Story cannot connect, work through these checks in order. Do not delete the save first. The game is strict about version, so a one-patch gap refuses the handshake.
Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.
1. Match the exact game version
The client and dedicated server must run the same Vintage Story release, including the patch number.
Read the version on the player's main menu
Note the full string, not just 1.20.
Update the dedicated server to that build
Stop the server. On berrybyte, Auto Update pulls the configured channel on the next start. Restart once after the patch is live. Pin both sides to stable or both to unstable. Do not mix them.
Compare the server log
The version printed at startup must match the client exactly.
If you do not want to pin versions by hand, rent a Vintage Story server that stays on the current stable.
2. Sync the required mods
Vintage Story lists missing or mismatched mods at connect. The server will not silently skip a required ID.
Read the refusal list
The client dialog names the mods that do not match.
Use the download prompt
Let Vintage Story download the server and universal mods offered by the connection screen. Install a matching client build manually when the mod does not support automatic download.
Restart both sides
A newly dropped mod is read at boot.
3. Add the server in Multiplayer
The dedicated-server guide calls this control Add new server.
Copy Server address
On berrybyte, copy Server address from Overview. Do not
assume port 42420.
Create the server entry
Launch Vintage Story, open Multiplayer, click Add new server, enter the host and port, then choose Create.
The official dedicated-server guide documents this client path and the current network requirements.
4. Check TCP and UDP on the game port
The documented default is 42420. Vintage Story versions 1.20 and newer need TCP and UDP on that same configured port.
Use the port the server bound
On berrybyte, Overview is the source of truth. On a
self-hosted box, read serverconfig.json.
Forward both protocols (self-host)
Every firewall and router between the machine and the internet must allow TCP and UDP on that port.
berrybyte opens the allocated port for you. Self-hosters who are fighting NAT can rent a Vintage Story server that already has it reachable.
5. Check the default whitelist
Dedicated servers enable whitelist mode by default from Vintage Story 1.20 onward. Add the player's exact account name from Console:
/player PlayerName whitelist onRun /list whitelisted to inspect the current entries. Set
WhitelistMode to Off in serverconfig.json when the server should accept
any authenticated player, then restart.
The Vintage Story account name is the identity the allowlist reads. Copy it from the player to avoid spelling and capitalization errors.
6. Share or clear the password
A passworded world rejects a blank or mistyped string.
Read the configured password
On berrybyte, open Settings → Game Settings.
Send the exact string, or clear it
Check capitalisation and characters that chat apps rewrite. Clear it for a public test, then restart.
7. Confirm the world loaded
A dedicated server that failed to open the save is not joinable.
Read Console
Wait until the log says the world loaded.
Check the configured world name
If you uploaded a save, the name in config must match the folder you copied.
If the connection still fails
Confirm Console reached a loaded world. Then check the leftover causes:
- A privilege role refusing the player after whitelist approval.
- An outdated
.dllfrom a previous Vintage Story series. - Check berrybytestatus.com.
Frequently asked questions
Why can't I connect to a Vintage Story server?
Match the exact Vintage Story version first. Then sync the required mods, add the server in Multiplayer, check TCP and UDP on the bound port, and confirm that your player is whitelisted.
Why does Vintage Story say incompatible version?
The client and dedicated server are on different releases, including a mismatch like 1.20.4 versus 1.20.5. Update both sides to the same build. Do not mix stable and unstable.
What port does a Vintage Story dedicated server use?
Port 42420 is the default. Current servers from version 1.20 onward need both TCP and UDP on the configured port. berrybyte opens its allocated port with both protocols.
Why do mods block a Vintage Story join?
Required server mods must exist on the client at the same version. Vintage Story will list the missing IDs. Install those mods, or remove them from the server for a vanilla test.
Why does a new Vintage Story server say I am not whitelisted?
Dedicated servers enable whitelist mode by default from version 1.20 onward. Add the player with /player username whitelist on from the server console, or turn WhitelistMode off when you want an open server.
How do I join a Vintage Story server by IP?
Open Multiplayer, choose Add new server, enter the host and allocated port, then create and join the entry. On berrybyte the address appears under Overview → Server address.