When you run pgcli on a remote database and nothing happens, the first question should be simple: what port is listening? PostgreSQL defaults to 5432. But many deployments—especially those behind gateways, proxies, and managed environments—run PostgreSQL over 8443. This isn’t a guess. It’s a deliberate choice to route secure database traffic through an HTTPS-friendly port.
pgcli is a modern command-line client for Postgres with autocomplete and syntax highlighting. It’s fast, clear, and efficient. If you’re connecting to a remote instance on 8443, you must explicitly tell pgcli to connect there. Example:
pgcli -h your-db-host.com -p 8443 -U dbuser -d dbname
If SSL is required, add:
pgcli "postgresqls://dbuser:password@your-db-host.com:8443/dbname"
When you hit connection errors, check firewall rules. Many cloud firewalls block 8443 by default. Verify that the port is open inbound and outbound. Ensure the database service itself is configured to listen on 8443. On managed platforms, this may be handled at the proxy layer, meaning your database is “always on 8443” whether you see it or not.
There are security implications. Port 8443 is often associated with HTTPS, so databases on this port typically require SSL/TLS. Make sure pgcli is built with SSL support. Always verify the certificate chain; a bad cert will either break your connection or silently downgrade security if your client is misconfigured.
Performance-wise, pgcli over 8443 is no different from 5432—unless there’s a proxy with rate limits, deep packet inspection, or session timeouts. Long-lived transactions may drop if the proxy is tuned for short HTTP sessions. In those setups, keep commits small and quick.
The key steps to a successful 8443 pgcli connection:
- Know your endpoint. Managed services document the port in their connection info.
- Set the port explicitly. Never assume the default.
- Test with
psql too. Confirms it’s not a client-specific issue. - Check SSL/TLS settings. For compliance and security.
- Verify network access. Port open both ways with correct rules.
Getting pgcli on port 8443 working is often the final blocker before you can truly see and control your data in real-time. There’s no reason to fight your environment or guess. The whole setup can be live in minutes if you use platforms designed to remove that friction.
If you want to see how fast a secure 8443 Postgres connection can really go, set it up now on hoop.dev and watch it run live almost instantly.