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

How good engineering unlocks fast scaling

You're building systems and tools to help companies grow without drowning in work. This fuels your equity, career capital, and reputation.

via swizec.com RSS Feed December 9, 2025

Binance employee suspended after launching a token and promoting it with company accounts

Binance has announced that the company has suspended an employee who used the platform's official Twitter accounts to promote a memecoin they had launched. The token, called "year of the yellow fruit", pumped in price aft…

via Web3 is Going Just Great December 8, 2025

Our Overfitted Century

Cultural stagnation is because we're stuck in-distribution

via The Intrinsic Perspective December 8, 2025

Generated by openring