games647
[17:05:27 ERROR] [fastlogin]: Putting session: com.velocitypowered.proxy.connection.client.LoginInboundConnection@15bd21cf
What happened?
well so far is working but i just notice something like i think possibly is a bug:
[17:05:27 ERROR] [fastlogin]: Putting session: com.velocitypowered.proxy.connection.client.LoginInboundConnection@15bd21cf
this error appear every time a player enter to the velocity server.
i tried everything so i think its a bug
Steps to reproduce
just configure everything acordin to the guide and then join as a player you will see this error in the velocityc console
Plugin list
authme protocol lib group manager essentialsx
Configuration file
No response
Server log
[17:05:27 INFO] [fastlogin]: GameProfile Player uses a premium username [17:05:27 ERROR] [fastlogin]: Putting session: com.velocitypowered.proxy.connection.client.LoginInboundConnection@15bd21cf [17:05:27 INFO]: [initial connection] /204.76.203.35:9619 has disconnected
Plugin version
released this Apr 28 ·
Platform
Velocity
Relevance
-
[x] I tried the latest build (build refers to development builds not necessary a release version; i.e. v1.10 is out of date)
-
[x] I checked for existing tickets - If there are, please vote them with a thumbs reaction and not create new ones
It's likely that this player doesn't own the Mojang account associated with the username. Therefore, the client closes the connection if requested to perform a Minecraft authentication.
It's likely that this player doesn't own the Mojang account associated with the username. Therefore, the client closes the connection if requested to perform a Minecraft authentication.
yeah i guess, but its with my account and im premium user, so everybody can enter premium and no premiums, but those messages just appear with java players, not with gayser players i notice that. but nayways still working and still auth the premium players so i dunno why that message with only java players. also there is a lot of more errors but i guess those are bugs too since is still working fine. do you want me to atach those errors here too?
I was going to open an issue when I saw this "error".
Some more details on my end :
Way back in 1.21.4, using FastLogin + AuthMeReloaded 5.6.0, both proxy (Velocity) and servers (PaperMC) in offline mode :
- "Premium" users were automaticaly registered and logged-in with AuthMe
- "Non Premium" users in the other hand were requested to register and/or login
This was the expected behavior.
Now, I'm fully updated with Velocity 3.4.0-557 and PaperMC 1.21.10-108 and :
- Known "Premium" users, stored in both AuthMe and FastLogin DB are forced logged-in. It uses the Online "Premium" UUID.
- Unknown "Premium" users, which aren't stored in AuthMe DB, got inserted into FastLogin DB with a "null" UUID and "premium" set to 0. As such, they are requested to login and/or register. Their UUID is the equivalent "offline UUID"
- "Non Premium" users are working as usual, no changes on them.
Now, if I delete my "Known Premium account" from AuthMe and FastLogin, on the next login attempt, it'll ask me to register (with an offline UUID).
So my best guess, something has changed, either Paper or Velocity side, which handle this plugin differently, but don't know where to look at.
If you need any more info/debug/tests @TuxCoding , let me know, I'll be more than happy (as this is quite blocking on my side, messing with LuckPerms)
As I did move from one proxy to another for this specific MC server, I did redo all the config to be sure on the proxy + lobby and may have found that one of the backend was back in Online mode (frack me).
So it's working again now, even tho I still see thos "[17:44:42 ERROR] [fastlogin]: Putting session: com.velocitypowered.proxy.connection.client.LoginInboundConnection@XYZ" But in the end, that message is marked as an "error" while it's just some "standard debug" from what I see there : https://github.com/TuxCoding/FastLogin/blob/65a379c3c2ebc522325b1ff8c09de2853f0f66f7/velocity/src/main/java/com/github/games647/fastlogin/velocity/task/AsyncPremiumCheck.java#L85
It's flag as an "error" and might be more an "info" (and maybe only listed when into a "debug" mode, as this isn't really usefull in normal running state).