Handshake timed out

The message appears when the browser client starts the WebSocket and the server does not finish the handshake in time. EaglerXServer’s config notes mention eagler_login_timeout, with a default around 10 seconds, and they discuss TLS being terminated by nginx or Caddy because enable_tls defaults off while require_tls defaults on.

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

Issue 183 reports an EaglerXServer Velocity proxy connected to a Minecraft 26.2 Paper backend. It does not identify the browser client as 26.2. At this review the issue was open with zero comments, not a documented fix.

• Confirm the published wss:// address, port/path and certificate hostname. Public clients need a certificate chain their browser trusts.
• Operators: compare timestamped proxy/backend logs, inject_address and the reverse proxy WebSocket upgrade configuration before changing timeouts.
• The configuration documents eagler_login_timeout as 10000 ms. Raising it does not repair wrong listeners, missing upgrades, authentication failures or protocol mismatches.
• Issue 183 reports a modern Paper backend behind Velocity. It is a user report, still open with zero comments at the review, not evidence that the browser was running 26.2 or that all modern backends are unsupported.

Related: Make a server · Can’t connect