Failed to validate connection.
Closed this issue ยท 10 comments
Most likely an issue with either your login cridentials being wrong or the settings in LP/MySQL not being setup properly.
Whatever it is, it not really is an issue caused by LP itself.
@Andre601 Well, I checked my settings, they seem good to me. So how exactly is this not a LP problem? You didn't give an explanation...
It doesn't need to be a fault on LPs side, since a missconfiguration on your MySQL database (for example a too short lifetime for connections) can cause that too.
And the error clearly states, that LP tries to connect on an already closed connection, which means that either the setting in the config of LP or the one in MySQL is set wrong.
I already linked the page about common errors in storage systems and yours could be one of 2 listed errors.
Ok, wasn't saying it "had" to be LP's fault, I just needed a better explanation, thank you, I will speak with my host.
@Andre601 Edit: Sorry, I also did not see that you gave a link until I got home on my PC, wasn't obvious on my phone. :(
It was literally because I was missing :3306 on the address, the config file states that can be omitted, this description needs to be updated based on my experience.
Edit: Take it back, problem still exists.
May be fixed by 2cf919a
Are those errors showing on startup, or just periodically whilst the server is running?
While server is running, I have increased max connections and idle connections, no errors yet, will report back.
I had set vault-unsafe-lookups: true (I didn't really want to, but it was the recommendation of all the errors by LuckPerms spit out below. I did some more reading about those errors and it seems the LuckPerms devs all agree it is the cause of other plugins. This likely caused the errors I was getting above. Can you help me to know who I should be contacting? WorldGuard? Citizens? So many different plugins are listed below I'm not sure which ones I should be approaching. Thanks!
Edit: This is with default config using h2 database (and MySQL does the same thing).
Worldguard seems to be the culprit, removing it solves all my console Error spam. I will pursue that path for now. Thanks.