Before you start
Copy the full message, time, client edition and version. Record the address and port actually assigned in the panel. Check whether another player can join the same server. Back up the world and configuration before making changes. Remove RCON passwords, database credentials and tokens from logs shared with anyone.
Use the correct edition and protocol
Java and Bedrock clients do not directly connect to the same server software. Crossplay requires an explicitly configured, compatible gateway. Having an IP address does not show that such a gateway is installed. Check your chosen edition and the features actually offered for the service.
Java gameplay generally uses a TCP endpoint, while Bedrock server gameplay uses UDP. Common defaults never replace the panel allocation. On a shared node, copying a default port from a tutorial can conflict with another instance. A TCP test cannot validate Bedrock UDP connectivity.
Confirm that startup has finished
Open the logs and look for completed startup, bind errors, out-of-memory shutdowns or failing extensions. A machine or container being online does not prove the game accepts connections. World generation can take longer than an ordinary restart.
After adding a plugin or mod, check its dependencies and engine compatibility. Paper, Fabric, Forge and NeoForge do not automatically load the same extensions. Use a test copy and remove only the identified addition; deleting a world is not a way to diagnose a software error.
Separate the server address from DNS
Try the assigned IP address and port before testing a domain name. If that works but the domain fails, check DNS records, their destination and any port information. Java SRV records can advertise a port, but clients and diagnostic tools do not all interpret them identically.
Then compare from another authorised connection. When only one network fails, record its provider and the times rather than immediately changing the global configuration. Blocked ICMP ping does not establish that the game is unreachable; a ping response does not prove the game port is open either.
Check versions, access rules and configuration
Handle version, whitelist or authentication refusals according to their specific messages. Keep authentication and access protections enabled; disabling them globally does not fix routing. Check client, engine and modpack versions, followed by the configured access rules.
Bedrock LAN discovery can also open its usual ports in addition to a custom port. On a shared node, use the panel’s adapted configuration and request an allocation-conflict check. For a Java proxy or crossplay gateway, inspect every stage of the path rather than only the public address.
Distinguish simulation delays from networking faults
When players join and then disconnect, compare logs with CPU load, memory, free disk space and world activity at the same time. Heavy generation, a slow database or a blocking plugin can disrupt play while networking works. More RAM does not resolve every cause.
Where supported, profile the server during the issue with a compatible tool. Recent Paper versions include spark. A report from an empty server is less useful than one captured during the slowdown. Bound the recording and protect diagnostic links that may contain sensitive information.
Escalate with precise evidence
Give support the edition, versions, address used, time and timezone, exact message and completed tests. Explain whether direct IP works, whether the domain fails and which networks are affected. Include useful log excerpts after removing secrets.
Suspected DDoS activity needs correlation with traffic measurements or mitigation events. A timeout alone is insufficient evidence. Avoid repeated restarts and aggressive scans: they add load and make diagnosis harder. Test the fix using a normal connection, then check that regular players can return.
For your situation
| Situation | Next check |
|---|---|
| IP works but the domain fails | Check DNS destinations and, for Java when used, the SRV record. Treat the assigned port as the reference. |
| Only one network fails | Compare times and routes using another connection. Give support the provider and the exact message. |
| Startup does not finish | Read engine, memory, port and extension errors. Investigate the latest change on a copy before modifying the world. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.