Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incompatibility fastlogin #59

Open
cicatrice74 opened this issue Jun 26, 2021 · 16 comments
Open

incompatibility fastlogin #59

cicatrice74 opened this issue Jun 26, 2021 · 16 comments

Comments

@cicatrice74
Copy link

When using latest tcpshield 2.5 and fastlogin it causes fastlogin to not autologin my players, please fix this

@Dogocoton
Copy link

It works for me

@cicatrice74
Copy link
Author

u have to use latest fastlogin dev, latest tcpshield 2.5, it will go asking for login on autologin and autoregister premium players too

@Dogocoton
Copy link

try without tcpshield

@cicatrice74
Copy link
Author

cicatrice74 commented Jun 28, 2021 via email

@Dogocoton
Copy link

try resetting all your server's plugin data and worlds

@cicatrice74
Copy link
Author

cicatrice74 commented Jun 28, 2021 via email

@Dogocoton
Copy link

contact tcpshield via email

@cicatrice74
Copy link
Author

Possible no one has the same problem using tcpshiled >= 2.5 and fastlogin ? It is not properly functioning, it will ask for login every premium player, if you use tcpshield 2.4 it is properly functioning, please, give a test on it, i'm using paper 1.16.5 latest dev and latest fastlogin dev and latest authme reloaded dev, it is annoying repeating the same thing to only know there is an incompatibility and no one seems to be interested in fixing this up.
I have autoregister, autologin enabled on fastlogin, u should try this and finally tell me : "you are right, there is a problem with it, we are going to fix this."

@AlexPresso
Copy link

I opened an issue on the FastLogin project for the same problem: games647/FastLogin#595
Due to TCPShield changing the player IP while after it's authenticated, FastLogin fails retrieving it with:
No on-going login session for player: ...

@SkyDude0
Copy link

i have the same problem only with 2.5+ version

@cicatrice74
Copy link
Author

Can we finally know if this is a tcpshield issue or a fastlogin issue ?

@AlexPresso
Copy link

TCPShield is working fully as intended, the problem is due to FastLogin not being able to handle the player IP change:

When a player joins the server, he has the TCPShield proxy IP, FastLogin tries to auto-login the player with that IP. When TCPShield has finished connecting the player to the server, it replaces its IP with the real player's IP (not the proxy one anymore). Then FastLogin is unable to retrieve the player in the auto-logged list while using the first player IP (the proxy one which isn't used anymore).

@cicatrice74
Copy link
Author

The problem seems to be out again on latest tcpshield 2.5.5, any suggestion how to fix it ?

@argon000s
Copy link

TCPShield-2.5.6 with FastLoginBukkit tcpshield update is now saying all players ips are now 192.168.0.1 (my router internal ip)
any ideas how to fix?

@cicatrice74
Copy link
Author

Any news about this annoying issue ? Some of us still need fastlogin/tcpshield togheter, but it seems no one can help us find a definitive solution, is it possible all of you only have Mega/Servers ?
Please help us find a definitive solution:
TcpShield (RealIp plugin) + Fastlogin , so we can have the real players' ips on our servers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants