Databases in ISPmanager 6: MySQL and PostgreSQL

ISPmanager 6 supports MySQL (MariaDB) and PostgreSQL. Database management is available both through the panel interface and through phpMyAdmin/phpPgAdmin.

Creating a MySQL Database

Databases → MySQL → Create.

Opening phpMyAdmin

Databases → MySQL → select a database → phpMyAdmin. phpMyAdmin will open with automatic login.

Importing / Exporting a Database

Export (create a dump)

Databases → MySQL → select a database → Backup → Create. The file will be saved in the user's home directory.

Import via SSH

# Import via mysqldump
mysql -u user1_dbuser -p user1_dbname < backup.sql

# Or via ISPmanager CLI
ispmgr db.restore base=user1_dbname src=/root/backup.sql

Managing Database Users

Databases → MySQL Users → Create. You can create a user with access to several databases or just one.

Remote Access to MySQL

By default, MySQL is only accessible locally. For remote access:

# Allow access for a specific IP in ISPmanager:
# Databases → MySQL Users → select → Edit → Host: your_IP

Creating a PostgreSQL Database

PostgreSQL is created in the same section: Databases → PostgreSQL → Create. The logic resembles MySQL, but there are differences worth knowing in advance.

You can also create a user and a database from the console if you need automation without the panel interface:

# Create a PostgreSQL user and database via the ispmgr CLI
ispmgr db.postgres.user.edit name=appuser password=YourStrongPassword
ispmgr db.postgres.edit name=user1_appdb owner=appuser

Common Database Errors

Below are the messages you're most likely to see when connecting to a database created in ISPmanager 6, and what they mean in practice.

When Panel Management Isn't Enough

The ISPmanager interface covers most everyday tasks, but it doesn't replace direct access to the database server in a few cases:

• Setting up replication or a cluster — the panel manages standalone databases on one server
• Installing specific PostgreSQL extensions (for example, PostGIS) without a ready-made package in the system
• Fine-tuning my.cnf parameters for one specific database rather than for the whole MySQL server
• Regularly exporting dumps with non-standard mysqldump flags that aren't available in the panel's backup form

In these cases, use SSH access and standard console utilities — the panel doesn't block direct work through the terminal.

Verifying the Result

After creating the database and user, confirm that the connection actually works before wiring it into your application:

# MySQL: confirm the database is visible and accessible to the user
mysql -u user1_dbuser -p -e "SHOW DATABASES;"

# PostgreSQL: list databases and owners
psql -U appuser -h 127.0.0.1 -l

# Confirm the service responds at all
mysqladmin -u user1_dbuser -p ping

If mysqladmin ping returns mysqld is alive but the database you need doesn't show up in SHOW DATABASES, check user rights first, not the network or firewall. For more on backing up these databases, see ISPmanager 6 backups and the task scheduler for regular dumps.

Backing Up Databases Separately from the Full Site Backup

A scheduled site backup in ISPmanager usually includes both files and the entire database, but for larger projects that can be overkill: a full dump of a large database takes time and space even if only one table changed. For such cases, the Databases section offers a targeted backup of a specific database on its own schedule — running more often than the full site backup, without re-exporting files that haven't changed.

Frequently asked questions

Why can't a new MySQL user see a database that already exists in the panel?

When a user gets created separately from a database, ISPmanager does not grant access automatically — the checkbox for granting rights to an existing user has to be ticked while creating the database, or rights added later through the user management section. Otherwise the connection succeeds fine, but SHOW DATABASES returns an empty list for that login.

Is it safe to open remote access to MySQL for development from a home computer?

It can be, provided a specific IP address is used instead of a range and a dedicated user is created with only the rights it needs, never root. The catch: a home IP address often changes with the provider, and the rule silently stops working. Tunneling the connection through SSH or restricting access to a work server is more reliable.

Which should a new project pick, MySQL or PostgreSQL, given the panel supports both?

The choice should follow the application's requirements, not panel convenience, since both databases are created equally easily through the interface. PostgreSQL is stronger at complex queries and strict data typing, while MySQL is more familiar for typical CMS platforms and has wider support in ready-made scripts. Migrating between them once a project is live is costly, so decide early.

Can a specific database be backed up more often than once a day?

Yes, a targeted backup for one database in the Databases section runs on its own schedule independent of the full site backup, including intervals more frequent than daily. This suits tables that change constantly, where a full backup of every file and the whole database is overkill and takes noticeably more time and disk space.