Can’t connect

Connection failures come from the address, the version, or the wrong menu. Browser servers want wss://. Java hosts such as donutsmp.net do not become Eaglercraft servers when you paste them into the box.

Last reviewed: 2026-10-28. By the Eaglercraft Guide editorial team.

Record the exact address, client version and error before changing settings. A shared-world invite code and a public server WebSocket URL go into different connection flows.

Copy the address from the directory page, including wss://.
Match your client (1.8.8, 1.12.2, 26.2 or 26.3) to the server tag.
Shared worlds use the worlds list. They are not the public server directory.
If the directory join link works and your typed address does not, trust the link.
Mobile browsers drop sockets when the tab sleeps. Rejoin rather than changing clients.

Original pixel illustration of a grass field, wooden house, pond and sheep

Original pixel illustration of a torch-lit cave, chest and blue pool

Questions

My friend’s world says not working.

Have them reopen the shared world and send a fresh link. Your export of an old world is not their live session.

Related: How to join · Worlds · Handshake

Still broken? Related checks

These links explain related topics, not a guarantee of compatibility with every build or server.

Sources

Project FAQ: 1.8 world transfer, shared-world invitations, controls, browser requirements and PBR. Reviewed 2026-10-28.
EaglerXServer README: Java 17, supported browser clients, installation and proxy listeners. Reviewed 2026-10-28.
HeartSMP operator wiki: 26.2 WASM client, WSS endpoint and 26.3 backend; not a join test. Reviewed 2026-10-28.
ArchMC listing: wss://arch.mc, 1.8.8 tag and advertised modes. Reviewed 2026-10-28.

Original illustrations on this page are drawn for eaglercraft.pro. They are not official screenshots.