Connect IONOS Cloud PostgreSQL from a Desktop GUI (NLB + ISRG Root X1 + verify-full)
Connect IONOS Cloud PostgreSQL from a laptop GUI: put a Network Load Balancer in front of the private LAN, use the cluster DNS name with sslmode=verify-full and Let's Encrypt ISRG Root X1, and skip the default postgres database on v2—with HiDataLinker, a free local-first PostgreSQL desktop client.
An IONOS Cloud PostgreSQL cluster lives on a private LAN in your Virtual Data Center. A laptop cannot reach it until you put a Network Load Balancer in front of it. sslmode=verify-full also fails unless you attach Let's Encrypt ISRG Root X1 and connect by the cluster DNS name, not the raw NLB IP. On current v2 clusters, the default postgres database is denied. This guide walks an IONOS PostgreSQL desktop GUI path with HiDataLinker, a free MIT PostgreSQL and MySQL desktop client: local-first credentials, URL paste, Dump / same-engine migrate, and no seat or tab freemium wall.
IONOS CLOUD is a third-party service; this guide is not affiliated with IONOS.
1. Reach the private cluster (IONOS NLB PostgreSQL 5432)
IONOS does not publish a public hostname you can type into a GUI from home. In the Data Center Designer, the official laptop path is a TCP Network Load Balancer: reserve a public IPv4, listen on 5432, and forward to the cluster's private IP on 5432, with Proxy Protocol set to none. Set this up in the IONOS DCD (or Terraform)—HiDataLinker does not create the NLB or VDC for you. From a jump host or VPN already on that LAN, skip the NLB and use the private address directly.
If you enabled IONOS's managed pgbouncer, official examples use port 6432 instead of 5432. Forward the same port you will type into the client, then verify with nc -vz <NLB_PUBLIC_IP> 5432.
2. Download ISRG Root X1
All client connections are TLS. IONOS's default SSL mode is prefer, and clients cannot turn TLS off. Server certificates are issued by Let's Encrypt for the cluster DNS name (dnsName), which looks like pg-abc123.postgresql.de-txl.ionos.com. For verify-ca or verify-full, make IONOS PostgreSQL ISRG Root X1 available to the client. Official IONOS examples use:
curl https://crt.sh/?q=9314791 > ca.crt
3. sslmode=verify-full against the cluster DNS name
| Mode | Encrypted | Verifies cert | Verifies hostname |
|---|---|---|---|
require |
Yes | No* | No |
verify-ca |
Yes | Yes | No |
verify-full (attach ISRG Root X1) |
Yes | Yes | Yes |
*With libpq, a CA in the default path can make require act like verify-ca—set sslmode=verify-full for hostname checks.
postgresql://USER:PASSWORD@pg-abc123.postgresql.de-txl.ionos.com:5432/APP_DB?sslmode=verify-full&sslrootcert=/path/to/ca.crt
Use the exact cluster dnsName as the host. verify-full fails if you paste only the NLB public IP, because the certificate is issued for that DNS name. If the name does not resolve to the NLB from your laptop, keep the DNS name as the host and point traffic at the NLB IP with a hosts entry or a hostaddr= query parameter. Percent-encode passwords. IONOS also requires SCRAM-SHA-256; there is no TLS-off workaround.
4. Use your v2 database name, not postgres
IONOS has decommissioned PostgreSQL v1 (the DBaaS API generation, not the engine version). On v2 clusters, connecting to the default postgres database is denied. Use the database name and user you set when you provisioned the cluster.
5. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app (see the download page for OS builds).
- Open New Connection → paste the URI (keep TLS on; do not strip
sslmode,sslrootcert, or the cluster DNS name). - Test, then connect. Profiles stay on your machine—local-first, no hosted workspace.
- Browse schemas, run SQL, and use Dump (
.sql) or same-engine migrate to clone connections.
Source: github.com/henrybit/HiDataLinker · Overview: /db-client
HiDataLinker is a thin Tauri desktop app for PostgreSQL and MySQL—paste DATABASE_URL, keep creds local, and avoid seat / connection / tab freemium walls. Honest v1: MySQL + PostgreSQL as marketed; not an IONOS DCD, NLB/VDC manager, or MariaDB client.
Common failures (and the fix)
- Timeout, no clear auth error — No NLB (or VPN) path, wrong target IP/port, or you used the private address from a public network.
certificate verify failed/ missing root cert — You skipped ISRG Root X1 or usedverify-fullwithoutsslrootcert.- verify-full fails after “it worked with require” — You connected by NLB IP; use the exact cluster DNS name.
- Permission denied on
postgres— This is a v2 cluster; connect to the database name you provisioned. - Auth failure / wrong port — Re-copy the cluster user and password (SCRAM-SHA-256). If the managed pooler is on, official examples use 6432, not 5432.
Soft next step
Need an IONOS PostgreSQL desktop GUI that pastes the URI, uses the cluster DNS name with sslmode=verify-full and ISRG Root X1, and stays local-first?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker
The same TLS-and-allowlist pattern shows up on OVHcloud Databases and Amazon RDS. Reach the endpoint, attach the CA, then query from a free MIT client.