phpMyAdmin

"SSL Is Used with Disabled Verification" — What This Warning Means

When you connect to a MySQL or MariaDB database through DBEverywhere's phpMyAdmin, you may see a warning that says something like "SSL is used with disabled verification" or "SSL certificate verification disabled." This is normal and expected.

Your Connection IS Encrypted

The warning does not mean your connection is insecure. SSL/TLS encryption is active. Data traveling between DBEverywhere and your database is encrypted in transit, which means anyone between the two endpoints cannot read your queries or results.

What's Disabled: Certificate Hostname Verification

The part that's disabled is certificate hostname verification — the step where the client checks that the SSL certificate's hostname matches the hostname you connected to.

This is disabled because managed database providers (DigitalOcean, AWS RDS, PlanetScale, etc.) typically issue SSL certificates for internal hostnames that don't match the public hostname you use to connect. For example, your connection might use db-abc123.example.com, but the certificate was issued for an internal name like node-1.internal.provider.net.

If hostname verification were enabled, these connections would fail even though the encryption itself is working correctly.

Is This Secure?

For all practical purposes, yes. The connection is encrypted with TLS, which protects against eavesdropping and tampering. Disabling hostname verification means the client doesn't confirm the identity of the server via the certificate's Common Name — but since you're already specifying the exact host to connect to, and the connection is going over an encrypted channel, the risk is minimal.

This is the same approach used by most database clients (MySQL Workbench, DBeaver, TablePlus) when connecting to managed databases with SSL enabled.

Can I Enable Full Verification?

Not through DBEverywhere's phpMyAdmin interface. If you need strict certificate verification for compliance reasons, you would typically connect using a local MySQL client where you can specify the CA certificate file directly.