Make an Eaglercraft server

Players connect with wss://. Your Java server still speaks the usual game port. EaglerXServer sits between them. The readme describes one JAR that can run with Spigot, Bungee or Velocity.

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

Requirements below come from the EaglerXServer README and configuration reference. No server was deployed for this guide, and no free or always-online hosting service is promised.

What the readme actually requires

• Java 17 or newer.
• Protocol support documented for 1.8, 1.12.2 and 1.5.2. 1.5.2 may need EaglerXRewind. 26.2 is not in that support list.
• ViaVersion and ViaBackwards appear in the template discussion when you want more than one Java version.
• enable_tls defaults to false in the notes, while require_tls defaults to true. People put nginx or Caddy in front and terminate WSS there.
• A large view distance can end the stream. That is called out in CONFIG.md.

A public Paper template aimed at 1.12.2 says port 25565 can accept both Java and Eagler clients when the bridge is installed. A template is a starting point you must maintain. It is not a hosting recommendation.

Implementation sequence from the README

• 1. Back up an existing server. Choose a Spigot/Paper server or a BungeeCord/Velocity proxy and install Java 17 or newer. The README recommends the proxy route and says Bukkit support above Minecraft 1.17 is not currently maintained.
• 2. Obtain EaglerXServer from the repository Releases page. Put its JAR in the chosen platform's plugins folder. Do not leave the old EaglerXBungee or EaglerXVelocity bridge installed beside its replacement.
• 3. Install compatible ViaVersion, ViaBackwards and ViaRewind versions when protocol translation is needed. Add EaglerXRewind only if you need the documented 1.5.2 browser-client support.
• 4. Start the chosen server to generate configuration, then stop it before editing. On BungeeCord/Velocity, set inject_address in the EaglercraftXServer listener configuration to an actual listener address from the underlying proxy configuration; do not invent a second listener port.
• 5. Read the generated comments and CONFIG.md for your installed release. Decide where TLS ends. If nginx or Caddy terminates public WSS, configure WebSocket upgrade forwarding to the bridge listener and use a valid certificate for the public hostname.
• 6. Publish the full wss:// hostname, port when non-default, and path when configured. Permit only the intended public listener through the firewall and keep backend-only ports private. Do not assume Java port 25565 is also the public TLS port.
• 7. Verify startup logs, listener binding, DNS, certificate hostname/expiry, reverse-proxy upstream and WebSocket upgrade behavior. Then perform a separate authorized join test with a documented client version before publishing the address. No server or join test was run for this guide.

Port and login checks

For a direct bridge listener, the README says Java and Eagler connections can share an IP and port; a reverse proxy may expose a different public TLS port. A Java ping alone does not test WSS. If the browser reaches the login phase but times out, compare the proxy and backend logs before changing eagler_login_timeout, whose documented default is 10000 ms. Issue 183 describes a Minecraft 26.2 Paper backend behind Velocity; it does not identify the browser client as 26.2 or publish a fix.

Third-party video: How to: Create a free Eaglercraft server! by RigBot, published 15 December 2025. Identity and upload metadata were checked on 27 October 2026; this is not an official release note, a complete content review, or a gameplay test by this site. The local player cover is original artwork, not a frame from the video.

Play video

How to: Create a free Eaglercraft server!. The player loads only after you press play.

Related: Handshake timeout · Source · Moderation