Project Zomboid Stuck on Getting Server Info Fixes

If Project Zomboid hangs on the “Getting Server Info� screen when you try to join a multiplayer server, the fix is usually to disable your VPN or proxy, switch to a wired connection, or manually add the server’s IP and port to your favorites. This article explains why the error happens and walks through the fixes that actually work, from quick checks to deeper network troubleshooting.

What Causes the “Getting Server Info� Hang

Project Zomboid’s multiplayer uses a peer-to-peer (P2P) connection model, even on dedicated servers. When you click a server in the browser, your client sends a small UDP packet to the server’s IP and port. The server replies with its current game state—map, mods, player count, and settings. If that reply never arrives, or arrives corrupted, the client sits on “Getting Server Info� indefinitely.

Common culprits include:

• Your firewall or router blocking UDP ports 16261–16262 (the default server ports).
• A VPN or proxy that changes your network path and interferes with the handshake.
• IPv6 issues—some servers only listen on IPv4, and your client may try IPv6 first.
• Mod mismatch—if the server has mods you don’t have, the info request can stall.
• Server-side lag or a full server that doesn’t respond fast enough.

Understanding that this is a network handshake problem, not a game crash, helps you target the right fix.

Quick Fixes to Try First

Start with these simple steps—they resolve the majority of cases:

1. Restart the game and Steam. A fresh client can clear a stuck connection.
2. Disable your VPN or proxy. If you’re using one, turn it off completely and try again.
3. Use a wired connection. Wi‑Fi can drop packets; an Ethernet cable gives a stable path.
4. Switch to IPv4. In Steam, go to Settings → Network, and set “Internet Client� to IPv4. This forces the game to use IPv4 only.
5. Add the server to your favorites manually. In the server browser, click “Favoritesâ€� → “Add Serverâ€�, type the IP and port (e.g., 192.168.1.10:16261), then try joining from there.

If none of these work, move on to the more involved fixes below.

Firewall and Router Port Forwarding

Your firewall might be silently dropping the UDP reply. On Windows, allow Project Zomboid through the firewall:

1. Open Control Panel → Windows Defender Firewall → Allow an app through the firewall.
2. Click Change settings, then Allow another app.
3. Browse to your Project Zomboid executable (usually in Steam\steamapps\common\ProjectZomboid) and add it.
4. Ensure both Private and Public boxes are checked.

If you’re hosting a server, you also need to forward UDP ports 16261–16262 on your router to the server’s local IP. The exact steps vary by router, but generally you log into your router’s admin page (often 192.168.1.1), find “Port Forwardingâ€�, and create a rule for UDP 16261–16262 pointing to the server’s IP. Without this, outside players can’t reach your server, and you may see the same hang when trying to join your own server from a different machine.

Mod Mismatch and Server Browser Issues

If the server uses mods, your client must have the exact same mods (and versions) installed. A mismatch can cause the info request to fail silently. To fix:

• Subscribe to the same Steam Workshop mods as the server. Most servers list their mods in the server browser description or on a website.
• If the server has a mod list, copy it and use the “Add Serverâ€� feature in the browser—some clients let you paste a mod list directly.
• Try clearing your Steam download cache: Steam → Settings → Downloads → Clear Download Cache. This doesn’t remove mods, but it can fix corrupted downloads.

Also, the server browser itself can be flaky. If a server is full or has a long queue, the info request may time out. Try refreshing the list, waiting a minute, or joining a different server to see if the issue is isolated.

Advanced Network Troubleshooting

If the basic fixes fail, you’re dealing with a deeper network issue. Here are the next steps:

1. Check if the server is actually online. Use a tool like Ping or an online port checker to see if the server’s IP and port respond. If not, the server is down or your network can’t reach it.
2. Temporarily disable your firewall (or add a rule for UDP 16261–16262) to see if it’s the culprit. Re-enable it after testing.
3. Try a different DNS. Sometimes DNS issues cause the game to resolve server addresses incorrectly. Switch to a public DNS like Google’s (8.8.8.8) temporarily.
4. Reset your network stack. Open Command Prompt as Administrator and run netsh winsock reset, then restart your PC.
5. Check for IPv6 issues. If your router has IPv6 enabled but the server doesn’t support it, the handshake may fail. You can disable IPv6 on your network adapter temporarily to test.

If you’re on a college campus or corporate network, UDP traffic may be blocked entirely. In that case, the only workaround is to use a different network (e.g., a mobile hotspot) or ask the network admin to allow the ports.

Server-Side Fixes (If You Host)

If you’re the server host and players get stuck on “Getting Server Info�, the problem is often on your end. Check these:

• Port forwarding is correct. UDP 16261 is the default game port; 16262 is for Steam queries. Forward both.
• Your server’s IP is static. If it changes, players can’t connect. Set a static IP or use a dynamic DNS service.
• Server is not overloaded. Too many players or heavy mods can slow the info response. Restart the server if it’s been up for days.
• Server version matches client. If your server is on a different build than the client, the handshake fails. Update both to the latest stable version.

Also, check the server console for errors when a player tries to connect. It may show a rejected connection reason.

Frequently Asked Questions

Why does it only happen on one server?
If only a specific server hangs, it’s likely that server is down, full, or has mods you don’t have. Check the server’s website or Discord for status updates.

Will reinstalling the game fix it?
Rarely. The issue is almost always network-related, not a corrupted game file. Reinstalling is a last resort after trying all network fixes.

Does using a VPN ever help?
Sometimes a VPN can bypass a broken route, but it more often causes the problem. If you must use a VPN, try a different server location.

Can I join a server via IP directly?
Yes. In the server browser, click “Favorites� → “Add Server�, enter the IP and port, and try joining. This bypasses the server list query, which can sometimes fail.

What ports do I need open for Project Zomboid?
UDP 16261 (game) and 16262 (Steam query). If you’re using a dedicated server, you may also need TCP 27015 for Steam’s server list.

Is there a way to skip the “Getting Server Info� screen?
No, it’s a required handshake. But you can reduce the wait by making sure your network is stable and the server is responsive.

Related

• Blender 3D Basics: Getting Started Guide
• VLOOKUP vs Nested IFs: Why VLOOKUP Wins
• Is Disney Worth Paying For? Plan Guide