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

A massive Easter sale and a preview of my next book (out late 2026)

Easter 2026 Bundle And a preview of The Magic Toy FactoryWhy the software you make and use sucks. Get The Ebook bundle for €49 EUR, discounted from €134 (price includes VAT, where applicable) It doesn’t seem to matter what process or method you use, whateve…

via Baldur Bjarnason's Notes on the Web March 31, 2026

Hubbub Pro 2.29.1 (bug fixes) out the door.

via Colin Devroe March 31, 2026

Issue 103 – The President’s Council of Podcasters

Coinbase is accused of holding the cryptocurrency industry hostage over stablecoin rewards, prediction markets face an onslaught of opposition, and a Stand With Crypto poll can’t even get enthusiasm from its own activists

via Citation Needed March 31, 2026

Generated by openring