Connect STACKIT PostgreSQL Flex from a Desktop GUI (ACL + TLS 1.3)
Connect STACKIT PostgreSQL Flex from a laptop GUI: add your IPv4 to the instance ACL, copy the user Hostname, Port, and connection string, keep TLS on (officially always TLS 1.3), and paste into HiDataLinker, a free local-first PostgreSQL desktop client.
STACKIT PostgreSQL Flex is managed PostgreSQL on the German / Austrian STACKIT cloud. A laptop GUI times out until your public IPv4 is in the instance ACL, and TLS cannot be turned off (officially always TLS 1.3). This guide shows how to connect STACKIT Postgres from a desktop GUI 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.
STACKIT is a third-party service; this guide is not affiliated with STACKIT.
1. Add your laptop IPv4 to the instance ACL
In the STACKIT Portal, open PostgreSQL Flex (or Databases > PostgreSQL Flex), select the instance, and add an ACL entry. Official getting-started docs: look up the machine’s public IPv4 at 1.1.1.1/cdn-cgi/trace, copy the ip value, append /32, and click Add ACL IP. Without that entry, you cannot connect from that client.
The predefined ranges 193.148.160.0/19 and 45.129.40.0/21 only cover STACKIT cloud services, not a home or office laptop. A single host uses /32. IPv6 cannot be added. Do not set 0.0.0.0/0. If your public IP changes (ISP, VPN, travel), update the ACL. HiDataLinker does not edit STACKIT ACLs—do this in the Portal, and wait until the instance is Active. See create and manage instances.
2. Copy the user connection string, Hostname, and Port
Open Users → Create user. Give a username and the roles CreateDB and Login—there is no default admin or postgres user. Immediately copy the Connection string, Username, and Password; official docs say you can’t retrieve them again. Click Done, then select the user and copy Hostname and Port as well.
Official examples look like <instance-id>.postgresql.eu01.onstackit.cloud on port 5432. The FAQ says you currently cannot change the port—still copy the live values, and do not invent a hostname for another region.
Then Databases → Create Database, pick a name (getting started uses crm), and set the new user as owner. If you paste the copied connection string, you may need to replace the database name at the end. Official CLI samples often end in /stackit—do not assume stackit or postgres is a database you can query. Use the database you created.
When composing a URI for a laptop client, add sslmode=require (the official user-create string often omits it):
postgresql://USER:PASSWORD@<INSTANCE-ID>.postgresql.eu01.onstackit.cloud:5432/YOUR_DB?sslmode=require
See create and manage users and connect to PostgreSQL Flex. Password reset is via the API today.
3. TLS 1.3 is always on (no CA file to download)
The official FAQ: connections are always encrypted with TLS 1.3 and signed certificates. Unencrypted access is not possible. Do not strip TLS just to “get connected,” and do not look for a STACKIT CA bundle—there isn’t an official one.
Official pgAdmin 4 steps fill the Connection tab and leave everything else untouched (no SSL tab). Official compose-your-own URIs have no sslmode. For a desktop client, append sslmode=require (the wording used in STACKIT’s Kubernetes/SKE guide). Use verify-full only if the client verifies the hostname against a known CA in the OS trust store, and connect by the user-entry Hostname, not a raw IP. Otherwise stay on require. There is no current official PgBouncer or pooler; use the Hostname and Port from the user entry for browse, SQL, or Dump.
4. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app.
- Open New Connection → paste the URI (keep
sslmode=require; use the database you created) or fill host, port, user, password, and database. Percent-encode special characters in the password. See paste a DATABASE_URL. - Test, then connect. Profiles stay on your machine—local-first, no hosted workspace.
- Browse schemas, run SQL, and use Dump (
.sql) or same-engine PostgreSQL → PostgreSQL migrate on that direct connection.
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 the STACKIT Portal, not an ACL editor, and not a MariaDB, MongoDB, or Redis client.
Common failures (and the fix)
- Timeout, no clear auth error — The laptop (or current VPN) IPv4 is missing from the ACL, you used IPv6, or the public IP changed. Add
x.x.x.x/32. Do not “fix” this with0.0.0.0/0. - Auth failure / missing password — The password is shown only at user creation and cannot be retrieved. Create a new user, or reset via the API. Percent-encode special characters in the URI.
- Unknown database — You cannot assume
postgresor/stackit. Create a database in the Portal and put that name in the client or URI. - SSL errors — TLS cannot be turned off. Add
sslmode=requireif the client tried a non-SSL startup. Do not hunt for a STACKIT CA download. Ifverify-fullfails afterrequireworked, use the full Hostname (not a raw IP) and the OS trust store, or stay onrequire. - Wrong host — Copy Hostname from the user entry (
*.postgresql.eu01.onstackit.cloudin official examples), not an instance display name.
Soft next step
Need a STACKIT PostgreSQL Flex desktop GUI that pastes the Portal connection string, keeps TLS 1.3 / sslmode=require, and stays local-first?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker
The same “reach the endpoint, then query from a free MIT client” pattern shows up on IONOS Cloud PostgreSQL (private LAN + NLB + ISRG Root X1) and OVHcloud Databases (authorised IPs + a project CA).