Skip to content
Game Servers

Fix Minecraft "io.netty... Connection Refused: No Further Information"

io.netty.channel.AbstractChannelConnection refused: no further informationFailed to connect to the server
7 min read Updated 12 June 2026 ESAGAMES Team

This long io.netty error boils down to one thing: your client couldn't open a connection to the server. Usually it's the address, the port, or the server being down. Here's how to check, step by step, including DNS-related causes.

The exact wording of a Minecraft connection error tells you where the problem is. Match yours before diving in — "connection refused" is a very different fix from "timed out":

ErrorWhat it meansWhere to look
Connection refused: no further informationReached the host, but nothing is listening on that portWrong port, or server not running
Connection timed outNo response at all from the addressFirewall/port not open, or wrong IP
Unknown host / UnknownHostExceptionThe domain didn't resolveDNS / a typo in the address
io.netty... internal exceptionConnection dropped mid-sessionUsually server-side lag or a crash

This article covers connection refused — the checks below go in order of how often each is the cause.

Step 1: is the server online?

Confirm it's up for everyone, not just you, with our Minecraft status checker. If it's offline for all, it's the server, not you.

Step 2: check the address and port

"Connection refused" almost always means a wrong address or port. Verify the exact IP/domain, and add the port if it's non-default:

play.yourserver.net:25566   # only if the port isn't 25565

Step 3: server admin checks

  • The server is actually running and bound to the right IP (server-ip= blank usually = all interfaces).
  • The port is open in the firewall and forwarded.
  • There's no SRV-record mismatch if you use a domain.
"No further information"

That phrase just means the OS gave no extra detail — it doesn't indicate a deeper problem. Treat it as a plain "couldn't connect" and check address, port and server status.

It's a connection failure. Check the server is up, then the address and port — that's where the problem almost always is.

DNS and hosting-level causes

  • A domain pointing at an old IP after a server migration — DNS changes take time to propagate; see how to point a domain to a server (DNS A record).
  • The host's network firewall or security group blocks the port even though the server's local firewall allows it — check both layers, not just one.
  • The server crashed silently on startup and never actually opened the port — check the server console/log rather than assuming it's purely a networking issue.

How to prevent this

  • Use a low DNS TTL before a planned IP change so players pick up the new address quickly.
  • Re-check with a status checker after any migration, firewall change, or port edit — don't assume it worked.
  • Publish the exact IP:port (or domain) players should use, and update it everywhere at once if it changes.

A server that's always reachable

Our Minecraft hosting gives you a clean ip:port with the firewall handled — protected, online in minutes.

Minecraft hosting
FAQ

Frequently asked questions

What does "io.netty connection refused" mean in Minecraft?

Netty is Minecraft's networking library; the message means your client couldn't establish a connection. Usually the server is down, or you have the wrong address or port.

What does "no further information" mean?

It just means the operating system returned no extra detail about why the connection failed. It's not a separate problem — treat it as a normal connection refusal.

How do I fix it?

Check the server is online (with a status checker), confirm the exact address and port, and — if it's your server — make sure it's running and the port is open and forwarded.

Is "connection refused" the same as "connection timed out"?

No. "Refused" means something actively rejected the connection (wrong port, server down, or a firewall sending a reject) — it responds fast. "Timed out" means nothing answered at all, often a silent firewall drop or a completely wrong address.

Why does it work with the IP but not the domain?

This points to DNS — the domain may be pointing at an old or wrong IP, or an SRV record is misconfigured. Verify the A/SRV records match the server's current IP and port.

Can this happen right after moving my server to a new host?

Yes — DNS changes take time to propagate, and the old IP may still be cached by some players' resolvers for a while. Using the raw IP:port temporarily confirms whether it's a DNS propagation issue.

Further reading

Go deeper on this

Guides and explainers that pair with this fix — from our guides and blog.

Knowledge base

Related articles

Skip the troubleshooting

Managed, protected hosting in Frankfurt — we handle the Linux, the network and the DDoS so you don't have to.

Payments Secure checkout with cards, banking apps and digital wallets.

Choose the payment flow that fits your stack and region without leaving the platform.

Pay by Zen Visa Mastercard Paysafecard PaysafeCash Skrill Trustly Bancontact UnionPay iDeal WebMoney