How to Find Your PostgreSQL Database Credentials
Locating connection details for your PostgreSQL database based on common setups.
What You'll Need:
- Hostname (or Server Address): Server address (e.g., IP, domain name).
- Port: Network port (default: 5432).
- Database Name: The specific database to connect to.
- Username (or Role): The user account/role with database access.
- Password: The password for the specified Username/Role.
Where to Look Based on Your Setup:
Cloud Database Service
(e.g., AWS RDS, Google Cloud SQL, Azure, Heroku Postgres, DigitalOcean)
- Log in to your cloud provider's dashboard (AWS, GCP, Azure, Heroku, DO).
- Find the database service section and locate your PostgreSQL instance/add-on.
- Look for "Connection Info," "Credentials," "Endpoints," "Connectivity."
- You'll find the Hostname, Port, Database Name, and Username ("Master Username", etc.).
- The Password was set during setup. Use the provider's console/CLI for resets if needed.
- Important: Check firewall/security group rules to allow connection from our service.
- Helpful Links:
Web Hosting with Control Panel
(e.g., cPanel, Plesk - Less common for PostgreSQL)
- Log in to your hosting control panel.
- Look for "PostgreSQL Databases" or similar sections.
- Should list Database Names and associated Usernames (Roles).
- Hostname is often
localhost
, but *verify* with host. - Port is usually 5432.
- Password set during user creation; use panel tools for reset.
- Important: Remote access rules may need configuration (IP allowlisting). Check host docs.
- Helpful Links:
Self-Hosted / Custom Server
(e.g., VPS, Dedicated Server, On-Premise)
- Ask the administrator/developer/DevOps person managing the server.
- Check application config files (
.env
,settings.py
,database.yml
, etc.) carefully. - Check PostgreSQL config files:
postgresql.conf
(forlisten_addresses
,port
) and potentiallypg_hba.conf
(for access control rules). - Refer to installation documentation.
- Passwords can be reset via
psql
commands by an admin (e.g.,ALTER USER ...
). - Helpful Links:
Using a Database Management Tool
(e.g., pgAdmin, DBeaver, TablePlus, Postico)
- Open your PostgreSQL management tool.
- Find the connection manager ("Servers," "Connections," "Edit," "Properties").
- The saved settings will display Hostname, Port, Username (User/Role), and potentially the default Database Name.
- Password might be masked or stored in your system keychain.
We understand that your database credentials are highly sensitive. Connecting requires us to store them, and we want to assure you we take this responsibility extremely seriously.
To safeguard your information, we utilize Infisical, a dedicated and highly secure secrets management platform designed specifically for handling sensitive data like API keys and database credentials.
Here's how we protect your credentials using best practices:
- Secure Storage with Infisical: Your credentials are not stored directly in our application databases but are managed securely within Infisical.
- Encryption: Credentials are encrypted both at rest (when stored in Infisical) and in transit (when communicated between our services and Infisical).
- Strict Access Control: Access to these credentials within our systems and Infisical is tightly controlled, audited, and limited only to the essential processes required to connect to your database and provide our service.
- Secure System-Level Key Rotation: We take extra precautions on our side to protect how our systems access those credentials. Specifically, we regularly rotate the internal access keys to your credentials — the secure secrets manager we use to store your credentials. This helps minimize risk in the event of a breach and ensures that even if a key were somehow compromised, it would quickly become invalid. It’s one of the ways we enforce strong operational security around your sensitive data.
Your trust is paramount. While we implement robust measures on our end, please continue to treat these credentials carefully yourself and avoid sharing them through insecure channels (like email or public chat).
Still Stuck?
If you need further assistance finding these details, please consult the relevant technical contact (developer, hosting support, IT admin).