TL;DR - Contabo VPS plans are some of the cheapest on the market but include zero database management tools — no cPanel, no phpMyAdmin, no web GUI. - Installing phpMyAdmin on your Contabo server creates a publicly accessible admin panel that bots will find and attack within hours. - DBEverywhere gives you a full phpMyAdmin or Adminer interface from any browser by connecting to your Contabo MySQL through a single whitelisted IP. - Configure your firewall to allow one IP on port 3306, create a remote MySQL user, and you're in. - Free tier: 5 sessions/month. Paid tier: $5/mo for unlimited sessions, saved connections, and SSH tunnels.

Table of Contents

• Why Contabo VPS has no database GUI
• The real cost of installing phpMyAdmin on Contabo
• Four ways to manage MySQL on a Contabo VPS
• Side-by-side comparison
• How to connect to your Contabo MySQL from a browser
• Configuring your Contabo VPS firewall
• Contabo-specific considerations
• FAQ

Contabo VPS Database GUI: How to Manage MySQL Without cPanel

Contabo has built a massive following among budget-conscious developers. Their VPS plans start at EUR 4.99/month for 4 vCPUs and 8 GB of RAM — specs that would cost 3-5x more on DigitalOcean, Linode, or AWS Lightsail. According to hosting review aggregators, Contabo serves over 200,000 active customers across data centers in Germany, the US, UK, Japan, Singapore, and Australia.

But there's a catch that every Contabo user discovers on day one: you get a bare Linux server and nothing else. No control panel, no Contabo database gui, no web-based management tools of any kind. If you're running MySQL or MariaDB on your Contabo VPS database, you need to figure out how to manage it yourself.

This guide covers four approaches to Contabo MySQL management, compares them honestly, and walks through the fastest way to get a full database GUI without installing anything on your server.

Why Contabo VPS has no database GUI

Contabo's business model is simple: give developers more hardware for less money by cutting everything that isn't raw compute. Their VPS S plan offers specs that compete with providers charging $40-50/month:

The trade-off for that pricing is clear: no managed services, no premium support queue, no fancy dashboard. Contabo's customer panel lets you reboot your VPS, reinstall the OS, manage reverse DNS, and view bandwidth usage. That's it. No firewall management UI (you handle that with ufw or iptables), no managed databases, no marketplace apps.

For a developer who knows their way around Linux, this is fine — until they need to browse a database table. At that point, the options are: install a GUI on the server, set up an SSH tunnel to a desktop client, or use the MySQL CLI. Most Contabo users, especially those self-hosting WordPress, Laravel, or other PHP applications, end up installing phpMyAdmin directly on the server. And that's where problems start.

The real cost of installing phpMyAdmin on Contabo

The most common Google search for Contabo database access is literally "contabo phpmyadmin install." Tutorials for this are everywhere: install Apache, install PHP, download phpMyAdmin, configure it, set up a virtual host.

Here's what those tutorials don't emphasize:

Your phpMyAdmin becomes a target immediately. Automated scanners probe every IP address on the internet for /phpmyadmin, /pma, /mysql, and similar paths. A 2023 analysis by Wordfence found that phpMyAdmin login pages receive an average of 13,000 brute-force attempts per month per exposed instance. On a Contabo VPS, which has a static IP that doesn't change, bots will catalog your phpMyAdmin URL and attack it indefinitely.

phpMyAdmin CVEs are not theoretical. The phpMyAdmin security advisories page lists over 70 CVEs since 2003, including cross-site scripting, SQL injection, and remote code execution vulnerabilities. Every unpatched phpMyAdmin instance is a potential entry point.

It consumes resources on a server that's already tight. Contabo's budget plans are generous on paper, but the actual performance (CPU priority, disk I/O) is shared. Running Apache + PHP + phpMyAdmin adds persistent memory usage (100-200 MB) and CPU overhead for every request. On a VPS that's also running your application and database, this matters.

You have to maintain it. PHP version upgrades, phpMyAdmin updates, Apache security patches, TLS certificate renewals. Every component is another thing that can break or become vulnerable. This is operational overhead that directly contradicts the reason most people choose Contabo: keeping costs and complexity low.

For the full breakdown of self-hosted phpMyAdmin risks, see our deep dive on phpMyAdmin security risks.

Four ways to manage MySQL on a Contabo VPS

1. Install phpMyAdmin on the server

The obvious choice and the most common. You get a familiar interface accessible from any browser. But you also get an attack surface, resource consumption, and ongoing maintenance. If you go this route, at minimum: put it behind HTTP basic auth, restrict access by IP in your Nginx/Apache config, and keep it updated religiously.

2. SSH tunnel + desktop client

The secure option. Open a tunnel (ssh -L 3306:localhost:3306 root@your-contabo-ip) and connect via MySQL Workbench, DBeaver, or TablePlus. Your database never touches the public internet. The downside: you need the desktop client and SSH key on every device. If you're on a tablet, a client's machine, or a public computer, this doesn't work.

3. Use the MySQL CLI

The minimalist approach. mysql -u root -p from an SSH session. Fine for SELECT queries and quick fixes. Not practical for browsing large tables, visual schema management, or exporting data. According to the 2024 Stack Overflow Developer Survey, 72% of developers prefer a GUI for database management over CLI tools.

4. Use a browser-based database gateway

Connect your Contabo MySQL to DBEverywhere through a single whitelisted IP. No software on your server, no desktop clients, full phpMyAdmin or Adminer interface from any browser. This is the approach we'll walk through.

Side-by-side comparison

For Contabo VPS database management specifically, the browser-based approach has an extra advantage: it doesn't consume resources on a server where you're already getting what you paid for in compute and nothing more.

How to connect to your Contabo MySQL from a browser

Step 1: Configure MySQL for remote connections.

SSH into your Contabo VPS and edit the MySQL configuration:

sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf

Change the bind address:

# Before
bind-address = 127.0.0.1

# After
bind-address = 0.0.0.0

Restart MySQL:

sudo systemctl restart mysql

Step 2: Create a MySQL user restricted to DBEverywhere's IP.

Don't use your root account for remote access. Create a dedicated user:

CREATE USER 'dbeverywhere'@'<DBEverywhere-IP>' IDENTIFIED BY 'a-very-strong-password-here';
GRANT ALL PRIVILEGES ON your_database.* TO 'dbeverywhere'@'<DBEverywhere-IP>';
FLUSH PRIVILEGES;

The IP is available on the DBEverywhere dashboard after signup. Restricting the MySQL user to a specific IP means even if someone obtains the credentials, they can't use them from any other address.

Step 3: Configure your firewall.

See the next section for the full walkthrough.

Step 4: Connect through DBEverywhere.

1. Go to dbeverywhere.com and create an account.
2. Click Connect.
3. Enter your Contabo VPS public IP, port 3306, the MySQL username and password you just created, and your database name.
4. You'll get a full phpMyAdmin interface — browse tables, run queries, import/export, manage users and permissions.

Credentials are used only to establish the session and are not stored unless you opt in (paid tier feature for saved connections).

If you've left shared hosting behind and miss having a GUI, you're not alone — we covered this exact transition in database management after leaving cPanel.

Configuring your Contabo VPS firewall

Contabo doesn't provide a cloud firewall through their dashboard. All firewall configuration happens at the OS level on your VPS. Most Contabo VPS instances ship with ufw (Uncomplicated Firewall) pre-installed on Ubuntu, or you'll use iptables on other distributions.

Using ufw (Ubuntu/Debian):

# Allow SSH (if not already allowed)
sudo ufw allow 22/tcp

# Allow MySQL only from DBEverywhere's static IP
sudo ufw allow from <DBEverywhere-IP> to any port 3306

# Verify the rule
sudo ufw status

Using iptables (CentOS/AlmaLinux):

# Allow MySQL from DBEverywhere's IP
sudo iptables -A INPUT -p tcp --dport 3306 -s <DBEverywhere-IP> -j ACCEPT

# Drop all other MySQL traffic
sudo iptables -A INPUT -p tcp --dport 3306 -j DROP

# Save the rules (so they persist across reboots)
sudo iptables-save > /etc/iptables/rules.v4

Critical: Do not open port 3306 to all traffic (0.0.0.0/0). Restrict it to the single DBEverywhere IP. This means your MySQL port is accessible from exactly one address in the world — the gateway that you're connecting through.

For more on why single-IP whitelisting is effective, see our guide on database IP whitelisting.

Test the connection before using DBEverywhere by running from another server (or asking a friend to try):

mysql -h your-contabo-ip -u dbeverywhere -p

This should work from the whitelisted IP and fail from any other address.

Contabo-specific considerations

There are a few things unique to Contabo that affect database management:

Network performance. Contabo's VPS plans include 32 TB of outbound traffic per month (on the VPS S plan). That's generous for a budget provider. However, Contabo's network throughput can be inconsistent during peak hours, especially at their Nuremberg and Munich data centers. For database management (which involves relatively small data transfers), this is rarely an issue. For large imports or exports (multi-GB SQL dumps), you might notice slower speeds compared to premium providers.

No built-in snapshots API. Contabo offers VPS snapshots, but they're managed through the customer panel — not via API. If you want to snapshot your server before a major database change (always a good idea), you'll need to do it manually through the Contabo panel. Plan for 2-5 minutes for a snapshot to complete depending on disk size.

IPv6 support. Contabo assigns an IPv6 address to every VPS by default. Make sure your MySQL bind address and firewall rules account for IPv6 if you're using it. The bind-address = 0.0.0.0 setting only covers IPv4. For IPv6, you'd also need bind-address = :: or configure MySQL to listen on both stacks.

Contabo's DDoS protection. Contabo includes basic DDoS mitigation on all VPS plans. However, targeted attacks on an exposed phpMyAdmin instance can still cause disruption before mitigation kicks in. Not exposing phpMyAdmin on your server eliminates this vector entirely.

SSD vs HDD plans. Contabo still offers HDD-based VPS plans alongside NVMe SSD plans. If you're running MySQL on an HDD plan (the Storage VPS line), database performance will be noticeably slower. A browser-based GUI won't fix slow disk I/O, but it will at least give you a responsive interface while queries execute — unlike the CLI, which blocks your terminal.

FAQ

Can I use DBEverywhere with MariaDB on Contabo?

Yes. MariaDB is a drop-in replacement for MySQL and uses the same protocol, same port (3306), and same connection parameters. phpMyAdmin supports both MySQL and MariaDB fully. Many Contabo users running Ubuntu or Debian have MariaDB installed by default (it replaced MySQL as the default in several distributions). The setup process is identical.

What if I'm running PostgreSQL on Contabo instead of MySQL?

DBEverywhere supports PostgreSQL through Adminer. The connection process is the same, just use port 5432 and your PostgreSQL credentials. The firewall configuration is identical — allow DBEverywhere's IP on port 5432 instead of 3306. Adminer provides table browsing, query editing, import/export, and schema management for PostgreSQL.

Is Contabo's network reliable enough for remote database access?

For interactive database management (browsing tables, running queries, editing rows), Contabo's network is more than adequate. Latency from Contabo's European data centers to most EU and US locations is typically 20-80ms, which is imperceptible in a web interface. The only scenario where network quality might matter is importing/exporting very large SQL files (hundreds of MB), where Contabo's variable throughput could extend the transfer time.

Can I use this with Contabo's Object Storage?

Contabo Object Storage is an S3-compatible storage service and has nothing to do with database management. If you're looking to store database backups, Contabo Object Storage (starting at EUR 2.49/month for 250 GB) is a reasonable destination — but you'd use mysqldump and s3cmd for that workflow, not a database GUI.

Does Contabo offer managed databases?

No. As of 2026, Contabo does not offer managed database services. Every database on Contabo is self-managed — you install it, configure it, back it up, and manage access yourself. This is unlikely to change given their business model of providing raw compute at the lowest possible price. A browser-based Contabo database gui from an external service is the most practical way to add a management layer without changing your hosting setup.

Conclusion

Contabo delivers exceptional value for raw compute. A VPS with 4 vCPUs and 8 GB RAM for under EUR 5/month is hard to beat. But that value proposition breaks down if you spend hours setting up and maintaining phpMyAdmin on the server, or if you restrict your database work to the CLI because the alternatives feel like too much effort.

DBEverywhere gives you a full Contabo database gui — phpMyAdmin for MySQL/MariaDB, Adminer for PostgreSQL — from any browser. One firewall rule, one MySQL user, two minutes of setup. Your Contabo VPS stays lean: just your application and your database, no web-accessible admin panels for bots to probe.

The free tier handles occasional database checks. The paid tier at $5/month is still less than what you'd pay for the cheapest managed database on any premium provider — and you keep your Contabo pricing advantage intact.

Try DBEverywhere free -- connect to your Contabo database in 60 seconds