— visitors online
What's new
Offline, ports and status checks

Fix Minecraft server monitoring and address-check problems

MineRate tests the public status response from its own network. A failed status request is not proof that every player is disconnected, and a successful one does not test the full login flow.

Checked against the MineRate dashboard ·

Check the exact public endpoint and protocol before changing unrelated settings.

Before you start

  • The public host, port and edition recorded in the listing.
  • Access to relevant hosting/proxy settings or help from your hosting provider.

Step-by-step instructions

  1. Compare the recorded endpoint with player instructions

    Check spelling, public DNS and the actual allocated port. Do not submit a website URL, local address or backend-only port. For crossplay, test the Java and Bedrock endpoints separately in the public status checker.

  2. Check the status listener, not RCON

    For a Java server, review whether public status is enabled; Paper’s enable-status setting controls status responses. A proxy or MOTD plugin can override what the public endpoint returns. MineRate does not need your RCON password or remote-console access.

  3. Check the correct network protocol

    Java status normally uses TCP and Bedrock uses UDP. Review only the necessary hosting/firewall rule and any anti-DDoS or source restrictions. For Geyser, confirm the Bedrock bind port and follow the project’s connection troubleshooting documentation.

  4. Read the error and compare routes

    Unknown host points toward name resolution; connection refused can indicate that nothing is listening on the chosen endpoint; a timeout can result from filtering or an unreachable route. Compare a fresh MineRate check with a test from another permitted network and inspect server/proxy logs.

  5. Review monitoring history after the fix

    The regular monitor runs separately from an on-demand check, so catalog status may not change immediately. Check the next stored result in Statistics. For a persistently hidden or excluded listing, review publication status as well as restored availability.

If something does not work

Players can join but MineRate shows offline
Check status settings, proxy responses and filtering that affects the monitoring route. Do not turn off account authentication, whitelist or the whole firewall to fix a status-only problem.
Java is online but Bedrock is not
Check the Bedrock listener, allocated UDP port and crossplay configuration. A working TCP game port is not a Bedrock status response.
The player count or ping seems different
Counts are sampled and may represent a proxy’s whole network. Ping is measured from MineRate’s monitoring host, not from each visitor’s device, and is not the server’s TPS.

Common questions

Do I need to enable Query or expose RCON?

MineRate’s normal checks use the public Java or Bedrock status protocol. RCON credentials are not needed, and enabling unrelated management ports is not a substitute for a working status response.

Does an on-demand check rewrite my listing immediately?

The public status checker reports that request’s result. Regular catalog monitoring and its cached pages update separately; inspect the next saved check rather than assuming the checker edited your listing.

Official references

MineRate-specific behavior is described above; these references cover the underlying server settings and integrations.