TLS modes, CA & client certificates

functional

Choose how PostgreSQL, MySQL, ClickHouse, libSQL and Redis connections encrypt and verify, with your own CA, client certificates, or the OS trust store.

Choose exactly how a PostgreSQL, MySQL, ClickHouse, libSQL / Turso, or Redis connection verifies the server. The four-way TLS mode dropdown replaces the old two checkboxes: Disable connects in plaintext, Require encrypts without verifying the server's certificate, Verify CA checks the certificate chain but not the hostname, and Verify full checks both.

Your own CA, and mutual TLS

Servers signed by a private or cloud CA - RDS, Cloud SQL, Azure, or your company's own, verify cleanly when you point the connection at your CA file (PEM) instead of trusting every certificate. Hardened servers that demand mutual TLS can present a client certificate and its key.

  • Browse buttons in the connection editor set the CA file, client certificate, and client key.
  • Files stay on disk - only their paths are saved with the connection, and paths are what exported connections carry too.
  • Connection strings work - pasted strings are read for sslmode, sslrootcert, sslcert, sslkey, sslnegotiation, and the MySQL ssl-mode / ssl-ca / ssl-cert / ssl-key spellings.

Direct TLS on PostgreSQL 17

PostgreSQL 17 can start an encrypted connection straight away, the way a web browser does, instead of first asking the server whether it speaks TLS. That lets a standard TLS proxy such as Caddy or Traefik route several databases on one port by host name and reuse your site's certificate. Pick any TLS mode other than Disable and tick Direct TLS (PostgreSQL 17+); a pasted connection string with sslnegotiation=direct ticks it for you, and Open in Terminal passes it on to psql. Leave it off for older servers, which refuse the handshake (the error says so).

MySQL accounts that sign in with PAM or LDAP

Some MySQL accounts ask for the password as plain text. SQLly sends it only when the TLS mode verifies the server's certificate, Verify CA or Verify full, the default, so it always travels encrypted to a server you have checked. With Disable or Require the request is refused, and the error names the setting to change. AWS and Google Cloud IAM sign-in always uses TLS.

Which certificates Redis trusts

In Verify CA and Verify full, a Redis connection checks the server against the public certificate authorities built into SQLly - the same list on every machine. A CA file adds your own CA to that list, so a server signed by your CA verifies and servers with public certificates still do.

When your company's CA is already installed on your computer, in the macOS keychain, the Windows certificate store, or the Linux CA bundle, tick Also trust the OS keychain roots under the TLS fields, and the connection trusts your machine's store too, so it verifies without a CA file. With a CA file as well, the built-in list, the CA file and your machine's store are all trusted. The option never loosens anything: if the store cannot be read, the built-in list stays in force, and a certificate nobody trusts is still refused.

  • Pasting a rediss:// URL turns TLS on as Require (the URL says "encrypted", not "verified"), and never lowers a connection that already uses Verify CA or Verify full. A redis:// URL means plaintext.
  • Test Connection shows the handshake - the TLS version, cipher, the server name sent, how many certificates the server presented, and whether the chain verifies against what you trust, even in Require mode. See Connection diagnostics.
HTTP engines switch to HTTPS. On ClickHouse and libSQL any mode other than Disable turns the connection into HTTPS (ClickHouse's port becomes 8443), and a Turso host is always HTTPS whatever you pick. On Redis the mode is what rediss:// means; Amazon ElastiCache with in-transit encryption needs Require or Verify full, and Amazon MemoryDB always requires TLS. SQL Server keeps its own encrypt / trust-certificate settings, and SQLite, DuckDB and Oracle have no TLS dropdown - Oracle's TCPS goes in a connect descriptor in the Server field.
Unencrypted keys only. A passphrase-protected key is refused with a clear message rather than a mysterious handshake failure, export an unencrypted PEM copy for SQLly to use.