Remote MySQL
Remote MySQL manages the access host list: which machines, besides the server itself, are allowed to authenticate against MySQL. Add your office IP, a subnet, or a hostname pattern, and the panel extends database-user grants to cover connections from there.
Databases → Remote MySQLhttps://YOUR-SERVER-IP:8443/databases/remoteHow hosts work
A host entry can be a single IP (203.0.113.7), a subnet wildcard (192.168.1.%), a hostname pattern (%.example.com), or % for anywhere, which the page warns you about. Each entry carries a description and a status, and deletion requires typing DELETE because it revokes real access.
user@host pair, so "allowing a host" means creating host-specific variants of your database users. When you add a host, the panel walks the database users provisioned with your domains' databases and creates a matching user@newhost with the same role-based grants, using the securely stored credentials, so the same username and password work from the new location. Removing the host drops those user@host variants again. Disabled entries are skipped when new database users are created.%, and for one-off administration consider an SSH tunnel instead, which needs no remote access at all: ssh -L 3306:localhost:3306 you@server makes the remote database feel local, with SSH doing the authentication.Access
Behind the databases license feature with its own permission keys (view, create, edit, delete). ROOT and ADMIN manage server-wide entries (owner-less, applying to everyone); resellers and users manage only entries scoped to themselves. See roles and permissions. Host values are immutable after creation (delete and re-add to change one), and the examples panel on the page documents the accepted patterns.