How to Connect Your Render PostgreSQL Database to Indiequery

Last updated: November 21, 2025

Connect your Render PostgreSQL database to Indiequery to query and explore data through a web interface. No desktop apps to install, no SSH required. Just grab your connection details from Render's dashboard and connect in minutes.

Get Your Render Database Connection Details

Log into your Render dashboard at dashboard.render.com and navigate to your PostgreSQL database. Find the connection details on your database's Info page under the Connections section.

You'll see two sets of connection details: Internal (for connecting from other Render services in the same region) and External (for connecting from Indiequery and other external tools).

Use the External connection details. You'll need:

  • Host - The external hostname ending in .render.com (e.g., dpg-abc123.oregon-postgres.render.com)
  • Port - Default is 5432
  • Database - Your database name
  • Username - Your database username
  • Password - Click the eye icon to reveal the password

Connect to Indiequery

Navigate to app.indiequery.com and click Add Database Connection. Enter the external connection details from Render:

  1. Host - The external hostname from Render (ending in .render.com)
  2. Port - Enter 5432
  3. Database - Your database name
  4. Username - Your database username
  5. Password - Click the eye icon in Render to reveal, then copy
  6. Keep "Require SSL" checked (Render encrypts connections with TLS)
  7. Name your connection (e.g., "Render Production")
  8. Click Add Connection Indiequery automatically tests the connection. If it succeeds, you're ready to query.

Whitelist Indiequery's IP Address

Render's Access Control feature lets you restrict database connections to specific IP addresses. This is available on paid plans (not Free tier).

On your database's Info page in Render, scroll to Access Control and click Add IP address. Enter Indiequery's IP: 91.98.141.61/32, optionally add a description like "Indiequery", and click Save.

Only whitelisted IPs can now connect via the external URL. Internal connections from other Render services remain unaffected. If you're on Render's Free tier, IP whitelisting isn't available and your database accepts connections from any IP with valid credentials.

Use Internal vs External Connection

Always use the External connection details for Indiequery. The internal connection only works from other Render services in the same region and isn't accessible from external tools like Indiequery.

The external connection routes through the public internet and may incur data transfer charges, but it's required for Indiequery to connect to your database.

Connect to a Read Replica

If you have Render's Business plan or higher, you can create read replicas. Connect Indiequery to a replica instead of your primary database for safer querying. Read replicas are read-only by default (no accidental writes) and query load doesn't impact your primary database.

In the Render dashboard, navigate to your database and go to the PostgreSQL Instance section. Click Add Read Replica, choose the same region as your primary database, and wait for status to show Available.

Click the replica to view its dashboard and copy the replica's external connection details (host, port, database, username, password) to use in Indiequery. Read replicas have their own connection credentials separate from the primary database.

Common Connection Issues

"Connection timed out" or "Connection refused"

Check you're using the External connection details, not Internal. Verify Indiequery's IP (91.98.141.61) is whitelisted if you enabled Access Control. Confirm your database status shows Available in Render dashboard and you're using port 5432.

"SSL connection required"

Render requires SSL/TLS for external connections. Keep the "Require SSL" checkbox checked in Indiequery.

"Authentication failed"

Double-check your username and password from Render's Info page. Click the eye icon to reveal the full password. Passwords can include special characters, so copy carefully from Render.

"Database does not exist"

Verify the database name in Render's Info page. Database names are case-sensitive. If you customized the database name during creation, use that instead of the default.

Next Steps

Once connected:

  • Browse your database schema and tables
  • Run SQL queries with autocomplete
  • Create visualizations from results
  • Save queries for reuse
  • Build dashboards
  • Share results publicly Navigate to the query editor and start exploring your Render database.
← Back to Hosting Integration