Backend connection
Backend addressing, PROXY protocol and direct-access restrictions.
Backend address
The backend must be reachable from Lumin. Use the actual host and port of your server or proxy. Do not use a backend domain that points back to Lumin, which would create a connection loop.
PROXY protocol
Lumin can forward the player's real address using PROXY protocol. Receiver configuration depends on your backend, such as Velocity or another proxy. Configure both ends consistently before sending traffic; do not enable a header receiver on software that does not support it.
There is no single configuration that applies to every server implementation. Consult documentation for your exact backend version and your Lumin integration settings.
Restrict direct access
Configure the backend firewall to accept Minecraft connections from the agreed Lumin source addresses. Preserve your administrative access and test rules on one server first.
DNS ingress addresses are not necessarily the firewall source allowlist. Confirm the correct addresses before applying rules.
Deployment checks
- Join through the player-facing domain.
- Verify player-address forwarding if configured.
- Confirm direct backend access cannot bypass protection.
- Keep a rollback plan for your DNS and firewall changes.