SQL Database Connection Issues about totaleconomy

[ericgrandt]

This one should work, not sure why it isn't:

database {
    enable=true
    password="mypassword"
    url="mysql://158.69.121.39:3306/s2_TotalEconomy"
    user="u2_w1us4b8NrX"
}

Could it potentially not allow connections to the database from wherever you're running the server from? Also, could you send me the full log file?

Also this issue may be related to what you're going through: #327. MySQL issues have been fixed in the past by downgrading the version. At the time this issue was created, a downgrade from MySQL8 to MySQL 5 fixed it.

By the way, I removed the link to your gist as I believe one of the url's still contained a password, so please check that out.

[itzrobotix]

I have other plugins hooked into other SQL Databases just fine and also thanks for removing the link, the password will be changed now but I must have missed that one. Is it at all possible, there was an ‘@‘ in the password. Could that cause issues with the url?
The only error it gives is to check the credentials which I can see is the message thrown from the UncheckedExecutionException. So I can only assume it’s an issue with my credentials and the only possible thing anyone has been able to suggest is the fact there was an @ in the previous password. Haven’t tried it without yet but plan to on next server restart, could this be the issue?

Thanks for your quick response by the way!

[itzrobotix]

UPDATE: The password having an "@" symbol in it was causing the connection issue, it managed to connect to the database but now it's having another issue that's kind of related.
Seems it's unable to create the tables in the database or something, here is the stacktrace;
https://pastebin.com/Tt89k62S
Any idea what is causing this issue? @Erigitic

EDIT: I also found this stacktrace; https://pastebin.com/303nhHGj
Seems creating the table when a player joins then causes an issue and I'm not sure why.

FINAL EDIT: Both issues fixed. The first issue was resolved by removing the "@" from the database password. The second issue was caused by one of our currency names containing a space.

[ericgrandt]

I'll take note of the issue with the @ in the password. I'm sure the way the password is being passed into the connection string is incorrect in the code itself, and should be an easy fix.