Cuberite does not recognize Velocity as a proxy
aokod opened this issue · comments
Client version: 1.12.2
Server OS: Debian Linux
Cuberite Commit id: 95bc2e
Expected behavior
Ever since commit c52942 Cuberite is supposed to have BungeeGuard-style support for BungeeCord and Velocity (see PR #5291).
Actual behavior
Cuberite does not seem to recognize Velocity as a proxy when a user attempts to join from the Velocity server and is connected to a Cuberite server by the proxy if OnlyAllowBungee is used. Other configurations fail to authenticate the user.
Steps to reproduce the behavior
Try and connect to a Cuberite server that has authentication disabled through a properly configured Velocity server. The same Cuberite server should be joinable if used with BungeeCord.
Server log
Info [00:41:19] Kicking player fssp for "You can only connect to this server using a Proxy."
Info [00:42:17] Kicking player fssp for "You can only connect to this server using a Proxy."
Info [00:46:21] Kicking player fssp for "Unable to authenticate."
Taken from the Velocity server:
[00:46:21] [Netty epoll Worker #3/ERROR]: [connected player] fssp (/[ip]:12345): disconnected while connecting to creative: Unable to authenticate.
[00:46:21] [Netty epoll Worker #3/INFO]: [connected player] fssp (/[ip]:12345) has disconnected: Unable to connect to creative: Unable to authenticate.
yes, could be usefull to have a Velocity support