How to find the server IP in 7 Days to Die: rented server panels, ipconfig for self-hosted, default ports 26900-26903, join fixes and the SDK config error.
How to See Server IP in 7 Days to Die (2026)
Where the server IP lives depends on who hosts it: rented servers show it in the control panel, self-hosted servers need ipconfig for the local address, and the default port is 26900. You can also skip the IP entirely — most players find servers through the in-game browser, which works by server name, not address. This guide covers every way to find a 7 Days to Die server IP, how joining by IP works, the port-forwarding numbers that make self-hosting visible, the "can't find server" trap, and the specific fixes for the "Server SDK Config Update Failed" error that bricks dedicated server boots.
Official resources: Steam store page · Official wiki: Server · Official forum: SDK config error thread · Valve Developer Community: dedicated server
Where to Find the Server IP
There are three hosting scenarios, and each surfaces the IP differently:
| Scenario | Where the IP is | Example |
|---|---|---|
| Rented server (any host) | Control panel / dashboard, usually top-left "Address" field | 203.0.113.42:26900 |
| Self-hosted on your LAN | ipconfig → IPv4 of your machine |
192.168.1.50 |
| Self-hosted for friends over the internet | Your public IP (search "my ip") + port forwarding | 84.123.77.9:26900 |
The IP and port almost always travel as a pair — hosts display IP:PORT and the in-game "Connect to IP" box expects exactly that format. Default port is 26900; only change it if the server owner changed it in serverconfig.xml.
Your LAN IP (192.168.x.x) works only for players on your own Wi-Fi/router. Friends on the internet need your public IP — the one your router sees externally — plus port forwarding (below). The single most common "why can't my friend join" answer is that they were handed a LAN IP.
Joining a Server: Browser vs Direct Connect
You don't actually need the IP at all for public servers. Main menu → Join a Game → server browser → search by name, filter by region, connect. The browser only lists servers with ServerVisibility set to Public (2) in their config — private servers (0 = not listed, 1 = friends only) will never appear no matter how many times you refresh.
For private servers, friends-only games, or servers with visibility off, use Direct Connect: Join A Game → "Connect to IP" → paste IP:PORT → Connect. Direct connect bypasses the browser entirely, which is also the workaround when a public server you know exists isn't showing up in your filtered list.
Self-Hosting: Finding Your IP and Forwarding Ports
To host from your own PC:
- Find your LAN IP: Windows → open Command Prompt (
cmd) → typeipconfig→ copy the IPv4 address of your active adapter. - Find your public IP: search "what is my ip" in any browser. This is what remote friends need.
- Forward the ports in your router admin page to your LAN IP: TCP 26900, UDP 26901–26903 (the standard 7 Days to Die range; your
serverconfig.xmlmay use others). - Send friends
publicIP:26900.
If you're hosting and playing on the same machine, you can join yourself with 127.0.0.1:26900 (localhost) — useful for testing before you invite anyone. The official wiki's Server page documents the serverconfig.xml fields and the connection modes in detail.
Players searching for a friend's game and failing ("can't find server id", "session not found") are almost always hitting one of four things: the host's world isn't finished loading (the session only appears once the world is live), the region filter is set wrong on both sides, the game versions differ (console patch lag — see the crossplay guide), or the server is set to Friends/LAN visibility when it needs to be public. Direct connect with the literal IP fixes all four at once.
"Server SDK Config Update Failed": What It Is and How to Fix It
This error appears on dedicated server startup, usually as SDK Config Platform Update Request Failed, Result Code: EOS_NoConnection, and it means the server can't complete its Epic Online Services (EOS) platform handshake. The official forum thread on the error — answered by Fun Pimps staff — points at the causes and fixes:
- Missing root certificates (Windows). The EOS SDK verifies against the Epic API (
api.epicgames.dev) and fails without updated Windows certificates. Run Windows Update, then reboot the server. - Antivirus interference. Windows Defender or third-party AV blocking the server's outbound calls. Add the server install folder and the save folder to AV exclusions — the staff note that "you can't fully disable Windows Defender" without exclusions, which is the practical fix.
- Don't remove EOS from
platform.cfg. Changingcrossplay=EOSto empty "breaks things" — the game requires the EOS platform; the fix is the network/certificates, not the config. - Server can't reach Epic's servers. Firewall rules, NAT filtering, or a blocked outbound connection to
api.epicgames.devall produce the same result. Verify you can reach the API URL from the server box itself.
Also worth checking: mod folder names with spaces or non-English characters can make the server silently skip mods and fail config sync (rename them to plain ASCII and restart), and always start the server with the correct branch selected (e.g. the 3.1.0 stable branch, per the official V3.1 release notes). If the server still sits at "Server is still initializing," the log (output_log_dedi__*.txt) will name the exact failing step.
Finding Players: Servers, Communities, and Discord
Once the server's up, the second half of the question is finding people — or being found. The in-game browser plus server-list sites (7daystodie-servers.com aggregates public servers) cover the "pick a server" case. For organized groups, trading, modding support and LFG, the hubs are:
- The official 7 Days to Die Discord — linked from the Steam store page (invite
discord.gg/taYNEUS); official announcements, bug reports, and a large player base. - The official forum (community.thefunpimps.com) — the place the devs actually answer, including the SDK error thread above.
- Subreddit r/7daystodie — the busiest community for server ads, LFG, and mod support.
Per the official V3.1 announcement: dedicated server players "will need to select the correct branch, Default Public Version which is the v3.1.0 stable" — a reminder that version mismatch is the quietest killer of "I can't see the server" reports, since a server on the wrong branch is invisible to everyone else.
FAQ
How do I see the server IP in 7 Days to Die?
Rented servers: check your hosting panel/dashboard (usually an "Address" field showing IP:port). Self-hosted: run ipconfig on the host machine for the LAN IP, or search "my ip" for the public address friends need. The default port is 26900.
What port does a 7 Days to Die server use?
Default is TCP 26900, with UDP 26901–26903 for the game traffic. Forward those four to your LAN IP when self-hosting, and hand out publicIP:26900 to friends.
Why can't I find the server ID / IP when searching?
The host's world probably isn't loaded yet (sessions appear only once the world is live), the region filter is mismatched, the server visibility is set to Friends/LAN instead of Public, or the game versions differ. Direct connect with the literal IP:port bypasses the browser entirely.
How do I fix "server sdk config update failed"?
It's an Epic Online Services handshake failure at server startup. Fixes: run Windows Update (missing certificates), add the server install and save folders to antivirus exclusions, confirm the server can reach api.epicgames.dev, and do not remove EOS from platform.cfg — that breaks the server. See the official forum thread for the staff-approved sequence.
Where can I find 7 Days to Die players and servers?
The in-game server browser (Public servers), server-list sites, the official Discord (discord.gg/taYNEUS, linked from the Steam page), the official forum, and r/7daystodie for LFG and server ads.
Related guides: Is 7 Days to Die Crossplay? PC, PS5 & Xbox · 7 Days to Die Singleplayer: How to Survive · 7 Days to Die Creative Mode — commands and cheats · Rust Crossplay — the full truth · Valheim Crossplay — how it works
Last updated: August 13, 2026.
Related Guides
More 7 Days to Die Guides
7 Days to Die base designs: kill corridors, elevated kill boxes, pit and bridge bases, zombie AI pathing, materials, traps, and how to wire lights.
7 Days to Die beeswax: harvest tree stumps (20% drop, 40% near POIs), kill Rancher zombies in the desert, and craft the Apiary for renewable honey.
7 Days to Die Blood Moon guide: horde night schedule, game stage and waves, prep checklist, survival strategies, plus the 7 Days Blood Moons 4v1 game at $9.99.
7 Days to Die chest organization: container types, the wooden-crate upgrade trick, renaming and color coding, plus QoL mods that sort for you.
7 Days to Die creative mode: how to enable it, cm/dm/god/fly commands, the U item menu, giveself spawn commands, and server setup (BuildCreate).
7 Days to Die crossplay guide: PC, PS5 and Xbox Series X|S play together since V1.2. Requirements, how to enable, limits, cross-save truth, troubleshooting.
7 Days to Die Darkness Falls guide: KhaineGB's V6 overhaul, the 8 classes, 96-slot backpack, titanium and laser tech, and how to install it.
7 Days to Die maps explained: Navezgane cities and POIs, random-gen world sizes (4K-10K), Pregen maps, teleport commands and console map differences.