7 Days to Die: Can't connect to a server
Fix a 7 Days to Die connection. Match the branch, wait for world generation, split IP and port on Connect to IP, open TCP 26900 and UDP 26900 through 26903, then check EAC, crossplay, password, and whitelist.
If 7 Days to Die cannot connect, work through these checks in order. Do not delete the world first. After a TFP patch, the usual cause is a client on a different branch than the dedicated server.
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 branch and version
The client and dedicated server must run the same 7 Days to Die release and the same Steam branch. The current 2026 example is V2.6 stable versus the separate V3 experimental line. The version mismatch guide tracks the current release process.
Update the player's game
Close 7 Days to Die, let Steam finish the update, and leave experimental opt-in off unless the server is also experimental.
Update the dedicated server
Stop the server. On berrybyte, Auto Update pulls the current dedicated build on the next start. Restart once after the patch is live.
Compare versions
The version on the main menu must match the version in the server log.
If you do not want to babysit TFP patches, rent a 7 Days to Die server that updates on start.
2. Wait until the world has generated
A new dedicated world can sit on generation for a long time. Joins during that window fail.
Confirm Overview shows running
On berrybyte the process must be running, not still installing.
Read Console
Wait until the log finishes generating or loading the world. A first boot can take several minutes.
Retry one client
Test with one survivor before inviting the group.
3. Use Connect to IP
The browser is optional. The reliable test is Join a Game → Connect to IP.
Copy Server address
On berrybyte, copy Server address from Overview.
Split host and port
Launch 7 Days to Die, open Join a Game, click Connect to IP, and put the part before the colon in the IP field and the part after it in the Port field.
4. Open the complete port set
The Fun Pimps documents TCP 26900 and UDP 26900 through 26903.
Port 26903 is reserved at present, though its
firewall guide
warns that leaving it closed can block joining. A hosted allocation can
shift this whole set.
Use the ports the server bound
On berrybyte, Overview is the game address. The rest of
the set is opened for you. On a self-hosted box, read
serverconfig.xml.
Forward the full set (self-host)
If Connect to IP times out while Console looks healthy, allow TCP on the base port and UDP from the base port through base port plus three.
berrybyte opens the allocated set for you. Self-hosters who are fighting NAT can rent a 7 Days to Die server that already has those ports reachable.
5. Share or clear the password
ServerPassword in serverconfig.xml 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.
6. Check EAC, crossplay, and the whitelist
Easy Anti-Cheat must agree on the client and server. Whitelist entries live
in serveradmin.xml; the presence of an entry activates allowlist behavior.
Match EAC on both sides
Start the regular EAC client when EACEnabled is active. A player who launched the
EAC-off client needs a server configured the same way.
Review serveradmin.xml
Add the player's platform ID under <whitelist>, or remove every whitelist entry when the
server should accept the public.
Check console crossplay
Console players join through the browser. Set ServerAllowCrossplay for a crossplay
server, keep EAC active, use a supported player cap, and remove server mods that make the
world incompatible with consoles.
The current
dedicated-server reference
documents serveradmin.xml, server visibility, password, EAC, and crossplay
settings.
If the connection still fails
Confirm Console finished loading the world. Then check the leftover causes:
- A full player cap.
- Check steamstat.us.
- Check berrybytestatus.com.
Frequently asked questions
Why can't I connect to a 7 Days to Die server?
Match the game branch first. Stable and experimental builds use different protocols. Then wait for world generation, use Connect to IP on PC, check TCP 26900 and UDP 26900 through 26903, and verify EAC, password, and whitelist access.
How do I join a 7 Days to Die server by IP?
Launch the game, choose Join a Game, click Connect to IP, and split Server address at the colon. IP goes in the IP field, port in the Port field. On berrybyte that address is Overview → Server address.
What ports does a 7 Days to Die dedicated server use?
The official default firewall set is TCP 26900 and UDP 26900 through 26903. Port 26903 is reserved, but The Fun Pimps warns that leaving it closed can block joining. berrybyte opens the matching allocated set.
Why does 7 Days to Die say the server is running a different version?
The client and dedicated server are on different releases or Steam branches. Update both sides to the same stable build, or opt both into the same experimental branch. In 2026, V2.6 stable and V3 experimental are separate protocol lines.
Why is my 7 Days to Die server missing from the browser?
New worlds can take several minutes to list during generation. PC players can test Connect to IP. Console players need the browser, with crossplay enabled, EAC active, a compatible player cap, and server-side mods removed.