-
Notifications
You must be signed in to change notification settings - Fork 77
Description
Minecraft uses its own encryption protocol and not TLS:
https://minecraft.wiki/w/Java_Edition_protocol/Encryption
When I use this caddy-tailscale Docker container, users are not able to connect to my Minecraft Docker container. However they are able to connect other containers fine.
There is this tool for unwrapping TLS
https://github.com/lucasew/untls
There is this too, but I'm not so sure its as useful
https://github.com/lucasew/ts-proxy
When I run Tailscale on my host instead of caddy-tailscale, ask the user to connect to my TS Hostname or IP instead, it works. But then it seem to be exposing everything on my Desktop, instead of just the Docker network.
I saw this something like providing L4 Layer 4 raw UDP might work, but I don't know how to add L4 to caddy-tailscale
https://github.com/mholt/caddy-l4
My Caddyfile looks like the following:
{$MC_DOMAIN}:25565 { bind tailscale/{$MC} reverse_proxy mc:25565 }
with my .env as
TS: tail1cobsticated.ts.net MC: mc MC_DOMAIN: ${MC}.${TS} TS_MC_EXTRA_ARGS:"--advertise-tags=tag:minecraft"
The container is able to ping the other.