FAQs

How do I connect my PostgreSQL database?

By Max Hinrichs

Getting Started

How do I connect my PostgreSQL database to Indiequery?

Click "Add Database Connection" in your dashboard and fill in your connection details:

  • Connection Name: A friendly name (e.g., "Production DB")
  • Host: Your database server address
  • Port: Usually 3306 (MySQL default)
  • Database Name: The specific database to connect to
  • Username: Database user with read permissions
  • Password: Database user password

Click "Add Connection" to test and save. Indiequery automatically tests your connection when you save it. You can also test connections manually anytime from your connections list.

What database permissions does IndieQuery need?

Indiequery only needs SELECT permissions on the tables and views you want to query. We recommend creating a dedicated read-only user:

-- Create a read-only user for Indiequery
CREATE USER indiequery_readonly WITH PASSWORD 'secure_password';

-- Grant connection to your database
GRANT CONNECT ON DATABASE your_database TO indiequery_readonly;

-- Grant usage on schema (usually 'public')
GRANT USAGE ON SCHEMA public TO indiequery_readonly;

-- Grant select on all current tables
GRANT SELECT ON ALL TABLES IN SCHEMA public TO indiequery_readonly;

-- Grant select on future tables (optional)
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO indiequery_readonly;

Network & Security

Do I need to configure my firewall?

Yes, you'll need to whitelist Indiequery's server IP address: 91.98.141.61

For cloud databases: - Add this IP to your database's allowed IP addresses or security groups - Ensure your database accepts connections on port 5432 (or your custom port)

For self-hosted databases: - Configure your firewall to allow connections from 91.98.141.61 - Update your postgresql.conf to accept external connections - Modify pg_hba.conf to allow authentication from our IP

Is my data secure?

Yes. Indiequery uses multiple security layers:

  • Encrypted storage: All connection credentials are encrypted in our database
  • SSL/TLS required: All database connections use encrypted transport
  • Read-only access: IndieQuery cannot modify your data
  • Secure hosting: Our servers are hosted on secure infrastructure
  • No data retention: Query results are automatically deleted after 7 days

We strongly recommend using SSL connections and read-only database users.

Should I use SSL connections?

Always use SSL for production databases. IndieQuery forces SSL/TLS connections for security. Most cloud database providers support SSL by default.

If you're connecting to a local development database, SSL may not be necessary, but we still recommend it as best practice.

Troubleshooting

"Connection failed" - What should I check?

Network issues: 1. Verify our IP (91.98.141.61) is whitelisted in your firewall/security groups 2. Confirm your database accepts external connections 3. Check that the host and port are correct

Authentication issues: 1. Verify username and password are correct 2. Ensure the user has SELECT permissions on your database 3. Check that the user can connect from external IPs

Database issues: 1. Confirm the database name exists and is spelled correctly 2. Verify PostgreSQL is running and accepting connections 3. Check server logs for connection errors

"SSL connection required" error

This means your database requires SSL but your connection isn't configured for it. Check the "Require SSL connection" box in your connection settings.

If you're still having issues, your PostgreSQL server may not be configured for SSL connections.

"Permission denied" errors

Your database user lacks sufficient permissions. Ensure the user has: - CONNECT privilege on the database - USAGE privilege on the schema (usually 'public') - SELECT privilege on tables you want to query

Connection times out

Common causes: - Firewall blocking our IP address - Database server not accepting external connections - Incorrect host or port settings - Network connectivity issues

Indiequery has a 30-second connection timeout. If your database takes longer to respond, the connection will fail.

Can't see my tables in the schema browser

Check that your database user has SELECT permissions on the tables. Indiequery only shows tables and views that your user can access.

Database Configuration

How do I configure PostgreSQL for external connections?

Edit postgresql.conf:

listen_addresses = '*'  # or specify your server's IP
port = 5432
ssl = on  # recommended

Edit pg_hba.conf:

# Allow Indiequery to connect
host    your_database    your_user    91.98.141.61/32    md5

Restart PostgreSQL after making these changes.

What PostgreSQL versions are supported?

IndieQuery works with all modern PostgreSQL versions. We regularly test against the latest stable releases.

Can I connect to multiple databases on the same server?

Yes. Each database requires a separate connection in Indiequery. Your Starter plan includes 3 connections, while Pro includes unlimited connections.

Why use fresh connections instead of connection pooling?

This ensures better isolation and security. Each query gets a clean connection state, preventing issues with transaction state or temporary settings affecting other queries.

Still Need Help?

If you're still having connection issues:

  1. Use Indiequery's built-in connection test feature
  2. Check your database server logs for error messages
  3. Verify network connectivity from external sources
  4. Contact our support team with your connection error details

Note: Never share your actual database credentials when asking for help. Our support team can help diagnose connection issues without needing your passwords.

← Back to Blog