-
|
Hi! I have tried latest dev ProtocolLib and FastLogin, when i try joining server, it show Invalid session. My client ip in log is right. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
You need to forward the original IP to the Minecraft server. Otherwise features like IP bans, session based logins like in AuthMe will break or even be security risk. This includes FastLogin. Here in this case Mojang rejects your connection, because the IP address incoming to the server is different to the IP address the client made connecting to Mojang. Therefore suspected MITM proxy is assumed. If you really want skip this check, you can disable the proxy check in the configuration file. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer. it works when checking disabled. But the original ip seems to be forward to the server, ip in logs are original. |
Beta Was this translation helpful? Give feedback.
-
|
Is the IP address that FastLogin used a local one? The message clearly indicates that the connection was rejected by Mojang. Maybe there is an encoding issue of FastLogin during the transmission of it. |
Beta Was this translation helpful? Give feedback.
-
|
How is the original IP address forwarded to the server. Maybe FastLogin didn't received that notification. |
Beta Was this translation helpful? Give feedback.
-
IP address showed by FastLogin's log is original. I do not know how my idc do, but may use iptables etc. |
Beta Was this translation helpful? Give feedback.
You need to forward the original IP to the Minecraft server. Otherwise features like IP bans, session based logins like in AuthMe will break or even be security risk. This includes FastLogin. Here in this case Mojang rejects your connection, because the IP address incoming to the server is different to the IP address the client made connecting to Mojang. Therefore suspected MITM proxy is assumed.
If you really want skip this check, you can disable the proxy check in the configuration file.