-
Notifications
You must be signed in to change notification settings - Fork 56
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
Comments
It works for me |
u have to use latest fastlogin dev, latest tcpshield 2.5, it will go asking for login on autologin and autoregister premium players too |
try without tcpshield |
itried it,
whitout tcpshield 2.5 or with tcpshield 2.4 it is all ok.
Il Lun 28 Giu 2021, 02:20 Ignacio Mencía Serna ***@***.***>
ha scritto:
… try without tcpshield
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC76P7RSOFBWOIEC2TZS4LDTU6547ANCNFSM47LTVWSA>
.
|
try resetting all your server's plugin data and worlds |
what ?! Reset server's plugin data ?! I told you if i use old tpcshield 2.4
it normally functions, i will not delete my server's data to "try" this.
Il giorno lun 28 giu 2021 alle ore 19:07 Ignacio Mencía Serna <
***@***.***> ha scritto:
… try resetting all your server's plugin data and worlds
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC76P7VV5QJUPO6QHY4OODDTVCT6LANCNFSM47LTVWSA>
.
|
contact tcpshield via email |
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 opened an issue on the FastLogin project for the same problem: games647/FastLogin#595 |
i have the same problem only with 2.5+ version |
Can we finally know if this is a tcpshield issue or a fastlogin issue ? |
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). |
The problem seems to be out again on latest tcpshield 2.5.5, any suggestion how to fix it ? |
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 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 ? |
When using latest tcpshield 2.5 and fastlogin it causes fastlogin to not autologin my players, please fix this
The text was updated successfully, but these errors were encountered: