If you cannot connect to a Minecraft Java server, the cause may be an incorrect server address, wrong port, incompatible Minecraft version, whitelist settings, a mod mismatch, a server startup problem, or a network issue.
This guide explains how to troubleshoot common connection problems on a Down Side Hosting Minecraft Java server.
Down Side Hosting Minecraft servers use:
dsh.network:YOUR_PORT
Replace YOUR_PORT with the port assigned to your specific server.
For example:
dsh.network:25570
The example port above is only an example.
Use the port shown for your own Minecraft server in the Down Side Hosting server panel.
For basic connection instructions, see:
How to Connect to Your Down Side Hosting Minecraft Java Server
Before troubleshooting the player's computer, check the server.
Open your Down Side Hosting server panel and select:
Console
Make sure the Minecraft server has completely started.
If the server is stopped, starting, or repeatedly crashing, players may not be able to connect.
If the server will not start, see:
Keep the server console open while the player attempts to join.
If Minecraft reaches the server but rejects the connection, the console may show the reason.
Look for messages involving:
This can help determine whether the connection is reaching the server at all.
Make sure the player is using:
dsh.network:YOUR_PORT
For example:
dsh.network:25570
Common mistakes include:
Each Down Side Hosting game server can have its own assigned port.
The port identifies which Minecraft server the player is trying to reach.
For example:
dsh.network:25570
and:
dsh.network:25571
can represent two different servers.
Always use the port assigned to your server.
A connection-refused message generally means the client reached the destination but nothing accepted the connection on the requested port.
Check:
Also check the server console.
A timeout means the connection attempt did not successfully complete.
Possible causes include:
First verify that the server is online and another player can connect.
An Unknown Host error usually means Minecraft could not resolve the hostname.
For Down Side Hosting, verify that the player entered:
dsh.network:YOUR_PORT
and did not misspell:
dsh.network
Also check the player's internet connection and DNS resolution.
The player's Minecraft Java version needs to be compatible with the server.
For example, if the server requires a particular Minecraft version, a player using another version may receive an incompatible-version message.
Check:
When troubleshooting, using the exact version expected by the server is a good starting point.
Minecraft may display messages indicating that either the client or server is using an incompatible version.
If the client is too old, launch the Minecraft version required by the server.
If the server is running an older version intentionally, players need a compatible client unless the server has software that specifically provides cross-version support.
If the player receives a message indicating they are not whitelisted, add their Minecraft username to the server whitelist.
From the server console:
whitelist add PLAYERNAME
For example:
whitelist add Steve
To check the whitelist:
whitelist list
See:
How to Whitelist Players on a Down Side Hosting Minecraft Server
Check:
whitelist listRemove and re-add the player if necessary:
whitelist remove PLAYERNAME whitelist add PLAYERNAME
Minecraft authentication-related errors can sometimes occur when a player's login session is no longer valid or when authentication services cannot complete the request.
The player can try:
If multiple players suddenly experience authentication problems at the same time, the problem may not be specific to one player's server configuration.
A normal authenticated Minecraft Java server should generally keep:
online-mode=true
Do not turn account authentication off just to bypass an authentication error.
See:
Forge, Fabric, NeoForge, and modpack servers may require players to have matching client modifications.
Check:
A mismatch can prevent the player from joining even when the server itself is online.
A player may be missing a required mod or using a different version.
For complete modpacks, the easiest approach is usually to make sure the server and player are both using the same modpack release.
For example:
Server Modpack: 4.2.0 Player Modpack: 4.2.0
is preferable to:
Server Modpack: 4.2.0 Player Modpack: 4.1.6
unless the modpack specifically supports that combination.
The connection message or server console may identify a mod that the player is missing.
Install the required client-side mod using the correct:
Do not simply download the newest release without checking compatibility.
The client may have the correct mod name but the wrong version.
Compare the player's:
mods/
with the server or official modpack requirements.
For additional help:
Some Fabric servers use only server-side mods and may allow normal compatible Minecraft clients to connect.
Other Fabric mods require players to install Fabric and matching mods.
Whether Vanilla clients can connect depends on the mods installed.
Many Forge and NeoForge setups require the player's client to use the same or compatible mod configuration as the server.
For a modpack, players should generally install the intended client version of that modpack.
Paper, Purpur, and Spigot normally allow standard Minecraft Java clients to connect unless plugins or configuration alter the connection requirements.
A plugin could potentially affect:
If connection problems began after adding or updating a plugin, see:
If the player briefly joins and is then disconnected, check the server console.
Possible causes include:
The console message immediately before the disconnect is particularly important.
If everyone else can connect normally, investigate the affected player's:
This strongly suggests the server itself is reachable.
If no players can connect, first check:
server.properties changesIf the server shows as running but nobody can reach it, contact Down Side Hosting support.
A server process can appear online even when Minecraft has not successfully completed startup.
Check the console for a normal completed startup.
Also check for:
Failed to bind to port
Address already in use
or repeated startup errors.
Down Side Hosting assigns your server its port.
Do not randomly change:
server-port=
If you changed it, restore the server's assigned configuration.
If you did not change anything and the server reports a binding error, contact support with the complete console error.
The public connection hostname:
dsh.network
should not normally be entered into:
server-ip=
Leave that setting as configured by the hosting environment.
Changing server-ip incorrectly can prevent the server from starting or accepting connections.
If connections stopped working immediately after editing:
server.properties
check whether you changed:
server-port= server-ip= online-mode= white-list=
Restore the previous settings if necessary.
See:
If players can reach the server but joining produces errors after a world migration, check:
For modded worlds, make sure the mods required by the world are still installed.
See:
Large modpacks can take longer to process player connections.
Check whether the server is also experiencing:
Do not assume a timeout is purely a network problem on a heavily overloaded server.
Severe server lag can cause connection problems or timeouts.
Check for:
Can't keep up!
and other performance warnings.
See:
High ping represents network latency between the player and server.
If one player has high ping but others do not, investigate that player's network connection.
Possible factors include:
Additional server RAM will not directly fix high network latency.
A weak or unstable Wi-Fi connection can cause:
When possible, the player can test using a stable wired connection or another network to determine whether Wi-Fi is contributing to the problem.
A VPN can sometimes change network routing and increase latency or create connectivity problems.
If a player is having unexplained connection issues while using a VPN, temporarily testing without the VPN can help identify whether it is involved.
A local firewall or security application can interfere with Minecraft or Java networking.
If Minecraft works on another computer or network but not one specific device, check the local computer's network and security configuration.
Do not disable security software permanently as a troubleshooting solution.
Minecraft Java provides a Direct Connection option.
From:
Multiplayer
select:
Direct Connection
and enter:
dsh.network:YOUR_PORT
This can help determine whether a saved Multiplayer entry contains an old or incorrect address.
If Direct Connection works but the saved server entry does not, delete the old entry and add it again.
Use:
dsh.network:YOUR_PORT
with your current assigned port.
For client-side connection problems:
This is particularly useful for stale login-session problems.
If multiple players suddenly have connection issues:
A restart should not be used to hide a recurring server error.
Whenever someone tries to connect, watch the console.
The difference between:
No console message at all
and:
Player connected and was rejected with an error
is useful.
If nothing appears in the server console when the player tries to join, the connection may not be reaching the Minecraft server.
Check these in order:
dsh.network:YOUR_PORT.Down Side Hosting Minecraft servers use:
dsh.network:YOUR_PORT
Replace YOUR_PORT with your assigned server port.
The server may not be accepting connections on the requested port.
Make sure the server is started and you are using the correct assigned port.
The client was unable to complete the connection.
Check the server status, address, port, player's network, and server console.
Verify that:
dsh.network
was entered correctly and that the player's DNS and internet connection are functioning.
The player's Minecraft version may not match the version supported by the server.
Launch a compatible Minecraft Java version and reconnect.
The problem is more likely to involve your client, Minecraft version, mods, account session, whitelist status, or internet connection.
Check whether the server successfully started and whether the correct port is configured.
If the server appears healthy but nobody can connect, contact Down Side Hosting support.
When contacting Down Side Hosting support, provide:
Do not send account passwords or other private credentials.
Down Side Hosting provides Minecraft Java hosting with server panel access, console controls, file management, backups, and support.
Minecraft Java hosting starts at $2/month.
View Minecraft Java Server Hosting