Hello @james, thanks for your reply.
Yes, I saw your previous message and I’ve read the referenced post.
However, the issue is still happening even after following all steps exactly as described.
Key points:
You said that inter‑app network access is automatic and always allowed.
You confirmed that no permissions or UI settings are required.
You confirmed that the hostname "postgresql" is correct.
Given all of that, Metabase is still unable to connect to NocoDB’s internal PostgreSQL addon, and keeps returning:
“No pg_hba.conf entry for host 172.x.x.x”
This indicates that:
Metabase is NOT using the hostname “postgresql”
Metabase is instead falling back to an internal Docker IP (172.x.x.x)
The connection is being rejected at the PostgreSQL level
To help us properly debug this, could you clarify:
Why would Metabase try to connect using a 172.x.x.x container IP if “postgresql” is always resolvable between apps?
Is there a way to verify inside each container that the hostname “postgresql” resolves correctly (for example, via ping, nslookup, or another command)?
Is there any scenario where the hostname “postgresql” would NOT resolve automatically?
Is there a way to confirm that both apps are on the same internal Cloudron network?
Could you provide the exact expected behavior when an app tries to use the environment variables of another app’s addon?
We are simply trying to connect Metabase → NocoDB PostgreSQL using the internal addon credentials.
NocoDB works with these credentials, but Metabase refuses the same connection.
We would appreciate a more detailed explanation so we can proceed.
