Direct answer

Try Direct Connect to the same host and port. If joining works but the multiplayer list shows the server as offline, troubleshoot status ping separately from the game connection.

What it means

The server may still accept direct connections even when status ping is disabled or blocked.

If you are a player

  • Test the full hostname with Direct Connect; note whether the list shows “Can’t connect” but joining still works.
  • Try the server IP and port separately if the owner provides them; distinguish Bedrock and Java ports.
  • Compare results from another network and record the full address used.

If you run the server

  1. Check the server process and listener first, then verify enable-status and the configured server port for Java Edition.
  2. Validate DNS A/AAAA and SRV records for the actual hostname and port; stale IPv6 addresses may cause failures for only some clients.
  3. If a proxy is in front, verify the proxy’s status ping path independently from its backend login path.
  4. Confirm firewalls and hosting allocation expose the intended port; do not set a Bukkit backend publicly accessible just to make the list icon green.

Verify the result: External clients must get a reliable status/MOTD and complete a login; if the listing remains offline while login works, document the status-only fault.

References

References used to verify the settings and troubleshooting steps in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000