Can’t Connect to Minecraft Server (Checklist)

Checklist

1. Server online? Pterodactyl shows running and console is past Done.
2. Correct address? Panel IP:port — not localhost.
3. Edition match? Java client → Java server.
4. Version match? Client protocol compatible with server jar.
5. Whitelist / ban? Console: whitelist list, banlist.
6. DIY firewall? Only for self-hosted VPS — open 25565/tcp (Linux guide).

Managed Chapter22 customers skip home-router forwarding; the allocation is already public on the game node.

Related guides

• Ports Explained
• How to Join
• How to Open Ports on a Linux VPS (UFW, firewalld, iptables)
• DDoS Protection Basics for Game Servers

Frequently Asked Questions

Works on localhost only?

You are using 127.0.0.1. Friends need the public panel IP:port.

Java vs Bedrock?

Different editions. Use Geyser only if you intentionally bridge.

Managed hosting still failing?

Confirm the server is online, version matches, and whitelist/online-mode are not blocking.

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.