Docs
Setup instructions for connecting your Minecraft servers to Covariant Game.
Bedrock: NetherNet setup
NetherNet is the newer way Bedrock Edition connects to servers. This page covers how to configure Geyser for NetherNet behind our shield.
NetherNet works with your own domain: we recognize your server by the domain name the player typed. You do not need a separate Bedrock address for it. Players simply join with the domain your Java players already use, on port 19132.
What you need
- Geyser with NetherNet support, set to
transport: nethernet. - A backend in the dashboard with kind Bedrock (Geyser), pointing at Geyser’s address and its TCP signaling
port. - These ports reachable from our IP addresses (the IP list is linked in the dashboard):
- TCP on Geyser’s
port(for example19132) for signaling. - UDP on Geyser’s
webrtc-port(for example19133) for the game traffic.
- TCP on Geyser’s
Configure Geyser
Set these options in Geyser’s config.yml:
bedrock:
address: 0.0.0.0
port: 19132
# use "0" to re-use the 19132 port for this.
webrtc-port: 0
transport: nethernet
signaling:
mode: builtin
advanced:
bedrock:
signaling-trusted-proxies:
- https://game.covariantedge.com/ips.txt
prefer-signaling-proxy-address: trueWhat these options do:
portis the TCP port for signaling. Use this same port for your backend in the dashboard: it is the only port players reach through us, so the backend’s port is the signaling port.webrtc-portis the UDP port for the game traffic. Any free port works. Withtransport: nethernet,0reusesportover UDP.addressmust stay0.0.0.0, or your server’s own network address. With127.0.0.1, no player can connect over NetherNet.signaling.modemust bebuiltin, see the warning below.signaling-trusted-proxieslets Geyser trust the player IPs that we forward. See Real player IPs.prefer-signaling-proxy-addresstells Geyser to use the player IPs that we forward.
After updating your config, restart Geyser to activate NetherNet.
Warning: keep signaling.mode set to builtin. The nxs and hybrid modes register your server with an external signaling service, which hands players your server’s real address. Those players then bypass protection completely. Geyser also switches to nxs on its own when signaling cannot use its port. This happens with clone-remote-port: true, or when your Java server uses the same port. Keep clone-remote-port disabled and give Geyser its own port.
Warning: leave these Geyser options empty behind our shield:
signaling.builtin.https: we handle TLS for your domain and talk to Geyser over plain HTTP. With a certificate configured here, Geyser refuses those requests and NetherNet stops working.signaling.builtin.advertise-addresses: Geyser already reports the addresses we need. Do not enter our IP addresses here.
Proxy protocol does not apply to NetherNet: we forward player IPs with the X-Forwarded-For header instead, see Real player IPs.
Real player IPs
We forward the player’s IP in the X-Forwarded-For header of the signaling request. Geyser only trusts this header from the addresses in signaling-trusted-proxies:
advanced:
bedrock:
signaling-trusted-proxies:
- https://game.covariantedge.com/ips.txtThis setting does two things:
- Geyser sees the real player IP while the connection is set up, including connection checks by Geyser extensions.
- Our addresses are exempt from Geyser’s connection limit. Geyser’s signaling accepts only 8 connections at a time per IP address. All your players reach Geyser through a few of our addresses, so without this exemption, players can fail to connect while many join at once.
Geyser loads the IP list once at startup. If our IP addresses change, restart Geyser.
Troubleshooting
Bedrock players cannot connect, or only some of them can
NetherNet is not reaching your Geyser.
- Check that Geyser logged
Built-in signaling started on ...at startup, and thattransportisnethernet. - Check that the backend port in the dashboard is Geyser’s signaling
port, and that the backend kind is Bedrock (Geyser). - Check that TCP on that port is open for our IP addresses.
- Check that players join with a domain, which is added in the dashboard.
The server shows up in the list, but joining times out
Signaling works, but the game traffic does not get through.
- Check that the UDP
webrtc-portis open for our IP addresses. - Behind a NAT or in a container, check that the
webrtc-portis forwarded with the same port number. - Check that Geyser’s
addressis not127.0.0.1. - Check that your host’s own firewall does not filter UDP traffic from us.
Players fail to connect while many join at once
Add our IP list to signaling-trusted-proxies, as shown under Real player IPs above.