Hell Let Loose: Vietnam Server Browser Issues
Separate a stale browser result from a queue, reserved slot, server restart or connection failure before changing your network setup.
Quick server checklist
- Wait for the browser to finish its automatic refresh.
- Clear restrictive filters and compare more than one low-ping server.
- Check whether the symptom is a full queue, join error, timeout or disconnect.
- Try one other server before changing router, DNS or firewall settings.
- Record the server name, region, time and exact error if the problem repeats.
What the developers changed
Hotfix 1 changed the default browser to refresh more often, hide full servers unless filters are adjusted, and prioritise low-ping servers with 80 or fewer players. Additional official servers and server-stability fixes were also rolled out.
Current boundary
A displayed open slot is not a guaranteed seat. The server population can change before your join request completes, and community servers may apply queue or reserved-slot rules that are separate from the browser refresh.
Identify the actual failure
| Symptom | First check | Useful evidence |
|---|---|---|
| No servers | Clear filters, confirm the game is updated, then let the list refresh. | Platform, region, filter screenshot, build. |
| Open slots but cannot join | Refresh once and compare another server; the list may be stale or slots may be reserved. | Server name, displayed count, exact error. |
| Queue does not move | Decide whether to wait or select a lower-population server. | Queue position, elapsed time, server rules. |
| Timeout or disconnect | Try one other low-ping server before changing local network settings. | Time, ping, server, repeat frequency. |
| Everyone is removed | Check the official update thread for a server restart, patch or known outage. | Platform, server and timestamp. |
Safe troubleshooting order
1. Confirm the current build
Client and server builds must match. Finish the game update before treating a failed join as a network fault.
2. Reset only the browser view
Remove filters that can hide every result. Let the automatic refresh complete, then choose a low-ping server that is not near capacity.
3. Compare another server
If one server rejects the connection but another works, keep the investigation focused on that server, its queue or its rules.
4. Check official status
If multiple unrelated servers fail at the same time, review the developer launch thread and Team17 support before changing DNS, opening ports or disabling security software.
5. Report a repeatable case
Include the exact message, server name, region, platform, build and time. A screenshot of the listed player count and error is more useful than “servers are broken”.
Avoid these first moves
- Do not disable the firewall or security software as a generic first step.
- Do not assume every displayed slot is publicly joinable.
- Do not change DNS, router and game settings together; you will not know what mattered.
- Do not publish a community workaround as an official fix.