Try joining directly first. A missing browser listing does not always mean the server is offline.
Check the server and browser
- Wait for Console to show that startup has finished.
- Try connect ADDRESS:PORT in Rust’s F1 console using the panel’s game address.
- Search the exact server name, clear browser filters and check the relevant categories for your framework.
- Refresh and allow time for the listing to update.
Check the query port
Rust uses separate game and query ports, both over UDP. They cannot use the same port number. On the Autowipe egg, QUERY PORT in Startup sets the query port. Check it against the assigned allocations in Network.
If the query allocation or setting is missing, ask support to check it and the firewall. Use an assigned port rather than choosing a random one.
What to send support
Include the server name, game address, query port, whether direct joining worked and any startup errors. Leave out RCON passwords and private tokens.
Use the direct connection guide to test the game port. Check server.cfg if the browser is showing a different name.
Troubleshooting checks
| What you see | What to check |
|---|---|
| Only browser search fails | Try the direct connection first. Clear incompatible filters and confirm the displayed server name. |
| Both direct joining and browser search fail | Start with readiness and the assigned game address before changing listing settings. |
Official reference: Facepunch’s server.queryport documentation, QUERY PORT setting.
Your feedback helps us improve our guides.


