Connect your database to BI Jedi

If Test connection fails, the issue is almost always network or database permissions — not your BI Jedi app credentials. Follow this checklist with your IT team.

IP to allowlist (BI Jedi)

Queries run from BI Jedi servers. On the database firewall, cloud security group, or pg_hba.conf/ MySQL rules, allow inbound traffic on the DB port (e.g. 5432 for PostgreSQL) from:

63.182.176.239

If the database is only reachable on an internal network (VPN, private IP), BI Jedi cannot connect until you expose an Internet-reachable endpoint or an approved tunnel.

In the BI Jedi app

Side menu Data Sources → strategy Direct external source .
Card Active source → + (new) or gear icon (edit).
Fill in Name, DB Type, Host, Port, DB Name, User, and Password. Use the eye icon to verify the password.
Optional: Set as default for queries .
Test connection → if OK, Save connection .
Then Sync to import the table list (metadata only, does not copy all operational data).

PostgreSQL

Error no pg_hba.conf entry for host: add a line in pg_hba.conf allowing the user and database from IP 63.182.176.239 (or from the network where BI Jedi runs), then reload config (pg_ctl reload).
Verify PostgreSQL listens on the correct interface (listen_addresses).
User with CONNECT on the database and SELECT on tables to analyze.

MySQL / MariaDB

Create a user with a restricted host: CREATE USER 'reader'@'63.182.176.239' IDENTIFIED BY '…';
Security group / firewall: open port 3306 (or yours) toward 63.182.176.239.

Common errors

Connection refused — DB service down, wrong port, or firewall blocking.
Timeout — host not reachable from the Internet, private IP only without VPN/tunnel.
Host in the error differs from your public IP — the DB sees BI Jedi IP (63.182.176.239), not your office PC: allowlist that one.

Need help? Contact support · Back to tutorials