You Cannot Connect to a Server. Here Is Why

You found a server, you clicked connect, and something went wrong. Maybe a timeout. Maybe an error about a version. Maybe it just sat there and then went back to the menu without explanation.

There are about nine reasons this happens, and they are not equally likely. Working through them in order of probability rather than in order of interest gets most people connected in under two minutes.

1. Wrong game version

By a distance the most common cause, and the one most often misread as a network problem.

Servers accept clients matching their version, and updates are not synchronised, your game may have updated overnight while the server has not, or the reverse.

How to tell: the listing usually states a version. Compare it to yours. Errors mentioning "protocol", "incompatible", "outdated client" or "outdated server" are all this.

What to do: update or roll back to match, or find a server on your version. Many launchers allow selecting an older version, which is the fastest fix for a server that has not updated yet.

The Minecraft special case: you may be on the wrong edition rather than the wrong version. Java and Bedrock cannot connect to each other's servers at all. Bedrock or Java covers telling them apart, and this alone accounts for a large share of failed Minecraft connections.

2. The server is down

Obvious, routinely skipped.

How to tell: look at the listing rather than trying again. A server showing offline with a recent gap in its uptime history is down, not refusing you specifically. How these figures are produced explains what is being measured.

What to do: check back later, or check the server's Discord where an outage is usually mentioned within minutes.

The FiveM exception: FiveM reports itself over HTTP rather than a query protocol, and it can appear offline on lists while running perfectly. Why a FiveM server shows offline covers the mechanism: if it is FiveM and the listing says offline, it is still worth trying.

3. You are missing content

Common on modded servers, and it does not always announce itself clearly.

Modded Minecraft requires the exact modpack, matching versions. A vanilla client cannot join a Forge or Fabric server.

Garry's Mod and Source games download content on connect, and a failed or stalled download reads as a failed connection.

What to do: check whether the server requires a modpack before connecting. If the download stalls repeatedly at the same point, that is the server's content host misbehaving rather than your connection, why modded servers take so long to join covers both sides.

4. The address or port is wrong

Check the port. Many games use a non-default port and the listing shows it. 1.2.3.4 and 1.2.3.4:27016 are different servers.

Check for typos, particularly 0 versus O and 1 versus l in a hostname somebody typed out.

Check the address is current. Servers move. A bookmark from six months ago may point at nothing, and an address written in a forum post in 2023 almost certainly does. Connecting by IP directly covers the mechanics for each game.

5. The server is full

Some games say so plainly, some produce a generic failure, and some drop you silently.

How to tell: the listing shows the count against the cap.

The confusing case is a server showing 62/64 that still refuses you, because the last slots are reserved for staff and donors. That is not a bug and there is nothing to fix. The server is full — what now covers queues, reserved slots and which are worth waiting for.

6. You are banned

Worth considering before assuming a technical fault, particularly on a server you have played on before.

How to tell: most games show a ban message, but some produce a generic connection failure, and a ban applied by an IP rule frequently looks exactly like a timeout.

The innocent version of this is a household or shared connection where someone else was banned, or an alt-account detection system linking you to somebody you have never met. Both are appealable, and appealing without making it worse covers how.

7. A whitelist or password

Whitelisted servers reject anyone not on the list, sometimes with a clear message and sometimes not. If the listing mentions an application, that is what happened. Running a whitelist covers why servers use them.

Password-protected servers need the password entered in the right place, which varies by game and is not always where you expect. Private servers and passwords covers it.

8. Your VPN

A meaningful number of servers block VPN and datacentre address ranges, usually to make ban evasion harder. The rejection is rarely explained.

What to do: turn it off and reconnect. If that works, you have found it. Should you block VPN players covers why servers do this; it is a policy rather than a fault, and there is nothing to fix on your end beyond knowing.

9. Your own network

Last on the list because it is the least common and the first place people look.

Restart the game before anything else. A surprising share of connection failures are a client in a bad state.

Try a different server. If everything fails, it is you. If one server fails, it is that server.

Check your firewall if you have recently changed something.

Try a phone hotspot. Ten seconds, and it distinguishes "my connection" from "everything else" definitively.

Game-specific causes worth knowing

Some titles have their own recurring failure that does not fit the general list.

Minecraft: the edition, then the version. Java and Bedrock cannot reach each other's servers at all, and this is the largest single cause of failed Minecraft connections. After that, exact version matching. Bedrock or Java covers telling them apart in about ten seconds.

Minecraft: online-mode. A server running with account verification disabled will reject a normally-authenticated client on some configurations, and vice versa. Usually only relevant on private or offline servers, private servers and passwords covers when this is deliberate.

Source games: a missing map. On servers running custom maps, a failed download appears as a disconnect after the loading screen rather than as a download error. Retry once; if it fails at the same point, the server's content host is misconfigured.

Source games: sv_pure. A server configured to reject modified client files will drop you if you have custom models, skins or sounds installed. Removing them, or launching without them, resolves it.

FiveM: an artifact mismatch. After a GTA update, servers and clients can be briefly out of step. Usually resolves within a day or two and there is nothing to do but wait.

Rust and Oxide games: a plugin rejecting you. Group limits, VPN checks and whitelist plugins all reject with generic messages. The server's Discord will say which.

Older GoldSrc titles: occasionally a client build mismatch, particularly on servers running long-standing community patches. Finding servers for games everyone says are dead covers the wider set of quirks in these titles.

Errors that look like something else

"Connection timed out." Nothing answered. Server down, wrong address, wrong port, or blocked.

"Connection refused." Something answered and said no. The address is right, the port is wrong or nothing is listening on it.

"Disconnected by server" immediately after joining. Not a network problem: a ban, a whitelist, a full server, or a mod check that failed.

A crash on connect. Usually a content or version mismatch rather than a connection issue.

Joining and then dropping after twenty seconds. Frequently a download that failed, or a plugin rejecting your client.

When it worked yesterday

A server you have played on before that suddenly refuses you narrows the field considerably, because most of the general causes are already ruled out.

Your game updated. The most likely explanation by a distance. Launchers update overnight and servers do not always follow the same day.

The server updated. The reverse.

The server moved. Address changes happen, and a bookmark or a favourite entry keeps pointing at the old one. The listing has the current address — moving a server between hosts covers why owners are supposed to keep a domain precisely so this does not happen.

You were banned. Sometimes without a message, particularly if it was applied to an address rather than an account.

A whitelist was added. Servers sometimes close after a griefing incident, and existing players are not always automatically included.

Your VPN switched on. Or your ISP changed your address into a range the server blocks.

Checking the listing first resolves the first three, which between them account for most of this category.

The two-minute sequence

1. Check the listing. Online? Version? Full?, resolves most cases immediately
2. Restart your game. Free, and fixes more than it should
3. Check the port is included and correct
4. Turn off the VPN if you use one
5. Try another server to establish whether it is you
6. Ask in their Discord. Somebody else has hit the same thing, usually today