LuckPerms

LuckPerms

41.4k Downloads

permissions data for your user was not loaded during the pre-login stage - unable to continue. Please try again later. If you are a server admin, please check the console for any errors.

Sno0pyD0g opened this issue ยท 1 comments

commented

Description

Hello, I dont know how to fix this issue im having right now can you help me with this and this is my latest log

https://pastes.dev/kHQdK5fze4

and this is my plugins
image

Reproduction Steps

I just want to fix the luckperms error for the new player to join my server

Expected Behaviour

all the new players can't join due to the permission data for your user was not loaded

Server Details

Paper 1.18

LuckPerms Version

5.4.2

Logs and Configs

No response

Extra Details

No response

commented

successful login:

[04:51:14] [Geyser Spigot connection thread-4-3/INFO]: [LuckPerms] Processing pre-login for 00000000-0000-0000-0009-01f99775985d - .Skeletonmod6164
[04:51:14] [Geyser Spigot connection thread-4-3/INFO]: UUID of player .Skeletonmod6164 is 00000000-0000-0000-0009-01f99775985d
[04:51:14] [Server thread/INFO]: [LuckPerms] Processing login for 00000000-0000-0000-0009-01f99775985d - .Skeletonmod6164
[04:51:14] [Server thread/INFO]: [floodgate] Floodgate player logged in as .Skeletonmod6164 joined (UUID: 00000000-0000-0000-0009-01f99775985d)

unsuccessful login:

[04:51:14] [Geyser Spigot connection thread-4-4/INFO]: [LuckPerms] Processing pre-login for 00000000-0000-0000-0009-01f5323fc1e9 - .CrazzySheep21
[04:51:14] [Geyser Spigot connection thread-4-4/INFO]: UUID of player .CrazzySheep21 is b49318d7-29f1-3d6b-92aa-e41e2de97363
[04:51:14] [Server thread/INFO]: [LuckPerms] Processing login for b49318d7-29f1-3d6b-92aa-e41e2de97363 - .CrazzySheep21
[04:51:14] [Server thread/WARN]: [LuckPerms] User b49318d7-29f1-3d6b-92aa-e41e2de97363 - .CrazzySheep21 doesn't have data pre-loaded, they have never been processed during pre-login in this session. - denying login.

^ taken from your logs. You can see that the unsuccessful login failed because the players unique ID changed between the pre-login event and the login event. Seems like it could be a (configuration?) issue with either geyser or floodgate. You should ask there for help. :)