Creating and connecting to a MySQL database

Some plugins, mods, and apps store their data in a MySQL database instead of flat files — it's faster at scale and lets multiple servers share data. ServerPrism gives every server its own databases, created in a couple of clicks.

Create a database

1. Open your server and click the Databases tab.
2. Click Create Database / New Database.
3. Optionally set a name or remark so you remember what it's for (for example luckperms).
4. Confirm. The panel creates the database and a user, and shows you the connection details.

Find your connection details

After creation, the Databases tab shows everything you need to connect:

• Host — the database server address.
• Port — usually 3306.
• Database name — often prefixed, e.g. s5_luckperms.
• Username — auto-generated, e.g. u5_xxxxxxxx.
• Password — click to reveal or rotate it if needed.

Keep these safe — anyone with them can read and write your data.

Connect from a plugin or mod

Most plugins have a database or storage section in their config. Paste the details in. A typical LuckPerms config.yml looks like:

storage-method: mysql
data:
  address: HOST:3306
  database: s5_luckperms
  username: u5_xxxxxxxx
  password: 'your-password'

Save the config in the File Manager and restart the server so the plugin reconnects. Field names vary by plugin — check its own docs, but the host/port/database/username/password values are always the ones from the Databases tab.

Connect from an external tool

To browse or edit data yourself, use a client like HeidiSQL, DBeaver, or MySQL Workbench. Enter the same Host, Port, Username, Password, and Database. If external access is restricted for security, the panel's built-in database manager lets you run queries from your browser.

Common issues

• "Access denied for user": wrong username or password — copy them fresh from the Databases tab (watch for trailing spaces).
• "Unknown database": the database name is usually prefixed (e.g. s5_) — use the exact name shown in the panel, not just the remark you typed.
• "Communications link failure" / can't connect: use the Host and Port exactly as shown; don't substitute localhost.
• Plugin still uses flat files: you didn't switch its storage-method to mysql, or didn't restart after editing the config.

Tips

• One database per plugin keeps things tidy and makes backups/restores easier to reason about.
• Rotate the password from the panel if you ever pasted it somewhere public.
• Databases count toward a per-plan limit — need more, or a bigger one? Open a ticket.