Databases

Many plugins (permissions, economy, logging, Dynmap) need a database. The Databases tab provisions one for your server without you touching a database server.

Prerequisites

• database.read to see the tab, database.create to add a database, database.rotate to rotate a password, database.delete to remove one.
• A database allocation on the server and at least one database host configured by your administrator. Without either, the tab is not shown at all.

Create a database

1. Open Databases. The header shows how many you have used, for example 2 / 3 databases used.
2. Choose a host from the Select host dropdown — each option is listed as name (host:port).
3. Type a database name (for example dynmap) and select Create.
   • The name must start with a letter and use only lowercase letters, numbers and underscores, up to 32 characters.
   • Leave it blank or shorter than three characters and the panel generates a safe name for you.
4. The Database credentials dialog opens. Copy the Host (shown as host:port), Database, Username and Password.
5. Paste them into the plugin’s config file through Files, then restart the server.

Create is disabled once you reach the allocation limit. Deleting the server also removes its database records.

Caution

The dialog warns that the password “is shown only once and cannot be displayed again.” Copy it before selecting Done — if you lose it, rotate it.

Rotate credentials

1. Select Rotate on the database.
2. The Database credentials dialog opens with a fresh password. Copy it immediately — it is shown once.
3. Update every plugin config that uses it, then restart the server and check the logs for successful connections.

Delete a database

Select Delete and confirm. The dialog warns that this permanently drops the database and its credentials.

Troubleshooting

• The tab is missing: the server has no database allocation, or no database host is available to you — ask your administrator for one.
• Plugin cannot connect: use the host and port from the credentials dialog, not localhost — the database usually runs on shared infrastructure. Then confirm the username and password and that the server was restarted after the config change.
• Access denied after rotation: one of your configs still has the old password.
• Limit reached: delete a database you no longer need, or ask your administrator to raise the per-server allocation.

Related

• Storage — where administrators configure database hosts
• Files — edit the plugin config that uses the database
• Startup & Variables — variables some plugins need