1.13.1 Bungeecord/server weird problem
Kryniowesegryderiusz opened this issue ยท 3 comments
Hi, I have a little weird situation with disconecting players from server while joining. It reqires short explanation.
I have 3 servers - Bungeecord (1.13.1), Lobby, Skyblock (1.13.1). Everything has LP 4.3.7.
I have conneted them via bungeecord channel and I have one mysql database for all.
When I'm connecting from Lobby to Skyblock it loggs me to server for a while and dropps out to Lobby again with saing that server I was before shutted down (what didnt happened). When I disable bungeecord in spigot.yml on Skyblock and join directly, without bungeecord it works properly, so its weird. So I thought that was something with my bunge. I tried to disable all permissions on my nick - then I could join server normally via bungee. Next, i changed all permissions from 'global' to 'skyblock', so there is no global and its working now. But sometimes, when i try to join in it dropps me out, and i can join normally on next try. The other thing is, when i try to reload NameTagEdit plugin in game it dropps all players out with 'Unable to pass event
Its so strange, so I literally dont know, what can i do in that case. Especially that there were NO errors in logs on any server. I'm so helpless now, so Im writing here - maybe you have any idea what can be problematic.
Thank you. I was wondering, when it kicks player, but i couldnt find it. I think it could be problem with UUIDs, because im using offline online-mode and FastLogin (which is perhaps changing UUIDs)
Only thing I can think of is a not properly setup IP-forwarding for bungeecord.
To my knowledge (so don't count on it) does LP kick a player:
- when the database couldn't be loaded (would give an own kick-reason)
- when his UUID isn't the same as the one saved. (Don't count me on that. I never had that so idk if LP really does that or not)
I recommend you, to check if IP-forwarding is properly setup since this is the only thing I can think of, that would cause such issues.
I could also be a 1.13 bug but idk.