Information about using Geyser with TCPShield


Panel Setup

First, create a separate backend set which points to your instance.
To avoid lengthy debugging process, make sure you can login to your IP:Port on the Minecraft Bedrock client first i.e., please don't come to us with a broken Geyser instance.
An example for a Geyser backend set
After you've created a backend set, you can head to the Bedrock section on our panel and create a Bedrock tunnel:
Creating Bedrock Tunnel
Select the backend set that you have created:
Select the appropriate backend set
Click 'Done,' and you will be able to create your Dedicated Bedrock CNAME. Here's what it does:
  • Since Minecraft: Bedrock edition does not support virtual hostname routing, we cannot offer a shared anycasted IP as we can with Java. To overcome this limitation, each IP must be provisioned statically per tunnel.
  • This IP address will efficiently redirect all traffic from Minecraft: Bedrock edition to the backend set you created above. Therefore, you don't need to attach a domain to this backend set on the TCPShield panel.
You can now proceed to the next step: DNS Setup.
Copy your Bedrock CNAME and use it for the next step
Important: while your Bedrock tunnel is active, you won't be able to delete the underlying backend set. If you want to change the your IP address later, you can simply click on Edit. Or you can Delete the tunnel and make another one again.

DNS Setup

The DNS setup is quite similar to the setup one normally goes through to setup TCPShield.
You need to point a new CNAME to the Bedrock CNAME target we've provided you.
An example how to setup the CNAME

Using the same domain to connect to both Geyser and Java Edition

If you want to use, for example, play.example.tld to connect to both your Java Edition and Bedrock server, we need some special configuration.
Setup a SRV record which points to your Java Edition server
The CNAME for your Java Edition server has to be a different one than the one you want your players to connect to. In this case, we will use tcpshield as the name of the CNAME.
In order to get the SRV record setup, you can follow the guide here.
Change the name of your Geyser CNAME
If you have already created the CNAME as described above, change its name to the subdomain you want your players to be able to connect to. If you haven't created the CNAME yet, you can follow the steps as outlined above with the difference to set your name to, in this example, play.
An example of a full setup
After this is done, you are able to connect to both your Java Edition and Bedrock server with play.example.tld!

Plugin Setup

For the plugin not to block incoming Geyser connections, please create a new file under plugins/TCPShield/ip-whitelist. In this example, we will call this name geyser.list.
Add these lines to the file:
After you have saved the newly-created file and restarted your server, the plugin has been setup.

Proxy Protocol Setup

For those that can't use the TCPShield plugin, it's highly recommended that you switch to proxy protocol. Detailed instructions can be found here.

Firewall Setup

If you are using proxy protocol or want to use improve the secure your backend: You should considered block all incoming connections using a firewall solution. For this example, iptables is used.
ipset -F tcpshield
ipset -X tcpshield
ipset -N tcpshield nethash
for IP in $(curl -q; do
ipset -A tcpshield $IP
iptables -t raw -F
iptables -t raw -A PREROUTING -m set --match-set tcpshield src -p udp --dport 19132 -j ACCEPT
iptables -t raw -A PREROUTING -p udp --dport 19132 -j DROP

IP Forwarding

Currently, IP forwarding isn't yet supported but we are working very closely with the Geyser team to get it implemented.