Diagnose Rust game, query and RCON connection ports

A Rust server can accept players while missing from the browser, or appear online while its remote console fails. Diagnose each connection separately. A single successful port test does not prove that all three functions work.

Map the assigned ports

Record the public service address and each allocation. Rust uses UDP for server.port, UDP for server.queryport and TCP for rcon.port. Query and game ports must be distinct. Do not choose an adjacent port just because an online example uses it; the hosting platform must allocate and route that endpoint to your container.

Keep a private copy of the current startup settings and configuration. If changing network variables requires a restart, arrange a short maintenance window. World files, player databases and Oxide data do not need to be deleted to investigate reachability.

Test the game connection first

Wait for startup to complete and check for repeated crashes or bind errors.
From a Rust client outside the hosted container, try connecting directly to the assigned game address and port.
Record whether it times out, rejects the connection or reaches the loading screen. Note the exact time and the matching server-console output.
If another player can connect, compare locations and endpoints before changing the server. A local routing or client problem remains possible.

A generic TCP port checker cannot validate a UDP game listener. Likewise, a UDP probe with no reply is not conclusive unless it sends the expected protocol. Use actual Rust connection behaviour as the primary client test.

Then check discovery

If direct joining works but discovery fails, compare the configured query endpoint with the assigned query allocation. Allow time for listing updates and check the selected browser filters. Avoid changing the world name, identity or seed while testing browser visibility. Ask support to verify query traffic routing when the allocated values match but queries still fail.

Check RCON independently

Use a compatible trusted RCON client against the assigned TCP port. Confirm WebRCON mode and the password privately. A working game connection does not establish that the RCON listener is configured or permitted. Do not share credentials when reporting a timeout; support can investigate the network path without receiving the password in a public message.

Escalate with a small evidence set

Send the service ID, public endpoints, configured port values, UTC timestamp, client location and exact result for each test. Redact authentication strings and unrelated player details. Request checks for the specific protocol and allocation, not a blanket firewall exception. If a recent port change caused the issue, restore the recorded values and restart normally before attempting further changes.

Rust+ connectivity is another service with its own requirements. Keep it separate from game, discovery and RCON diagnosis so changing one feature does not obscure the original fault.