The three useful layers
- Minecraft process: the Java server process and world.
- Local listener: the port/interface where that process accepts connections.
- Public route: the SPUDZWARE hostname or gateway players use from outside the device/network.
Troubleshooting becomes much easier when these are checked in order. A public route cannot make a Minecraft process ready if the game server is still loading a world, and restarting Minecraft does not necessarily fix an authentication problem in the relay.
Use the hostname shown by SPUDZWARE
The control panel or launcher should present one copyable player-facing address for the relevant client. Server owners should share that address rather than internal IPs or backend management ports. If the address is still connecting, the UI should say so instead of showing a joinable-looking hostname with an unrelated error buried underneath.
Ports without the confusion
Local Hosting may use a local Minecraft port on the user's device, while the SPUDZWARE network has its own central routing architecture. These values serve different purposes. The UI should not encourage users to change infrastructure ports simply because a local process has not started yet. When a local port is unknown, “Waiting for server” is more useful than a bare dash.
Java and Bedrock are different network paths
Java Edition normally connects over its Java server address. Bedrock crossplay, when provided through a compatible Geyser/Floodgate setup, can require its own UDP-facing port and readiness check. Do not assume that Java success automatically proves Bedrock readiness; show the address and port specific to the client.
What a good status page reports
A useful hosting status distinguishes Starting, Online, Offline and Connection Error. Player count and memory are meaningful after the server is running. Tunnel retries, process IDs, exact local ports and low-level health probes can stay in technical details for support rather than dominating the normal server card.
Common failure patterns
| Symptom | Likely layer | First action |
|---|---|---|
| Server process stopped | Minecraft/runtime | Read startup log and retry only after the cause is clear. |
| Server running locally, public address offline | Public route/tunnel | Retry the connection; do not restart Minecraft automatically. |
| Java works, Bedrock does not | Crossplay/UDP readiness | Check Geyser/Floodgate and the Bedrock-specific port/state. |
| Port already in use | Local listener | Identify the conflicting local process before changing routing. |
Security
Public routing credentials and authentication tokens should never be shown in the UI, copied into support tickets or stored in world folders. Keep admin/dev services private, keep Minecraft online-mode/security settings intentional, and share only the join information players actually need.