NocoDB and Metabase on my Cloudron instance

[james]

Hello @luisegundo

To get the PostgreSQL credentials of the nocodb app open the web terminal of the nocodb app:

In this terminal copy and paste the following command and press enter:

printenv | grep -i POSTGRESQL

You will get an output like this:

CLOUDRON_POSTGRESQL_URL=postgres://user876d5ae64c9d44a4979aafbfffb68286:25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6@postgresql/db876d5ae64c9d44a4979aafbfffb68286
CLOUDRON_POSTGRESQL_DATABASE=db876d5ae64c9d44a4979aafbfffb68286
CLOUDRON_POSTGRESQL_PASSWORD=25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6
CLOUDRON_POSTGRESQL_USERNAME=user876d5ae64c9d44a4979aafbfffb68286
CLOUDRON_POSTGRESQL_HOST=postgresql
CLOUDRON_POSTGRESQL_PORT=5432

Copy and save this output somewhere, you will need it later.

Now in the metabase web UI I can add a database with the previous credentials.
Tip, use the CLOUDRON_POSTGRESQL_URL and put in the Connection string (optional) field in Metabase and give it a descriptive display name instead of the long generated string db876d5ae64c9d44a4979aafbfffb68286:

Now I can access the NocoDB PostgreSQL database in Metabase:

Is this what you needed?

[luisegundo]

Hello Cloudron Support,

I need assistance with an internal app-to-app database connection.

Context:
We are using NocoDB and Metabase on Cloudron Pro.
NocoDB is working correctly with the internal PostgreSQL addon (confirmed through Web Terminal using printenv | grep POSTGRESQL).
Metabase was freshly reinstalled and is working normally.

Problem:
We cannot establish a connection from Metabase to NocoDB’s PostgreSQL database.

Metabase shows this error:
“No pg_hba.conf entry for host 172.x.x.x”

The Cloudron documentation says that apps can access another app’s PostgreSQL addon via the hostname “postgresql”, and that the addon credentials can be used directly in other apps.

We followed the guide:
https://docs.cloudron.io/guides/connect-postgresql/

We retrieved the credentials inside NocoDB:

• CLOUDRON_POSTGRESQL_URL
• CLOUDRON_POSTGRESQL_DATABASE
• CLOUDRON_POSTGRESQL_USERNAME
• CLOUDRON_POSTGRESQL_PASSWORD
• CLOUDRON_POSTGRESQL_HOST (postgresql)
• CLOUDRON_POSTGRESQL_PORT (5432)

These credentials work inside NocoDB itself, but Metabase cannot connect using them.
It looks like the Metabase container is not allowed to access the NocoDB PostgreSQL addon.

Issue:
We are unable to locate any “Access Control”, “Network Policy”, or “Database addon permissions” screen in the current Cloudron UI for the NocoDB app.
Without these options, we cannot confirm whether Metabase is allowed to reach the internal PostgreSQL service of NocoDB.

What we need clarified:

1. Where exactly, in the current Cloudron UI, can we allow Metabase to access NocoDB’s PostgreSQL addon?
   (or confirm if this access is automatically allowed)

2. Does Cloudron require any explicit permission or network configuration for one app (Metabase) to connect to another app’s PostgreSQL addon?

3. Is the “postgresql” hostname the correct one for inter-app communication in this scenario?

4. If additional configuration is required, could you provide the exact step-by-step instructions?

This is blocking our setup, and we would appreciate detailed guidance.

Thank you.

[james]

Hello @luisegundo

Have you seen my previous answer? Just want to make sure it was not overlooked.
https://forum.cloudron.io/post/116969

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Where exactly, in the current Cloudron UI, can we allow Metabase to access NocoDB’s PostgreSQL addon?
(or confirm if this access is automatically allowed)

There is no such feature in the Dashboard to check this.
Network accessibility between apps is default and should work.

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Does Cloudron require any explicit permission or network configuration for one app (Metabase) to connect to another app’s PostgreSQL addon?

No.

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Is the “postgresql” hostname the correct one for inter-app communication in this scenario?

Yes.

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

If additional configuration is required, could you provide the exact step-by-step instructions?

See https://forum.cloudron.io/post/116969

[luisegundo]

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:

1. You said that inter‑app network access is automatic and always allowed.
2. You confirmed that no permissions or UI settings are required.
3. 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:

1. Why would Metabase try to connect using a 172.x.x.x container IP if “postgresql” is always resolvable between apps?
2. Is there a way to verify inside each container that the hostname “postgresql” resolves correctly (for example, via ping, nslookup, or another command)?
3. Is there any scenario where the hostname “postgresql” would NOT resolve automatically?
4. Is there a way to confirm that both apps are on the same internal Cloudron network?
5. 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.

[james]

Hello @luisegundo

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Why would Metabase try to connect using a 172.x.x.x container IP if “postgresql” is always resolvable between apps?

By default, the Cloudron internal PostgreSQL Service container with hostname postgresql resolves to the IP address 172.18.30.2.
If Metabase resolves the hostname postgresql to 172.18.30.2 that is correct.

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Is there a way to verify inside each container that the hostname “postgresql” resolves correctly (for example, via ping, nslookup, or another command)?

Yes, if you open the Web Terminal of an app, you can verify this with either nslookup or dig.

Example from a Cloudron server with just 1x LAMP app and from inside that LAMP apps Web Terminal

root@fbbbe700-24f0-4832-89e8-487e633c35d3:/app/code# nslookup postgresql
Server:         127.0.0.11
Address:        127.0.0.11#53

Non-authoritative answer:
Name:   postgresql
Address: 172.18.30.2
Name:   postgresql
Address: fd00:c107:d509::f

root@fbbbe700-24f0-4832-89e8-487e633c35d3:/app/code# dig postgresql

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> postgresql
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26454
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;postgresql.                    IN      A

;; ANSWER SECTION:
postgresql.             600     IN      A       172.18.30.2

;; Query time: 2 msec
;; SERVER: 127.0.0.11#53(127.0.0.11) (UDP)
;; WHEN: Wed Dec 17 19:17:33 UTC 2025
;; MSG SIZE  rcvd: 54

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

Is there a way to confirm that both apps are on the same internal Cloudron network?

If the Metabase app is resolving postgresql to 172.18.30.2 then it is in the same network.

---

@luisegundo said in NocoDB and Metabase on my Cloudron instance:

We are simply trying to connect Metabase → NocoDB PostgreSQL using the internal addon credentials.

I just want to make sure we are speaking about the same thing here.
Since in my previous post, the Metabase UI states Add a database and you are writing about using the internal addon credentials.
You are trying to add the NocoDB Database inside Metabase with the Add a database, correct?

If you feel like this is going nowhere, please enable Remote Support and write an email to support@cloudron.io and reference this topic in your email.

[luisegundo]

I need to link the NocoDB database to Metabase, but I need the following information: Database name
Username
Password
Host
Port

How can I get this information?

[james]

Hello @luisegundo
Please stop creating new topics with the same content, thanks.

Can you please explain what exactly is not working from the provided information in this topic?

[luisegundo]

This post is deleted!

[luisegundo]

My knowledge level is beginner, and I was using AI assistance, but it's not working either.

I already asked a colleague for guidance, and he's also having trouble.

Could you tell me exactly how to obtain the following information from NocoDB?

Database name
Username
Password
Host
Port

Please provide a step-by-step guide on how to do this, considering my beginner level.

[james]

Hello @luisegundo
I have written a guide with screenshots, did you see that one? https://forum.cloudron.io/post/116969
Have you tried following these steps?
At which step do you run into issues?