Veloren Can't Connect to Server: Version Mismatch and Login Errors

The most common reason you can't connect to a Veloren server is a build mismatch, shown as "Mismatched server and client version. Hint: You might need to update your game client or contact server owner for update." Client and server must run the same build channel (weekly or nightly) from the same day, so update both or switch the client to the server's channel in Airshipper. If the versions match, read the exact error on the login screen: each one in the table below points to a different cause, from the account server to the whitelist to a closed port.

Match the error to the fix

Version mismatch: the fix in detail

Veloren moves fast. Besides tagged releases there are two rolling channels:

• Weekly: a fresh build every week, what most players run.
• Nightly: a fresh build every day.

A weekly client and a nightly server are not compatible, and neither are two weeklies from different weeks once the network protocol changed between them. The login screen shows the client and server versions side by side when this happens, which makes it easy to see which side is behind.

If you are a player:

1. Open Airshipper.
2. Check which channel is selected. Switch to the server's channel if it differs.
3. Let it update, then launch.

If you run the server:

1. Check the server's channel and build date in its startup log.
2. Install the newest build of that channel and restart.
3. Tell players which channel to use. Post it in your server description or Discord.

The weekly build changes over once a week. Updating the server on the same day saves a round of "I can't get in" messages. If your group plays at odd hours, pick weekly over nightly, since nightly can change under you every day.

Account and authentication problems

Normal servers check every login against the official authentication server (auth.veloren.net, set as auth_server_address in settings.ron). That means:

• Every player needs a free account from veloren.net/account. There is no server password: the account is the login.
• The username and password typed on the title screen are the account details, not a character name.
• Usernames may only contain letters, numbers, _ and -.

"Authentication error on server" usually means a typo in the password, or the account was created moments ago. "Failed to connect to authentication server" means the player's PC cannot reach the auth service: a VPN, a strict firewall, DNS trouble or, rarely, an outage on Veloren's side. Try another network to tell which.

Do not run the server with --no-auth to work around this. It turns account checks off entirely, so anyone can join under any name, and admin roles tied to names become meaningless.

Server not found or timeout

When the server is running but nobody can reach it:

1. Address. Type the IP or hostname with the port if it is not the default, for example 203.0.113.10:14004.
2. Port. The game uses TCP 14004. On a home connection, forward it to the server machine and allow it in the firewall. Our port forwarding guide has router steps.
3. Carrier grade NAT. Some providers put you behind shared addresses where forwarding is impossible. See hosting without port forwarding.
4. Server load. A timeout can also mean the server is busy generating a world, especially right after a new seed or a bigger map. Watch the console and wait for it to finish.
5. Test locally. If you can join on the same network but friends cannot, the problem is the port forward, not Veloren.

Whitelist and bans

"You are not a member in the whitelist of the server you have attempted to join" means whitelist.ron has entries and the account is not among them. A moderator or admin adds players in game with /whitelist add <username>, or the owner edits the file and restarts.

Ban messages include the reason and, for temporary bans, when it ends. Admins lift them with /unban <username>. Our Veloren admin commands guide covers whitelist, ban and role commands.

After editing settings.ron, nobody can join

If the server no longer behaves as configured after you edited settings.ron, check the startup log. When the file has a syntax error, the server falls back to default settings and writes settings.template.ron next to your file. Defaults include a different server name and port settings, which can leave players knocking at the wrong door. Fix the missing comma or bracket, compare against the template and restart.

The official server works but mine does not

That narrows it down nicely: the player's client and account are fine. The difference is your server's build, address, port or whitelist. Work down the table from the top. Our Veloren server setup guide shows a working configuration to compare against.

Hosted servers remove half the list

A Veloren server from GamezServers has its own address, so the port and NAT steps do not apply. The build channel is a panel setting: pick weekly or nightly and restart to pull the newest build of that channel, which is the whole version fix on the server side. settings.ron and the whitelist are in the file manager, and the live console shows each login attempt, so you can see why someone was turned away.

FAQ

Why does Veloren say mismatched server and client version?

Your client and the server run different builds. Use the same channel (weekly or nightly) and update both.

Do I need a password to join a Veloren server?

No server password exists. You log in with your free Veloren account, and the server may use a whitelist.

What port does a Veloren server use?

TCP 14004 for the game.

Can I play on a server while auth.veloren.net is down?

Normally not, since logins are checked there. Wait for it to come back rather than disabling authentication.

Why can my friend join but I can't?

Compare your client channel and update date with theirs, then check whether you are on the whitelist or banned.