Zandronum Server Not Showing in Doomseeker or Can't Connect

A Zandronum server that does not show in Doomseeker is usually not registered with the master server (sv_updatemaster is off), not reachable on its UDP port (10666 by default), or hidden by a Doomseeker filter on the player's side. When it shows but players cannot join, the cause is nearly always a mismatch: a different Zandronum version, a missing commercial IWAD, or a PWAD whose version differs from the server's copy. Check those in that order and you will find it.

Doomseeker is only a browser. It asks the Zandronum master server for a list of addresses, then queries each server directly. Your server has to pass both steps to appear.

Quick diagnosis

The fastest test is the console. Open Zandronum, press the tilde key and type connect your.ip:10666. If that works, the server is fine and you are dealing with the list.

Register with the master server

The server must announce itself. In your config (or zandronum.ini), check:

sv_updatemaster 1
sv_hostname "Your Server Name"

With sv_updatemaster 0, the server is private: it runs and accepts anyone who has the address, but it never reaches the master list, so Doomseeker cannot see it. Changes apply on restart. On a running server you can also type sv_updatemaster 1 in the console.

The server reaches out to the master on its own, so you do not forward anything for that step. Once registered, a new server usually shows within a refresh or two.

Give the server a clean name. The master operators can ban servers that break their rules, and a banned server stays off the list no matter what you change locally.

Open the port

Players and Doomseeker both talk to the server on UDP, port 10666 unless you set -port to something else.

1. Confirm the port. The server console prints it at startup. A second server on the same machine often moves to 10667 without you noticing.
2. Firewall. Allow UDP inbound. Windows: netsh advfirewall firewall add rule name="Zandronum" dir=in action=allow protocol=UDP localport=10666. Linux with ufw: sudo ufw allow 10666/udp. More detail in Windows firewall rules for a game server.
3. Router. Forward UDP 10666 to the server's local IP and reserve that IP. The port forwarding guide covers the general steps.
4. CGNAT. If your router's WAN IP differs from your public IP, forwarding cannot work. How to tell if you are behind CGNAT explains the check.
5. Testing from home. Many routers do not loop the public IP back. Join your own server with its local IP, and have a friend outside test the public one.

Doomseeker filters

If the server is registered and reachable but one player still cannot see it, look at their Doomseeker:

• Filters. The filter panel can hide empty servers, full servers, servers without certain WADs or servers above a ping. Clear filters and refresh.
• Engine enabled. Under Doomseeker's configuration, the Zandronum plugin must be enabled and pointed at the player's Zandronum executable.
• Search box. A leftover search term hides everything that does not match.
• Refresh. The list is a snapshot. A server started a minute ago needs a fresh refresh.

Version mismatch

Zandronum clients only join servers on the same version. After a release like 3.2.1, servers and players update at different times and some joins start failing.

• Check the server version in its startup output.
• Have players check theirs in Zandronum or in Doomseeker's server details.
• Update whichever side is behind. Doomseeker can manage several Zandronum versions side by side if a player needs older and newer servers.

Testing builds are separate from releases. A server on a testing build only accepts clients on that same build.

WAD problems

Zandronum checks that each player has the same files as the server.

Missing IWAD. Commercial IWADs like doom.wad, doom2.wad, tnt.wad and plutonia.wad are never downloaded automatically. Players must own and copy them into their Zandronum folder. If your server is for the public, consider Freedoom as the IWAD so nobody is locked out.

PWAD not found. Wadseeker searches known WAD archives for the files the server lists. Obscure, private or renamed files fail. Fix it by:

• setting sv_website to a page with direct download links to your WADs, which Wadseeker also checks
• or sharing the files in your Discord and telling players to drop them into their Zandronum folder

Same name, different file. If a mod updated but kept its file name, players with the old copy fail the check even though Doomseeker thinks they have it. Rename updated files with a version number, like mymod-v2.pk3, and point the server at the new name. Tell players to delete the old copy if they still hit the check.

Case on Linux. A server on Linux treats Eviternity.wad and eviternity.wad as different files. The name in your start command or panel must match the file exactly.

Passwords and full servers

• sv_forcepassword 1 with sv_password asks every player for a password to connect.
• sv_forcejoinpassword 1 with sv_joinpassword lets people spectate freely but asks for a password to play.
• sv_maxclients caps total connections, sv_maxplayers caps active players. When players hit the second limit, they join as spectators, which can look like a failed join.
• A banned IP is refused. Check banlist.txt next to the config, or use the console.

The full settings list is in Zandronum server settings explained, and the setup from scratch is in how to host a Zandronum server.

Take the network out of it

Almost every cause above that is not a WAD mismatch is a home network issue. A GamezServers Zandronum server has its own address with the port open, so once sv_updatemaster is on it shows in Doomseeker and players can also connect to it directly. You set the IWAD and PWADs in the panel fields, upload files with the file manager or SFTP, and watch the console live when a WAD fails to load. DDoS protection is always on, which helps once the server is public.

FAQ

How long does a new Zandronum server take to appear in Doomseeker?

Usually a refresh or two after it starts, as long as sv_updatemaster is 1 and the port is reachable.

Can I hide my server from Doomseeker but still play on it?

Yes. Set sv_updatemaster 0 and have players use connect ip:port in the console, or add it in Doomseeker manually.

Why does Doomseeker show my server with no ping?

Its query packets are not getting answers. Check the server is running, the UDP port is open in the firewall and router, and the player is using the right port.

Do I need to forward a port for the master server?

No. The server contacts the master on its own. You only forward the game port so players and Doomseeker can reach the server.

Why can friends join but I cannot from home?

Your router probably lacks loopback. Connect using the server's local IP and port instead.