First decide: wrong entry, not running, or blocked

A server that “shows offline / won’t connect” almost always falls into one of these categories. Working through them from easiest to hardest is the fastest approach:

  1. Wrong address or port. This is the most common one. Java Edition’s default port is 25565, Bedrock’s default is 19132, and the two can’t be mixed up; an extra space in the address or a single wrong digit in the port will stop the connection cold.
  2. The server process isn’t actually online. The machine or container hasn’t started, just rebooted and isn’t ready yet, or the process crashed.
  3. Blocked by the network. The host firewall doesn’t allow the port, the router has no port forwarding, or the cloud host security group hasn’t allowed it.
  4. Version mismatch. The client and server aren’t on the same edition line (Java↔Java, Bedrock↔Bedrock), or the specific minor version doesn’t line up.

To quickly tell which category you’re in, use TopoBlocks’s free monitor-only mode: just enter the address plus port, and it pings the server the way an ordinary player would, telling you the online status, version, current player count, and latency. If monitoring can’t see it online, the problem is probably in the first three categories; if monitoring works fine but you still can’t get in, it’s most likely a version or entry issue on your side. To learn exactly what to enter when connecting, see Connecting to a Minecraft server.

Use monitor-only to pinpoint the issue (free, no write access)

Monitor-only is free and read-only: it needs only an address + port, never reads your world directory, has no write access at all, and needs no server password or login credentials. That makes it very safe for troubleshooting — it won’t touch your world, let alone overwrite any files.

  • Monitoring shows offline → go back to the previous section and double-check the port (Java 25565 / Bedrock 19132) and address, then confirm the process is online and that the firewall and port forwarding allow it.
  • Monitoring shows online, but you can’t get in → the problem is on the client side: check that the versions match and that the address and port are entered correctly under “Add Server” in-game.

To learn which metrics monitoring can see and how to set offline alerts, see How to monitor server online status / players / latency. If you’re still unsure whether to run Java or Bedrock and which default port to use, see Should you run Java or Bedrock for your server.

A few honest notes

  • Monitoring is free and read-only, never touching the world and with no write access. Full-management features like remote snapshots and safe deploy require your explicit authorization before they run; pricing for those paid features is as shown in the App, and failed jobs are refunded automatically.
  • TopoBlocks won’t change your server config for you. Monitoring helps you pinpoint the issue, but allowing the firewall port, setting up port forwarding, and aligning versions still have to be done on your server/router side; it won’t edit settings like server.properties, the whitelist, or OP.
  • If after troubleshooting you’d rather switch to a more hands-off approach, one-click managed hosting can automatically pick the version/plan/region and bring the server online, with deployment following “snapshot → validate → atomic switch → health check → automatic rollback on failure” and never overwriting your source files. For details, see the in-depth guide Safely deploying a server world.