Many plugins and mods need a MySQL database to store their data, and you can create one in under a minute from the Databases tab without installing anything.
MySQL is a database (an organised place to store information like player stats, economy balances or web-map data). Some plugins keep everything in flat files and need nothing from you. Others ask for database connection details in their config, and that is when this guide comes in.
Creating a database
- Open your server in the control panel and go to the Databases tab.
- Choose to create a new database. The panel handles the setup for you.
- Optionally set which hosts may connect. Leaving this as % allows connections from anywhere, which is the flexible default. If you know only this server will connect, you can leave it as is.
- Confirm, and the panel generates the database instantly.
The details you get back
Once created, the panel shows everything a plugin needs to connect. You will see:
- Host (also called the endpoint or address of the database server).
- Port, commonly 3306 for MySQL, shown next to the host.
- Database name, which the panel assigns.
- Username, also assigned by the panel.
- Password, which you can reveal and copy, and regenerate later if you need to.
Keep these somewhere safe. The password in particular is a credential, so treat it like one.
Plugging it into a plugin
Most plugins have a config file (often config.yml, database.yml or similar) with a database section. Open it on the Files tab and fill in the fields with the values from the Databases tab. A typical section looks like this:
```
database:
host: your-host-address
port: 3306
name: s123_yourdb
username: u123_xxxxxxxx
password: your-password
```
Match each line to the matching value in the panel, save the file, and restart the server so the plugin picks up the new settings. Watch the Console as it boots; a plugin that connects successfully usually says so in the log, and one that fails usually prints exactly what it could not reach.
Common mistakes to avoid
- Copying the wrong field. The username and database name look similar because both are prefixed by the panel. Copy each into its own line carefully.
- A stray space in the password. Paste cleanly, with no leading or trailing space, or the connection will be refused.
- Editing while the server runs. Change the config, then restart, so the file is not being read as you save it.
- Wrong port. Use the port shown in the panel; it is usually 3306 but always confirm.
Managing databases later
Back on the Databases tab you can rotate the password at any time (update the plugin config afterwards) or delete a database you no longer need. Deleting one removes its data permanently, so only remove databases you are sure are unused. As always, a snapshot on the Backups tab before big changes gives you a way back.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.