Bedrock / Geyser issues

Bedrock behind Infinity-Filter requires a dedicated IP, a Geyser module backend, the right Geyser config, and DNS that points at the dedicated CNAME. Most issues land in one of those four buckets.

For setup, see Geyser integration. For the dedicated-IP lifecycle, see Dedicated IPs.

Bedrock cannot connect, Java still works

Almost always one of:

bedrock.enable-proxy-protocol: true

That setting is for a UDP reverse proxy sitting directly in front of Geyser. Infinity-Filter is not one. With IF as the upstream, this must be false.

bedrock:
  enable-proxy-protocol: false

The Bedrock CNAME points at the old dedicated IP

After a dedicated-IP migration, the CNAME at your registrar is unchanged but resolves to a new IP. Players ping the cached old IP and time out.

Fix: confirm the CNAME points at the dedicated-IP CNAME (<uid>.ip.infinity-filter.com), not at the resolved IP. The CNAME stays the same even when the underlying IP rotates.

Stale Geyser backend module

The Geyser module in the panel can hold stale routing data after dedicated-IP changes. Delete it and re-add it from the Backends page — Bedrock connectivity should resume.

”Trouble establishing a connection to multiplayer services”

This Bedrock error usually means UDP traffic isn’t reaching Geyser. Check:

Backend firewall blocking UDP

Allow UDP 19132 (or whatever Geyser port you use) from the IF IP ranges.

Empty haproxy-protocol-whitelisted-ips

If advanced.bedrock.use-haproxy-protocol: true but the whitelist is empty, Geyser silently drops every wrapped UDP packet.

Fix: populate the whitelist with the IF IP ranges, or set advanced.bedrock.use-haproxy-protocol: false if you don’t need end-to-end real-IP forwarding for Bedrock.

Stale Geyser module backend

As above. Delete and re-add the Geyser module in the panel.

Geyser startup warns “HAProxy protocol expected”

use-haproxy-protocol is set incorrectly in advanced. The right values with IF are:

• advanced.bedrock.use-haproxy-protocol: false — by default (IF doesn’t send HAProxy headers to the Geyser UDP listener).
• advanced.java.use-haproxy-protocol: true — only if PROXY protocol is enabled on Velocity/BungeeCord.

If you want end-to-end real-IP forwarding for Bedrock, both advanced.bedrock.use-haproxy-protocol and advanced.java.use-haproxy-protocol go to true, and PROXY protocol is on at Velocity and at the IF Backends page, and the IP whitelist is populated. See Geyser integration.

”Header length exceeds allowed maximum”

The PROXY header isn’t being accepted by Geyser. Check:

• haproxy-protocol-whitelisted-ips includes the IF ranges.
• Your Geyser version supports the HAProxy header (run a recent build).

Bedrock module suddenly stopped after a subscription renewal

Billing has been observed to wrongly flag a dedicated IP for cancellation during renewal. The dedicated IP needs to be re-enabled platform-side.

Fix: open a support ticket on the Discord. We can re-enable it manually.

Bedrock module accepts only one backend

This is by design. Bedrock load balancing is not supported. A network can have one Geyser module forwarding to one backend.

For high-availability Bedrock, run a Velocity proxy with multiple downstream Spigot servers — the proxy distributes load internally; Geyser only handles the Bedrock→Java bridge.

Multi-proxy setup, only some Bedrock players can connect

In a multi-proxy load-balanced setup, Geyser must be installed on every proxy. Bedrock players routed to a Geyser-less proxy can’t authenticate and fail.

Fix: install Geyser (and Floodgate) on every proxy.

Floodgate on the wrong layer

Floodgate goes on the proxy only — never on backend Spigot servers. Installing it on a backend won’t break anything but is the wrong layer.

Backend port surprise

Players connect on UDP 19132 to the IF edge. The backend Geyser port is internal and can be anything; it doesn’t have to be 19132. You don’t need to expose 19132 on the backend.

If you’ve port-forwarded 19132 to Geyser, that’s fine — but it’s a coincidence, not a requirement.

Common one-line diagnoses

What’s next