WARDOGS Server Not Showing Up
At launch, a missing WARDOGS community server may be a browser filter, a region mismatch, a queue/authentication delay or a host process that never reached ready. Diagnose the layer before changing unknown ports.
Launch-day checklist
- Confirm the server status in the host panel or operator console.
- Reset the browser filters to a known state. During the beta BULKHEAD told players to search one region at a time, because selecting several was deliberately disabled while they scaled. Treat that as a historical workaround worth one try, not a guaranteed launch fix.
- Search the exact server name, including punctuation.
- Confirm Steam has the Early Access build installed and fully updated. The playtest is over, so a stale build is now a real cause.
- Check the official launch notes for changed discovery or port requirements.
Do not guess the final port map
| Observation | What it proves |
|---|---|
| Panel says ready, browser empty | Investigate discovery, filters and region. |
| Process restarting | Investigate build, entitlement or server package. |
| Other players see it | Local client filters or account state are likely. |
If the list went empty after a failed join, suspect the service rather than your setup. An empty browser during a launch surge usually is not your filters or your firewall, and reinstalling will not fix a problem thousands of people have at the same moment. Check whether others are seeing it before changing anything local.
There is still no public operator package, so any port list or direct-connect syntax you find elsewhere was guessed. Do not put invented values in a firewall.
If the browser is empty for everyone rather than only for you, read how to tell an outage from the login queue first. Track confirmed operator facts in the dedicated-server status guide.