Your server is running, but you or your friends can’t connect? There are usually a few common causes: the server hasn’t finished starting, the address is incorrect, the game and server versions don’t match, or the mods are different. The checks below will help you find the cause in most cases within a few minutes.
First, find out who’s affected: If no one can join the server, the problem is usually with the server itself. If only one player can’t connect, the issue is almost always with their game, mods, or internet connection.
- Has the server finished starting? Your server must be online in the Overview. Also open the Console: players can join only once no new startup messages appear there (for example, the
Doneline in Minecraft). The first startup after installation or an update, or with large modpacks, can take several minutes. - Is there currently an outage? If your server appears online in the web interface but can’t be reached in the game, check our status page. If there’s an outage, you don’t need to change anything. Don’t restore a backup or reinstall the server.
- Is the address correct? Copy the IP and port directly from the Overview. The port is always required (format:
IP:Port), unless you’re using a configured subdomain. Don’t change the ports yourself in the configuration file. Your server only works with the ports assigned during setup. - Do the game and server versions match? The game and server must use the same version. After a game update, the client is often newer than the server, or vice versa. Restart the server after updating or select the correct version under Switch games and manage variants.
- Does everyone have the same mods? For modpacks and modded servers, every player must have exactly the same mods, in exactly the same versions, as those installed on the server.
- Is access restricted? Check the whitelist, server password, and ban list. Players will be rejected if they aren’t on the whitelist or their name is spelled incorrectly.
- Connect directly instead of using the server list: If your server doesn’t appear in the server list, connect directly using the IP and port. The in-game list often takes a few minutes to update after startup.
- Check the log file: Open the current log file and look for errors that appear at the exact time of the connection attempt. See Server is down – What now? for instructions.
If everyone else can play, the problem is with the affected player:
- Fully restart the game and launcher, and check that the player is signed in to the launcher correctly.
- Compare the game version and mods with those on the server.
- Temporarily disable any VPN, proxy, strict firewall, or antivirus software.
- Restart the router or try connecting through a mobile hotspot. If that works, the issue is with the home network or internet provider.
| In-game message | Cause | Solution |
|---|---|---|
Connection timed out: getsockopt / Connection failed, timed out | Server is offline or still starting, incorrect port, or the player’s firewall | Check the console and copy the IP:port again from the Overview |
Outdated server / Outdated client | The game and server use different versions | Match the versions; see step 4 |
Failed to decode packet / Mismatched mod channel list | Client and server have different mods | Use the same modpack and version on both sides |
You are not white-listed on this server! | Player isn’t on the whitelist | Edit the whitelist |
Failed to verify username / The authentication servers are currently not reachable | Minecraft’s authentication service is experiencing an issue | Wait and try again later; check Minecraft’s status |
Bedrock players can’t connect directly to a Java server. You’ll need GeyserMC and its own Geyser port. See Java-Bedrock crossplay with GeyserMC. For Minecraft Bedrock, for example, the “Terracotta” error has its own section under Minecraft Bedrock: Common issues. Find more solutions under Minecraft: Common issues.
- Server setup isn’t complete: Your FiveM server must be fully set up and started in txAdmin before anyone can join. See Import a server base in txAdmin.
- “Cfx failed to reach the server” appears in the console: If it appears immediately after startup, it’s usually harmless. Test the connection by pressing
F8and enteringconnect IP:Port. If that works, the server should appear in the server list shortly. - Loading screen is stuck (for example, at “Awaiting scripts”): This is almost always caused by a faulty resource. The Live Console in txAdmin shows which one. Learn more under Install resources.
- Player isn’t on the whitelist: See FiveM: Whitelist.
- Connection drops while loading: Clear the game cache. See Clear the cache.
Find more solutions under FiveM: Connect to the server and FiveM: Common issues. For RedM, see RedM: Common issues.
Many games have dedicated guides to connection issues, including Valheim: Common issues, SCUM: Common issues, Hytale: Common issues, and Hytale: Slow connection. Check the Troubleshooting section in your game’s category.
In rare cases, DDoS protection can also filter out normal connections. A typical sign is that players reach the password prompt or loading screen but then get a timeout, even though the server is running. In the DDoS Protection tab, you can see whether an attack is currently being filtered. If your server has a dedicated IP address, you can briefly disable the protection to test. This isn’t possible with shared IP addresses. In that case, contact support. See Report a connection issue to support.
Connecting to your server files: Issues with FileZilla or WinSCP aren’t related to joining the game. See SFTP access for instructions on connecting to your server files.
If none of these steps helped, start a support chat in your ZapX customer account. To help us resolve the issue quickly, include:
- the game and version you’re using,
- the exact error message in the game (text or screenshot),
- whether all players are affected or only some,
- when the issue started and what you changed most recently,
- the error lines from the log file at the time of the connection attempt.