IP forwarding help
sfxworks opened this issue · 3 comments
Regarding the solution of forwarding IPs, I've run into a bit of an issue here.
[07:02:43] [Netty Epoll Server IO #1/WARN] [luckperms]: LuckPerms already has data for player 'sfxworks' - but this data is stored under a different UUID.
[07:02:43] [Netty Epoll Server IO #1/WARN] [luckperms]: 'sfxworks' has previously used the unique ids [09505c86-934f-4be8-84f0-aef3fa96cd0d] but is now connecting with 'da5d1871-31d9-3164-9ad1-a3308bba823b'
[07:02:43] [Netty Epoll Server IO #1/WARN] [luckperms]: The UUID the player is connecting with now is NOT Mojang-assigned (type 3). This implies that THIS server is not authenticating correctly, but one (or more) of the other servers/proxies in the network are.
[07:02:43] [Netty Epoll Server IO #1/WARN] [luckperms]: If you're using BungeeCord, please ensure that IP-Forwarding is setup correctly on all of your backend servers!
[07:02:43] [Netty Epoll Server IO #1/WARN] [luckperms]: See here for more info: https://github.com/lucko/LuckPerms/wiki/Network-Installation#pre-setup
Using k8s and ClusterIPs with 1 NodePort exposed. So pretty much if I forward IPs, I can't connect to my other servers as they are pods and IPtables is managed by k8s here. Id rather not touch this...things could get messy if I start messing with this service's dependencies. Is there a way to clear and reset UUIDs or another method to use my saved permissions?
Enabled via sponge and bungee still yields the servers not reaching each other. If I turn it off they are fine. Even if it is done via Minecraft, is it not forwarding the IP to the new server? Thus, the new container? The container only accepts traffic within the 10.0.0.0/8 range.
There are two settings in the Sponge config you need to enable. One is called bungeemode (or similar) and the other ip-forwarding (or similar).