Fix “Failed to Connect to Server” by checking the server address first, then the firewall, then the network path. Minecraft Java servers commonly use port 25565, so one wrong digit, blocked port, or weak connection can stop the join attempt cold [source: Minecraft Wiki].
TLDR: The player should confirm the IP or domain, add the port if needed, allow Minecraft through the firewall, and restart the router if the error keeps showing. For example, play.example.com:25565 may work while play.example.com fails if the server uses a custom setup. In many cases, the fix takes under 5 minutes, but firewall rules and router issues can stretch it to 20 minutes or more. It drives players crazy that one copied space at the end of an address can waste an entire evening.
1. Check the Minecraft Server Address
The most common cause is boring but real: the server address is wrong. The player should copy the address again from the server owner, website, or Discord post. Extra spaces, old domains, missing ports, and mixed-up characters are common troublemakers.
- Java Edition format: example.com or 123.45.67.89:25565
- Bedrock Edition format: server address plus a separate port field
- Local server format: a private IP such as 192.168.1.25
If the server uses a custom port, the Java player must add it after a colon. A missing port can cause Minecraft to contact the wrong door, so the server looks offline even when it is running.
2. Confirm the Server Is Actually Online
Before changing computer settings, the player should check if the server is up. A restart, crash, expired hosting plan, or plugin issue can block everyone. The fastest test is simple. Another player should try to join.
If nobody can connect, the issue is probably on the server side. The owner should check the console for crash messages, restart the server, and confirm the host panel shows it as online.
3. Allow Minecraft Through the Firewall
A firewall can block Minecraft even when the server address is perfect. Windows may treat a new Java version, launcher update, or modded client as a new app. That means old allow rules may no longer help.
- Open Windows Security.
- Go to Firewall and network protection.
- Select Allow an app through firewall.
- Allow Minecraft Launcher, Java Platform SE Binary, or the modded launcher.
- Enable both Private and Public if the network type is unclear.
Microsoft also lists firewall app permissions as a standard Windows security control [source: Microsoft]. The player should avoid allowing unknown apps, but Minecraft and Java must be allowed if they are being blocked.
4. Check Antivirus and VPN Settings
Some antivirus tools inspect game traffic. Some VPNs route traffic too slowly or block game ports. Honestly, it feels like security apps sometimes “help” by breaking the thing the player just opened.
The player should test without the VPN first. If Minecraft connects, the VPN server or protocol is the problem. If antivirus has a gaming mode or network shield, the player should add Minecraft as a trusted app instead of turning protection off for good.
5. Restart the Router and Flush DNS
Network gear gets weird. A router can hold bad routing data or stale DNS records. A full restart often helps more than expected.
- Close Minecraft.
- Unplug the router for 30 seconds.
- Plug it back in and wait for a full connection.
- Restart the computer or console.
- Try the server again.
On Windows, the player can also open Command Prompt and run:
ipconfig /flushdns
This clears cached domain records. It helps when a server moved to a new IP but the computer still remembers the old one.
6. Test the Network Path
If only one player cannot join, the issue is likely local. The player should try another network, such as a mobile hotspot. If the server works there, the home network or ISP may be blocking traffic.
A server owner hosting from home must also check port forwarding. The router needs to send port 25565 to the correct local server computer. The server computer should also keep the same local IP. If its IP changes after a reboot, the forwarding rule points to the wrong machine.
7. Match Game Version, Mods, and Whitelist
Not every “failed to connect” message is caused by the network. The player may be using the wrong Minecraft version. A 1.20.4 client may fail on a 1.21 server. Modded servers are even pickier.
The player should check these items:
- Game version: must match the server or be supported by it.
- Mod loader: Forge, Fabric, Quilt, or NeoForge must match.
- Mod list: required client mods must be installed.
- Whitelist: the player name must be added by the server owner.
- Account status: cracked clients will not join online-mode servers.
FAQ
Why does Minecraft say “Failed to Connect to Server”?
It usually means Minecraft cannot reach the server. The cause may be a wrong address, closed port, firewall block, offline server, bad DNS, VPN issue, or version mismatch.
Should the server address include a port?
Sometimes. Java players should add the port after a colon if the server uses a custom port, such as play.example.com:25570.
Can Windows Firewall block Minecraft?
Yes. Minecraft, Java, or a modded launcher may need permission on private and public networks.
Why can friends join but one player cannot?
The issue is probably on that player’s device or network. Firewall rules, VPN settings, DNS cache, or ISP routing may be the cause.
What should a server owner check first?
The owner should confirm the server is online, then check console errors, port forwarding, firewall rules, and the server IP.



