LuckPerms Bungeecord not working
draexo opened this issue ยท 5 comments
The base system is a rented dedicated server that I have installed Ubuntu 16.04 LTS and Multicraft on.
I used Multicraft to create the MySQL databases.
On 4.3.80 and 4.3.83 LuckPerms for bungee;
FYI: Everything works fine on servers, so I am assuming I am doing everything right in configuration, and I have included a redacted config farther on. The servers work, including syncing changes across servers.
It was suggested in the LuckPerms Discord channel that I open an issue here.
Here is my config: https://pastebin.com/Wr2V4AMf
(minus password and database name and user)
LuckPerms starts up fine and gives no error, however, most any command I type yields an error.
Here is the bungee server startup. Everything seems fine. ; https://pastebin.com/sRCTAD9M
If I type 'lpb info' I receive this error: https://pastebin.com/uufjrdDf
If I type 'lpb help' the command works: https://pastebin.com/BexaUWsN
If I type 'lpb listgroups' I get this error: https://pastebin.com/NXasWTKf
Seems like that Bungee isn't able to connect to the database. There also appears to be some logging output missing there?
Perhaps check the actual proxy log file to see if there's any more info
About the logs: Had to capture off of the console as it stopped recording them. I know I need to fix this. It seems about a week ago, all my servers stopped logging.
Also, for the bungee version, it seems having '#' as the first character of the password causes an issue.
I currently have the bungee version successfully connecting to a MySQL on another machine. To do that, I had to remove the '#' from the password.
The bungee will connect to the MySQl that the servers are connected to. However, it seems unable to perform any tasks. The console is clean on server startup, however, typing any commands besides lpb help (lpb info) yields and error. However, due to the logging issue, I can not provide the full logs. https://pastebin.com/6gx0HzXx
I believe this is because the databae name is '2', the user name is '2'. I can not seem to control these names (even though I created the server from scratch) because they are what Multicraft is assigning. Using a MySQL on another machine with more traditional user and database names, everything seems fine.
So, I have a work around; I will use the MySQL hosted on another machine I own where I can control the username and database name.
Okayyy, sure if that works then great. :)
It is not ideal, but it works. Again, the LuckPerms on the servers can connect to the database on the host machine with the user and database name of '2'. It is the LuckPerms Bungee that does not like that name.