-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Player can rejoin after ban #476
Comments
Did you correctly install AdvancedBan? Remember that it should only be installed on your Proxy when used on a network. |
Yes. It is installed on the BungeeCord server |
I am pretty sure then there has to be any error. Please check for the
following errors:
- on server start
- when banning
- when server stop
|
When I ban the player, there is no error code in the console of bungeecord or in the logs of the plugin. and the AdvancedBan logs are empty. |
It really seams like an SQL error because the tables dont even get created. And if there are no tables with entries there is no way to check for the plugin if the player is banned. I don't know whats wrong. Maybe I should clear the MySQL.Properties string in the config? |
make sure your mysql account you're accessing the database with has
required privileges to modify that database.
… |
I tested it using root and it didn't work |
What version of AdvancedBan (
/AdvancedBan
) are you using?AdvancedBan-Bundle-2.3.0-RELEASE.jar
What kind of server do you have (
Bungeecord/single server
)?Bungeecord
What server version (/version) are you using?
1-16R0.5-SNAPSHOT
Please provide the EXACT steps required to reproduce the problem...
Any error/log post it through pastebin.com and link it here. (Also include /plugins/AdvancedBan/logs/latest.log)
AdvancedBan log: --Empty--
Bungeecord startup: https://pastebin.com/7SywUR6S
Add any additional information below.
The database does not properly get setup. The database "Bans" gets created but no tables. The bungeecord log (startup) does not contain any errors.
The text was updated successfully, but these errors were encountered: