Скачать или смотреть Establishing a Remote Connection to a PostgreSQL Database in a Docker Container

A step-by-step guide on how to connect remotely to a PostgreSQL database hosted in a container, covering SSH port forwarding and configuration tips for NGINX.
---
This video is based on the question https://stackoverflow.com/q/77418159/ asked by the user 'Andrey Dmitriev' ( https://stackoverflow.com/u/20599180/ ) and on the answer https://stackoverflow.com/a/77418240/ provided by the user 'igops' ( https://stackoverflow.com/u/20085654/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How do I establish a remote connection to a PostgreSQL database hosted in a container on a server with ports: 127.0.0.1:5432:5432?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Establishing a Remote Connection to a PostgreSQL Database in a Docker Container

When running applications with Docker, it’s common to host your PostgreSQL database in a container. While this setup provides many benefits, it can also lead to challenges, especially when you need to connect to your database remotely. This guide addresses a common question: How do I establish a remote connection to a PostgreSQL database hosted in a container?

Understanding the Challenge

You have a PostgreSQL database running in a Docker container with the following configuration in your server.yml file:

[[See Video to Reveal this Text or Code Snippet]]

This configuration means that the database is only accessible from localhost, making it not reachable directly from the internet. To connect to this database remotely, you will need to employ a few strategies, including using NGINX as a proxy and utilizing SSH port forwarding.

Solution Overview

To connect to your PostgreSQL database remotely, follow these steps:

Setup NGINX on the server.

Use SSH to forward a local port.

Define the correct URL to connect to the database.

Step 1: Setting Up NGINX

First, you need to configure NGINX to allow remote access:

Update your NGINX configuration file. Here’s a basic example of what your NGINX server block should look like:

[[See Video to Reveal this Text or Code Snippet]]

Replace x.x.x.x with your server's public IP address.

Make sure NGINX is installed and running. You can typically do this with:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: SSH Port Forwarding

Instead of exposing your database directly over the public internet (which can be a security risk), it's often safer to use SSH port forwarding. This allows you to create a secure tunnel from your local machine to your database on the server.

Open your terminal and execute the following command:

[[See Video to Reveal this Text or Code Snippet]]

Replace user@ your-server-ip with your actual username and the server's public IP address.

This command forwards your local port 5433 to the server's port 5432.

Step 3: Connecting via DBeaver

Now that you have set up port forwarding, you can connect to your PostgreSQL database using DBeaver or any other SQL client.

In the connection settings, use the following URL:

[[See Video to Reveal this Text or Code Snippet]]

Here, localhost refers to your local machine, and 5433 is the port you used for the SSH forwarding.

Conclusion

By following these steps, you should be able to connect to your PostgreSQL database hosted in a Docker container remotely, using a secure and efficient method. Always remember to keep security in mind by not exposing your database directly to the internet and using SSH tunneling whenever possible.

If you encounter any issues during this process, feel free to revisit each step to ensure everything is configured correctly. Happy coding!