Vintage Story Unable to Connect to Server: Fixes to Try
Fix Vintage Story unable to connect to server errors with checks for server readiness, address, TCP and UDP, access settings, versions, and auth.
You will need
- The server address and port from its owner
- The exact error text and your client version
If you see Vintage Story unable to connect to server at the join screen, work through the server, address, access, and network checks before changing files. The exact message is a clue, not a diagnosis: a server that is still loading, a mistyped address, a whitelist, a blocked port, or an account-service issue can all stop a join. This checklist separates what you can check from what the owner must check, then points you to Anego’s status page if the problem may affect everyone. Vintage Story currently lists PC clients for Windows, macOS, and Linux, with no console client listed; each player needs their own game account.
Fix Vintage Story Unable to Connect to Server Step by Step#
Ask the owner whether the server is running and has finished loading the world. A process can be open while the world is still starting, and a server that stopped cannot accept a connection. If other players are already inside, ask whether they can still move and interact; that confirms the world is reachable for them, though it does not rule out your own access or network problem.
If you own a dedicated server, check its console or latest log for a ready message and the port it reports. The official Dedicated Server guide documents the startup flow and the default port. Compare the reported value with the address you gave your friend. If the process exited, read the last error before restarting repeatedly; the cause may be a failed startup rather than networking.
When only one person cannot join, keep the server running while you compare that person’s address, account, version, and network. If nobody can join, the owner should first confirm readiness and then inspect the shared address and network path.
Re-enter the address and port the owner gave you#
In Vintage Story, open Multiplayer and add the server with the address supplied by its owner. Check every character in the hostname or IP address. If the owner supplied a port, include it in the port field; the default dedicated-server port is 42420, but a server can use a different configured port. Do not substitute the owner’s local LAN address when joining from another network.
Open the server entry
In the game, choose Multiplayer, then add or edit the server entry.
Copy the supplied address
Paste the hostname or IP from the owner. Enter the supplied port separately if the form provides a port field.
Save and try once
Save the entry and try to join. If it fails, copy the exact message before changing another setting.
If the server appears in the public list, that listing is not required to join it directly. Ask the owner for the direct address if the list is empty or out of date. For a port-specific walkthrough, see which port a Vintage Story server uses.
Check whitelist, password, and bans with the owner#
Ask the owner to verify your exact Vintage Story player name against the server’s access settings. Dedicated servers use a whitelist by default in current server setups, and the owner may also have configured a password or ban. A similar-looking name is not enough if the entry does not match your account.
The owner can check the server configuration and player controls without turning off account verification. If they changed the whitelist or password, have them confirm the saved value and ask you to retry. The server commands guide explains the owner-side command context; the owner should use the panel or console that manages this particular server.
The owner can also confirm whether the server is private by design. If access is intentional, they should add the right account or share the correct password through a private channel.
Compare compatible client and server versions#
Check the version shown by your client and ask the owner for the server version. Use compatible releases from the same network-version series; matching every patch digit is not a universal requirement. As checked on October 13, 2026, the latest stable release was 1.22.7, whose network version is 1.22.6; that example can change after a new release. The project’s version source defines network compatibility.
If one side is on a different major or minor series, update the older side using the official Vintage Story downloads, then try again. Don’t downgrade or replace a server install until the owner confirms which build the world and mods use. The server configuration guide can help the owner locate the server’s settings.
Check TCP, UDP, and firewall rules#
The default dedicated-server port is 42420. Since Vintage Story 1.20, the official guidance says a dedicated server needs both TCP and UDP allowed. Configure separate rules for the same port on the host firewall and, when self-hosting from home, the router. Some routers do not handle a combined “TCP/UDP” rule correctly.
The official multiplayer troubleshooting guide describes two useful clues:
| Message | First check | What it does not prove |
|---|---|---|
| “Host has failed to respond” | Whether the owner forwarded the port and whether the public IP changed | That UDP is definitely the cause |
| “Host has actively refused” | Whether the server is listening and the host firewall allows it | That the router is necessarily wrong |
| Immediate whitelist or password refusal | Whether the owner’s access settings match your account | That the network path is broken |
The owner should verify the configured port, the firewall rules, and the router’s forwarding target. If the server used to work and the owner hosts from home, ask whether their public IP changed. A player should allow the official game executable through their own firewall only when the operating system asks or the rule is missing; don’t switch off the firewall wholesale.
Separate a server problem from your PC or connection#
Try another Vintage Story server you are allowed to join, or ask a second player to try this one. If you can join other servers but one friend cannot join this server, the owner should focus on that server’s address, access list, configured port, and host firewall. If you cannot join any server but others can, check your own game version, local firewall prompt, internet connection, and account status.
For self-hosters, the official troubleshooting guide recommends allowing VintagestoryServer.exe on the host firewall and testing with another computer on the same local network. A successful local test shows the server can accept a nearby connection; internet access still depends on the router and the correct public address. Players should allow Vintagestory.exe if their firewall is blocking it.
If you recently added server-side mods, tell the owner when the failures began and whether every player is affected. A mod can be relevant, but a connection error alone does not establish that a mod caused it. Vintage Story can offer joining players a download for server-side or universal mods; client-side mods still need to be installed by each player. Ask the owner to compare the mod’s ModDB entry, author’s supported game versions, and required dependencies with the server’s installed release. Labels can be incomplete, so don’t assume that a mod works with every patch or remove client files at random. The owner’s server mod guide covers the managed install flow.
Check Anego’s services when multiple players fail#
Vintage Story requires each player to authenticate with their own account. If several players suddenly cannot authenticate or join, check the official service status page for auth servers, the master server, ModDB, and the CDN. The status page showed all listed systems operational at 02:54 UTC on October 14, 2026; that is only a dated snapshot, so use the page for the current state.
An auth-service issue is different from one server refusing one player. Don’t delete clientsettings.json as a first step: the official troubleshooting guide warns that removing it resets local settings and saved server entries. If the status page reports an incident, wait for Anego’s update and retry afterward. If it shows healthy services, return to the server-specific checks instead of changing account security settings.
Decide whether managed hosting would remove your server-side work#
If the failing part is a home server’s router, public address, or host-side configuration, a managed Vintage Story server can remove that home-network setup from your checklist. Game Hosting’s Vintage Story server page documents its open TCP and UDP game port, a panel for the owner’s whitelist/admin status, player controls, and human support for host-side questions. It cannot fix your PC’s firewall, a player account issue, incompatible versions, another server’s access rules, or an Anego service outage.
If you already rent this server, send its owner or host the exact message, your client version, the time it happened, and whether other players can join. That gives them a useful starting point without exposing your password or account credentials.
Keep the report small and useful#
Before asking for more help, collect four details: the exact error text, whether other players can join, your client version, and whether the owner recently changed the address, version, access settings, port, or mods. The owner can add the server’s ready log line and configured port. Never post an account password or private server credentials in a public forum.
If the issue happens after you enter the world and then disconnects, share the full reason shown in the client with the owner. The distinction matters: a failed join, a public-list problem, an auth-service outage, and a mid-session disconnect each need different evidence.
For the shortest route, check the address and readiness first, then access settings and compatible versions. Move to the TCP/UDP and firewall checks when the message or owner’s setup points to the network, and check Anego’s status when the problem affects multiple players.
Quick answers
Why can't I connect to my Vintage Story server?
First confirm the server finished starting, then check the address, access settings, compatible network version, and TCP and UDP reachability. The error text narrows the search but does not prove one cause.
Are Vintage Story servers down?
Check the official Vintage Story status page for current auth, master server, ModDB, and CDN incidents. A status snapshot can change, and a server-specific join failure may have another cause.
How do I connect to a Vintage Story server?
In Vintage Story, open Multiplayer, add the server, and enter the address and any port the owner supplied. Every player needs their own Vintage Story account.
Why does Vintage Story say the host has failed to respond?
The official troubleshooting guide says this often points to port forwarding; since version 1.20, check TCP and UDP separately on port 42420. It is a clue, not a guaranteed diagnosis.