After your VPS is provisioned, log into your YouStable dashboard and navigate to the VPS section. You will see your server listed with its IP address and status. Step 2: Connect to Your VPS via SSH<\/h3>\n\n\n\n Now that your VPS is ready, you need to connect to it. You do this through SSH, which is a secure way to access your server remotely from your computer. The connection gives you full command-line control over the server.<\/p>\n\n\n\n
So, how to connect from Windows? <\/strong><\/p>\n\n\n\n\nOn Windows, you can use a tool called PuTTY or the built-in Windows Terminal. I recommend the Windows Terminal since it comes pre-installed on Windows 10 and 11.<\/li>\n\n\n\n Open your Windows Terminal or Command Prompt and run this command:<\/li>\n<\/ul>\n\n\n\nssh root@YOUR_VPS_IP_ADDRESS<\/code><\/pre>\n\n\n\n\nReplace YOUR_VPS_IP_ADDRESS with the actual IP address from your YouStable welcome email. When prompted, type yes to accept the connection, then enter your root password.<\/li>\n<\/ul>\n\n\n\nOnce connected, you will see a terminal prompt that looks like: root@your-server-name:~#<\/p>\n\n\n\n
This confirms you have root access to the VPS and are ready to begin the installation.<\/p>\n\n\n\nSecurity Note<\/strong>Step 3: Update Your VPS Before Installing Anything<\/h3>\n\n\n\n Before you install PostgreSQL, update your server’s package list. <\/p>\n\n\n\n
This makes sure you get the latest available version of every package and avoids dependency issues during installation. Skipping this step is one of the most common reasons people run into errors.<\/p>\n\n\n\n
Run these two commands one after the other:<\/strong><\/p>\n\n\n\nsudo apt update<\/code><\/pre>\n\n\n\nThis command fetches the latest package information from Ubuntu’s servers. <\/p>\n\n\n\n
sudo apt upgrade -y<\/code><\/pre>\n\n\n\nThis command upgrades all installed packages to their latest versions<\/p>\n\n\n\n
The -y flag automatically confirms the upgrade without asking you each time. This process might take a few minutes depending on how many packages need updating.<\/p>\n\n\n\nYou will see a long list of packages being updated scrolling through your terminal. Wait until you see the command prompt return.Step 4: Install PostgreSQL on Your VPS<\/h3>\n\n\n\n Now comes the main part. <\/p>\n\n\n\n
You are going to install PostgreSQL using the official PostgreSQL APT repository. <\/p>\n\n\n\n
I recommend this method over the default Ubuntu repository because it gives you the latest stable version of PostgreSQL with up-to-date security patches.<\/p>\n\n\n\n
Add the Official PostgreSQL APT Repository<\/strong><\/p>\n\n\n\nRun these commands in order to add the official PostgreSQL repository to your server:<\/p>\n\n\n\n
sudo apt install -y curl ca-certificatessudo install -d \/usr\/share\/postgresql-common\/pgdgsudo curl -o \/usr\/share\/postgresql-common\/pgdg\/apt.postgresql.org.asc --fail \\https:\/\/www.postgresql.org\/media\/keys\/ACCC4CF8.asc<\/code><\/pre>\n\n\n\n Now run the automated repository setup script:<\/strong><\/p>\n\n\n\nsudo apt install -y postgresql-commonsudo \/usr\/share\/postgresql-common\/pgdg\/apt.postgresql.org.sh<\/code><\/pre>\n\n\n\nWhen this script runs, it will ask you to confirm adding the repository >> Press Enter to accept >> After it finishes, your server now has access to the official PostgreSQL packages.<\/p>\n\n\n\n
Install PostgreSQL<\/strong><\/p>\n\n\n\nNow install the latest stable version of PostgreSQL. As of 2026, PostgreSQL 17 is the current stable release:<\/p>\n\n\n\n
sudo apt updatesudo apt install -y postgresql<\/code><\/pre>\n\n\n\nPlease Note:<\/strong><\/p>\n\n\n\n\nRunning ‘sudo apt install -y postgresql<\/strong>‘ installs the latest version available in the PGDG repository.<\/li>\n\n\n\nIf you want to install a specific version like PostgreSQL 17, you can run: sudo apt install -y postgresql-17<\/strong><\/li>\n<\/ul>\n\n\n\nBoth commands work fine for this guide.<\/p>\n\n\n\n
\nYou will see PostgreSQL and its dependencies being downloaded and installed.<\/li>\n\n\n\n The installation automatically starts the PostgreSQL service when done. <\/li>\n<\/ul>\n\n\n\nStep 5: Verify That PostgreSQL Is Running<\/h3>\n\n\n\n After installation, PostgreSQL starts automatically. You need to verify that it is actually running before you move forward. A service that is installed but not running will cause confusing errors later.<\/p>\n\n\n\n
Run this command to check the status:<\/strong><\/p>\n\n\n\nsudo systemctl status postgresql<\/code><\/pre>\n\n\n\nYou should see an output that shows ‘active (running)’ in green. That means PostgreSQL is up and accepting connections.<\/p>\n\n\n\n
If you see ‘inactive’ or ‘failed’, run: sudo systemctl start postgresql<\/strong><\/p>\n\n\n\nThen check the status again.<\/p>\n\n\n\n
You can also confirm the PostgreSQL port is listening by running:<\/p>\n\n\n\n
ss -tlnp | grep 5432<\/code><\/pre>\n\n\n\nYou should see port 5432 listed, which is PostgreSQL’s default port. If you see it, the database is ready.<\/p>\n\n\n\nEnable PostgreSQL to Start Automatically on Reboot. By default, PostgreSQL should start on boot, but it is a good habit to make sure:<\/p>\n\n\n\n
sudo systemctl enable postgresql<\/code><\/pre>\n\n\n\nThis ensures PostgreSQL starts automatically every time your VPS reboots, so you never have to worry about it being down after a server restart.<\/p>\n\n\n\n
Step 6: Access the PostgreSQL Command Line<\/h3>\n\n\n\n PostgreSQL uses a special system user called ‘postgres’ that gets created automatically during installation. To access the PostgreSQL command line, you switch to this user first and then open the PostgreSQL shell.<\/p>\n\n\n\n
Switch to the PostgreSQL User. And to do that, run this command:<\/p>\n\n\n\n
sudo -i -u postgres<\/code><\/pre>\n\n\n\nYour terminal prompt will change. <\/p>\n\n\n\n
You are now operating as the postgres system user. Notice how the prompt now shows postgres@ instead of root@.<\/p>\n\n\n\n
Open the PostgreSQL Shell (psql) >> Now open the PostgreSQL interactive terminal by running:<\/p>\n\n\n\n
psql<\/code><\/pre>\n\n\n\nYou will see a prompt that looks like this:<\/strong><\/p>\n\n\n\npostgres=#<\/code><\/pre>\n\n\n\nYou are now inside PostgreSQL >> You can run database commands from here. To exit the shell at any time, type:<\/p>\n\n\n\n
\\q<\/code><\/pre>\n\n\n\nYour terminal should now show: postgres=# <\/p>\n\n\n\n
This is the psql prompt. Everything you type here is a PostgreSQL command.<\/p>\n\n\n\n
SQL commands end with a semicolon (;). psql commands start with a backslash (\\).<\/em><\/strong><\/p>\n\n\n\nStep 7: Create a New PostgreSQL Database and User<\/h3>\n\n\n\n The default postgres superuser is fine for administration, but for your actual applications, you should always create a dedicated database and a dedicated user with limited permissions. <\/p>\n\n\n\n
This is a clean way to organize your projects.<\/p>\n\n\n\n
Create a New Database<\/strong><\/p>\n\n\n\nFirst, make sure you are inside the psql shell (you should see postgres=#<\/em>). Then run:<\/p>\n\n\n\nCREATE DATABASE myappdb;<\/code><\/pre>\n\n\n\nReplace myappdb with whatever name you want for your database. You will see ‘CREATE DATABASE<\/strong>‘ in the output, which confirms it worked.<\/p>\n\n\n\nCreate a New Database User<\/strong><\/p>\n\n\n\nNow create a user that your application will use to connect to this database:<\/p>\n\n\n\nCREATE USER myappuser WITH ENCRYPTED PASSWORD ‘YourStrongPassword123!’;<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nPlease Note<\/strong>:<\/p>\n\n\n\n\nReplace ‘YourStrongPassword123!’ with a unique password.<\/li>\n\n\n\n Use a mix of letters & special characters.<\/li>\n\n\n\n Never use simple passwords like ‘123456’.<\/li>\n<\/ul>\n\n\n\nGrant Permissions to the New User<\/strong><\/p>\n\n\n\nGive your new user full access to the new database:<\/p>\n\n\n\nGRANT ALL PRIVILEGES ON DATABASE <\/strong>myappdb <\/strong>TO <\/strong>myappuser<\/strong>;<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nNow your user myappuser has full control over myappdb. This user cannot access any other database unless you explicitly grant that permission.<\/p>\n\n\n\n
Verify the Database Was Created<\/strong><\/p>\n\n\n\nTo see a list of all databases on the server, run \\l<\/strong><\/p>\n\n\n\nYou should see myappdb in the list alongside the default postgres and template databases.<\/p>\n\n\n\n
The \\l command lists all databases with their owner and encoding. You should see myappdb listed with myappuser as owner after granting privileges.<\/p>\n\n\n\n
Type \\q<\/strong> to exit psql when done. <\/p>\n\n\n\nStep 8: Configure PostgreSQL for Remote Access<\/h3>\n\n\n\n By default, PostgreSQL only accepts connections from the server itself (localhost). <\/p>\n\n\n\n
If your application runs on a different server, or if you want to connect to the database using a tool like pgAdmin from your laptop, you need to configure PostgreSQL to allow remote connections. <\/p>\n\n\n\n
Please follow these steps carefully.<\/p>\n\n\n\n
Edit the PostgreSQL Configuration File<\/strong><\/p>\n\n\n\n\nFirst, exit the psql shell if you are still inside it by running \\q. <\/li>\n\n\n\n Then go back to your root or sudo user >> Find the PostgreSQL configuration file and open it:<\/li>\n<\/ul>\n\n\n\nsudo nano \/etc\/postgresql\/*\/main\/postgresql.conf<\/code><\/pre>\n\n\n\n\nInside this file, find the line that says:<\/strong><\/li>\n<\/ul>\n\n\n\n#listen_addresses = 'localhost'<\/code><\/pre>\n\n\n\n\nChange it to:<\/strong><\/li>\n<\/ul>\n\n\n\nlisten_addresses = '*'<\/code><\/pre>\n\n\n\n\nThe asterisk (*) tells PostgreSQL to listen on all available network interfaces >> Save the file by pressing Ctrl+X, then Y, then Enter.<\/li>\n<\/ul>\n\n\n\nEdit the Client Authentication Configuration<\/strong><\/p>\n\n\n\n\nNow open the pg_hba.conf<\/em> file which controls who can connect and how:<\/li>\n<\/ul>\n\n\n\nsudo nano \/etc\/postgresql\/*\/main\/pg_hba.conf<\/code><\/pre>\n\n\n\n\nScroll to the bottom of this file and add this line:<\/li>\n<\/ul>\n\n\n\nhost all all 0.0.0.0\/0 scram-sha-256<\/code><\/pre>\n\n\n\nDisclaimer<\/strong><\/p>\n\n\n\n\nThe line above allows connections from ANY IP address. This is fine for initial setup and testing.<\/li>\n\n\n\n For a production server, replace ‘0.0.0.0\/0’ with your specific IP address.<\/li>\n\n\n\n Allowing all IPs on a production server without a firewall is a security risk.<\/li>\n<\/ul>\n\n\n\nRestart PostgreSQL to Apply Changes<\/strong><\/p>\n\n\n\nAfter editing both files, restart PostgreSQL for the changes to take effect:<\/p>\n\n\n\n
sudo systemctl restart postgresql<\/code><\/pre>\n\n\n\nThen verify it is still running:<\/strong><\/p>\n\n\n\nsudo systemctl status postgresql<\/code><\/pre>\n\n\n\nPlease note this too: <\/strong><\/p>\n\n\n\n\nAfter restart, the status should still show ‘active (running)’.<\/li>\n\n\n\n If it shows an error, check your edits in postgresql.conf and pg_hba.conf for typos. <\/li>\n<\/ul>\n\n\n\nStep 9: Configure the Firewall to Allow PostgreSQL<\/h3>\n\n\n\n Even with PostgreSQL configured to listen on all interfaces, your VPS firewall may still block incoming connections on port 5432. You need to open this port. <\/p>\n\n\n\n
On Ubuntu, the default firewall is UFW (Uncomplicated Firewall).<\/p>\n\n\n\n
Check If UFW Is Active<\/strong><\/p>\n\n\n\nsudo ufw status<\/code><\/pre>\n\n\n\nIf UFW is active and port 5432 is not listed, you need to add it. If UFW is inactive, you can skip to the next section, though I recommend enabling it at first.<\/p>\n\n\n\nAllow PostgreSQL Through the Firewall<\/strong><\/p>\n\n\n\nRun this command to allow connections on PostgreSQL’s port:<\/p>\n\n\n\n
sudo ufw allow 5432\/tcp<\/code><\/pre>\n\n\n\nFor better security, allow connections only from a specific IP address:<\/strong><\/p>\n\n\n\nsudo ufw allow from YOUR_IP_ADDRESS to any port 5432<\/code><\/pre>\n\n\n\nReplace YOUR_IP_ADDRESS with the IP of the machine you are connecting from.<\/p>\n\n\n\n
Enable UFW If It Is Not Active<\/strong><\/p>\n\n\n\nTo enable UFW and ensure SSH access is not blocked:<\/p>\n\n\n\n
sudo ufw allow OpenSSHsudo ufw enable<\/code><\/pre>\n\n\n\nPlease also make sure that:<\/strong><\/p>\n\n\n\n\nAlways allow OpenSSH before enabling UFW.<\/li>\n\n\n\n If you enable UFW without allowing SSH first, you will lock yourself out of the server.<\/li>\n\n\n\n If that happens, use the VPS emergency console in your YouStable dashboard to regain access. <\/li>\n<\/ul>\n\n\n\n
![\"YouStable](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-31.png\")
<\/a><\/figure>\n\n\n\n![\"VPS](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-32.png\")
<\/a><\/figure>\n\n\n\n![\"Operating](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-29.png\")
<\/figure>\n\n\n\n![\"Choose](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-27.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-30.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-28.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-41.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-33.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-37.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-43.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-40.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-34.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-36.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-44.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/06\/image-39.png\")
<\/figure>\n\n\n\n