Open igorzid opened 4 years ago
This feature doesn't work well anymore, i ended using sessions with mysql
I can confirm, same issue here. Any fixes or workarounds?
Please fix this :/
preserve sessions as a quick, dirty, and imperfect alternative.
AuthMe 6 will have a completely different way of determining if the user is logged in or not, so this will be fixed there. We can't ditch stuff in the current codebase. I'm sorry you would wait indefijnitely for this to be fixed
Can´t you simply run authmebungee on the bungeeproxy side?
Please let me know if the issue is now fixed
@MithrandirCraft bump
Doesn't seem to be working for me right now. I posted it did some time ago here, but then deleted comment since I was actually seeing session preservation (which I'd somehow not disabled).
Just to be clear, it's only a matter of setting autologin: true on AuthmeBungee's config to get this to work. Correct?
For now I'll just try to update Authme again on all servers, but I'm quite certain I already did this 15~ days ago.
When i login on our first server "survival" and i teleport to second server "skyblock" it wants sometiems login again, when i log in, it says to me that i am already logged, but i cant move i can only use jump for moving so i have to reconnect the server to be able to move properly on the server.
When i log in server "skyblock" and i teleport to "survival" i have to always log in again. When i login server "skyblock" or "survival" and i teleport to our third server "hard" i have to always login again aswell.
Its just weird that sometimes i dont need to login again when i teleport to "skyblock server" but i have to login always again when i teleport to the servers "survival" and "hard".
I have autologin set to true in config on bungeecord server. We are using MYSQL. We have the latest build 2402 on spigot servers and the latest build 158 on bungeecord server.
digors config_bungee.txt config_hard.txt config_skyblock.txt config_survival.txt