I can't log in to my database (Access denied)

Access denied means MySQL received a username, password, host or database name that does not match. Everything you need is on one page in the panel, and these checks cover almost every case.

1Copy, Do Not Type

• In the game panel, open your server and click Databases under MANAGEMENT.
• Every field on the card has its own copy button, and the eye icon reveals the password.
• Use those buttons rather than selecting the text by hand. A missed character or a trailing space is the single most common cause of this error.

2Check the Username, Database and Host

• Username and database name are generated for you and both start with your server number, for example u83519_YXY3Iv7LcN and s83519_example. They are never root, and the username is not your panel login.
• The Host is the IP address on the card. localhost and 127.0.0.1 point at your own game server, where no MySQL is running, and give a connection refused error instead.
• Every database has its own username. Credentials from another database, or from an old server, do not work.

3Lost the Password

• Press Reset password on the card to generate a new one. The old password stops working immediately.
• Update it everywhere afterwards: the Database section of the server.cfg Editor and any tool you saved it in.

4Let phpMyAdmin Log You In

• Press Open in phpMyAdmin at the bottom of the card. The panel signs you in for that database, so there is no username, password or server to choose.
• Browsing to phpMyAdmin yourself and filling in the login form is what usually produces an access denied screen.

5External Tools

• HeidiSQL, DBeaver and MySQL Workbench connect with the Host, Port, Username and Password from the card. See the HeidiSQL guide for the exact fields.
• Databases are reachable from anywhere by default. If your card shows a Restricted label, connections are limited to one address; open a ticket if you did not ask for that.

Finished

Working through these five points solves it in nearly every case. If MySQL still refuses you, open a ticket with the exact error message and the name of the database, and we will check the account from our side.