MySQL Databases
The Databases page manages the server's MySQL databases end to end: create a database with its own user in one dialog, watch sizes and connections live, back up, optimize and repair per database, and jump into phpMyAdmin. A drift detector even spots databases created outside the panel and lets you adopt them.
Databases → MySQL Databaseshttps://YOUR-SERVER-IP:8443/databases/mysql| Database | Domain | User | Size | Tables | Actions |
|---|---|---|---|---|---|
| example_wp utf8mb4 | example.com | example_wp | 412 MB | 18 | connect · backup · optimize · delete |
Creating a database
Pick a domain first; the database name and user then build under the domain's prefix (the domain's first label, dashes turned to underscores, so example.com gives example_). The user name mirrors the database name as you type until you edit it yourself, and a generator produces a strong 16-character password. Every database is created as utf8mb4 / utf8mb4_unicode_ci, today's correct default for full Unicode including emoji.
After creation the Connection String Wizard opens automatically with ready-to-paste configuration for WordPress, Laravel, Django, Node.js and raw PHP PDO, including the server's MySQL socket path, each downloadable as the framework's config file. Passwords are never echoed into these snippets; you paste your own.
information_schema in one batched, cached query, and per-database stats runs ANALYZE TABLE first so numbers are honest right after big imports.Per-database operations
Connection reopens the wizard. Change Password rotates the database user's password. Backup dumps the database to a compressed file on the server (shown with its full path) and offers an immediate download; the dump runs with --single-transaction, so InnoDB tables are backed up consistently without locking the live site. Optimize and Repair run table by table and report OK/failed per table. The per-row phpMyAdmin button opens phpMyAdmin with the database preselected. Delete is the dangerous one: it drops the database, its user and all data, and demands typing DELETE to proceed.
The drift detector
ROOT and ADMIN see an extra card whenever reality and the panel disagree: databases that exist in MySQL but not in the panel (created by hand, by a migrated app, or by a colleague over SSH), and panel records whose database has vanished. Orphans can be adopted: pick the owning domain, and the panel registers the database, reusing the existing MySQL user when it can detect one (so wp-config.php keeps working), or minting a fresh user whose password is shown exactly once. Orphan deletion requires typing the database's exact name; system databases are refused outright.
phpMyAdmin
The big phpMyAdmin button opens the bundled phpMyAdmin. For ROOT it signs in automatically through a single-use, five-minute SSO token; other roles land on phpMyAdmin's login page and sign in with a database user. The SQL-file upload limit inside phpMyAdmin is adjustable from the MySQL Tuner page.
Access
Behind the databases license feature, with granular permission keys per operation (view, create, delete, backup, download, optimize, repair, phpMyAdmin, connection info) and drift operations gated separately for admins. Visibility follows the roles and permissions chain (users their own databases, resellers their customers', admins their chain, ROOT all), and drift operations are administrator-only. Everything is mirrored on the External API under databases:* scopes. This page manages MySQL; the panel's own PostgreSQL runs the panel itself and is not offered for customer databases here.