Tunnel to Production PostgreSQL Database

| databases | devops |

As any responsible sys admin, I only allow local connections to my production database server. This means that if I need to access my DB from my local machine I would most likely need to use an SSH tunnel in order to connect.

For some reason, pgadmin3 no longer seems happy on Ubuntu 16.04 LTS and I am not able to make an SSH tunnel. In addition, it is a bit annoying that you are not able to save passwords with an SSH tunnel by default in pgadmin3, especially since my password is a long and random 50 character string.

The solution is pretty simple using the -L SSH flag.

ssh -L 15432:localhost:5432 $USER@$SERVER

This command creates a tunnel on my  production server, and forwards port 5432 (the default PostgreSQL port) to my local port 15432. This allows me to connect using pgadmin3 as if the database were running on my local machine.

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

6,000 curl stickers

I am heading to FOSDEM again at the end of January. I go there every year and I have learned that there is a really sticker-happy audience there. The last few times I have been there, I have given away several thousands of curl stickers. As I realized I d…

via daniel.haxx.se January 6, 2026

Pluralistic: Code is a liability (not an asset) (06 Jan 2026)

Today's links Code is a liability (not an asset): AI psychosis, tech boss edition. Hey look at this: Delights to delectate. Object permanence: Coldplay CD DRM; Star Wars Wars; Digital manorialism vs neofeudalism; Transvaginal foetal sonic bombardment:…

via Pluralistic: Daily links from Cory Doctorow January 6, 2026

KVM migration from intel to AMD fails with missing cmp_legacy feature (+ solution)

Context I'm running a virtualisation lab environment, with four Intel-based CPUs (i5-6500) and one AMD Ryzen 3 PRO 2200GE. When migrating virtual machines from one of the Intel hosts to the AMD host, the migration would fail with the following error: er…

via Louwrentius January 6, 2026

Generated by openring