Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Discuss
  3. NocoDB and Metabase on my Cloudron instance

NocoDB and Metabase on my Cloudron instance

Scheduled Pinned Locked Moved Discuss
8 Posts 2 Posters 41 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    luisegundo
    wrote last edited by joseph
    #1

    Cloudron Support,

    I have installed both NocoDB and Metabase on my Cloudron instance.
    Both apps installed successfully, but I am unable to connect Metabase to NocoDB’s database.

    NocoDB is running with SQLite by default, and when I try to configure it to use the PostgreSQL addon, the connection does not work.

    I would like to clarify the following:

    Does the Free plan support internal networking between apps (for example, allowing Metabase to connect to NocoDB through the PostgreSQL addon)?
    Is the failure to switch NocoDB to PostgreSQL related to Free plan limitations?
    After upgrading to the Pro plan, will I be able to configure NocoDB to use PostgreSQL and then allow Metabase to connect to that PostgreSQL database normally?
    Thanks in advance.
    Luis

    J 1 Reply Last reply
    0
    • L luisegundo

      Cloudron Support,

      I have installed both NocoDB and Metabase on my Cloudron instance.
      Both apps installed successfully, but I am unable to connect Metabase to NocoDB’s database.

      NocoDB is running with SQLite by default, and when I try to configure it to use the PostgreSQL addon, the connection does not work.

      I would like to clarify the following:

      Does the Free plan support internal networking between apps (for example, allowing Metabase to connect to NocoDB through the PostgreSQL addon)?
      Is the failure to switch NocoDB to PostgreSQL related to Free plan limitations?
      After upgrading to the Pro plan, will I be able to configure NocoDB to use PostgreSQL and then allow Metabase to connect to that PostgreSQL database normally?
      Thanks in advance.
      Luis

      J Offline
      J Offline
      joseph
      Staff
      wrote last edited by joseph
      #2

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

      NocoDB is running with SQLite by default

      NocoDB is using postgres by default. What makes you think it is using SQLite by default? If you open Web Terminal, you can run env | grep POSTGRES_ and you will see the postgres credentials nocodb uses. You can put these credentials in metabase to connect.

      Does the Free plan support internal networking between apps (for example, allowing Metabase to connect to NocoDB through the PostgreSQL addon)?

      All this is not related to subscription and plans. It's deployed the same way in all the plans.

      1 Reply Last reply
      1
      • L Offline
        L Offline
        luisegundo
        wrote last edited by
        #3

        Hi,

        I have a clean Cloudron Pro installation.

        • Metabase installed from Cloudron App Store
        • I completed the initial Metabase setup
        • I can access Metabase normally
        • However, I do NOT see "Admin settings" anywhere
        • There is no option to add a database

        In the top-right settings menu, I only see:

        • Account settings
        • Help
        • About Metabase

        This suggests my user is not an admin.

        Questions:

        1. How can I confirm if my Metabase user is an admin on Cloudron?
        2. How can I promote my user to admin?
        3. Is there a Cloudron-supported way to reset or assign the Metabase admin user?

        Thanks.

        1 Reply Last reply
        0
        • L Offline
          L Offline
          luisegundo
          wrote last edited by
          #4

          Hi Cloudron Support,

          We have a fresh Cloudron Pro installation (domain dados.server.seuimovel.com.br). All the apps we plan to use are already installed and the admin user (admin@cloudron.local) is working, so we have full administrative access in the UI.

          Our stack will consist of the following Cloudron apps (plus a few external services that must be connected to them):

          Category Cloudron App Purpose
          Data & Processes NocoDB Low‑code relational data store (tables/funnels)
          Automations n8n Workflow engine (triggered by webhooks, timers, etc.)
          Customer Service Chatwoot Live‑chat / ticketing system
          Email Marketing Listmonk Newsletter & bulk‑email campaigns
          Analytics Metabase BI dashboards and reporting

          Exportar

          Copiar
          External services we need to connect:

          Z‑API – WhatsApp gateway (to be called from Chatwoot and n8n)
          Amazon SES – high‑deliverability SMTP for Listmonk
          The core open question is how to provide a single PostgreSQL database that can be used by both NocoDB and Metabase (and optionally by n8n for its own data). We have identified three possible approaches, but we need confirmation on whether each is supported on Cloudron, and, if so, the exact steps to implement them:

          1️⃣ Use the internal PostgreSQL instance that NocoDB runs on (the one that is not exposed in the Cloudron UI).
          Is it possible to expose that internal database to other apps (Metabase, n8n) via a network‑allowed hostname/port?
          If it is possible, what configuration changes (e.g., Cloudron networking, app permissions, environment variables) are required?

          2️⃣ Deploy a dedicated PostgreSQL app on Cloudron (the “PostgreSQL” addon) and configure both NocoDB and Metabase to connect to it.
          What are the exact steps to:

          Create the PostgreSQL app (or enable the addon) on Cloudron Pro
          Retrieve the connection credentials (host, port, database, user, password) from the Cloudron UI
          Configure NocoDB to use this external PostgreSQL (via its Settings → Database page)
          Configure Metabase (Admin → Databases → Add database) with the same credentials
          Optionally point n8n to the same PostgreSQL instance (if we want to store workflow data there)
          3️⃣ Use an external PostgreSQL service (e.g., Supabase, Amazon RDS, Neon) and have all Cloudron apps connect to it.
          What is the recommended way to store the external credentials securely in each app (environment variables, Cloudron Secrets, etc.)?
          Are there any Cloudron‑specific networking restrictions we need to be aware of when an app connects to an external host?

          Additional integration questions
          n8n ↔ Chatwoot – We want n8n to listen to Chatwoot webhook events (new tickets, status changes) and also to push updates back to Chatwoot. Is there a built‑in “Chatwoot” node in n8n, or do we need to use generic HTTP/Webhook nodes? Any documentation for the required authentication (API token, JWT) would be appreciated.

          Chatwoot ↔ Z‑API (WhatsApp) – We plan to forward incoming WhatsApp messages from Z‑API to Chatwoot and send replies back through Z‑API. What is the recommended webhook configuration on Z‑API, and does Chatwoot support a custom “WhatsApp” channel out‑of‑the‑box, or must we use the generic “API” channel?

          Listmonk ↔ Amazon SES – We intend to use Amazon SES as the SMTP relay for Listmonk. Are there any Cloudron‑specific steps (e.g., adding SES credentials as a “Mail Server” addon, or setting environment variables) to make this work reliably?

          Metabase ↔ NocoDB tables – Once the PostgreSQL connection is established (options 1‑3 above), will Metabase automatically discover the NocoDB tables (including the separate tables we will create for each funnel: Captação, Oportunidades, Follow‑up, Relacionamento, Gestão)? If not, what is the minimal configuration needed in NocoDB to expose those tables to external queries?

          Automation of “Responsável” field – In NocoDB we need the “Responsável” column to be automatically populated based on the ticket owner in Chatwoot (or the workflow owner in n8n). Is there a native NocoDB trigger we can use, or should we create an n8n workflow that updates the record via NocoDB’s REST API? Any example workflow would be helpful.

          Documentation request – Could you provide (or point us to) a consolidated Cloudron documentation page that covers:

          Managing app‑to‑app networking and permissions (especially for database sharing)
          Storing and retrieving secret credentials for external services (SES, Z‑API, external PostgreSQL)
          Exporting/importing NocoDB schemas so that we can version‑control our funnel tables
          Summary of what we need
          Confirmation on whether Option 1 (internal NocoDB PostgreSQL) can be exposed, and the exact steps if it is possible.
          Full, step‑by‑step guide for Option 2 (dedicated Cloudron PostgreSQL), including how to point NocoDB, Metabase, and optionally n8n to it.
          Guidance for Option 3 (external PostgreSQL), especially regarding secret handling and network policies.
          Answers to the integration questions (n8n ↔ Chatwoot, Chatwoot ↔ Z‑API, Listmonk ↔ SES, Metabase ↔ NocoDB tables, automation of “Responsável”).
          Links to any relevant Cloudron documentation or example repositories that cover the above topics.
          We prefer to keep everything inside Cloudron whenever possible to reduce external dependencies, but we are open to using external services (SES, Z‑API, external PostgreSQL) if they are required for robustness.

          Thank you for your help – we look forward to a detailed response so we can move forward without further trial‑and‑error.

          Best regards,
          Luis

          1 Reply Last reply
          0
          • J Offline
            J Offline
            joseph
            Staff
            wrote last edited by joseph
            #5

            @luisegundo after you intsall metabase, the initial admin credentials are:

            Username: admin@cloudron.local
            Password: changeme123
            

            You should see a popup after installation with the above info. Otherwise, in the App -> Info.

            L 1 Reply Last reply
            0
            • J joseph

              @luisegundo after you intsall metabase, the initial admin credentials are:

              Username: admin@cloudron.local
              Password: changeme123
              

              You should see a popup after installation with the above info. Otherwise, in the App -> Info.

              L Offline
              L Offline
              luisegundo
              wrote last edited by
              #6

              @joseph,

              We have a fresh Cloudron Pro installation (domain dados.server.seuimovel.com.br ). All the apps we plan to use are already installed and the admin user (admin@cloudron.local) is working, so we have full administrative access in the UI.

              Our stack will consist of the following Cloudron apps (plus a few external services that must be connected to them):

              Category Cloudron App Purpose
              Data & Processes NocoDB Low‑code relational data store (tables/funnels)
              Automations n8n Workflow engine (triggered by webhooks, timers, etc.)
              Customer Service Chatwoot Live‑chat / ticketing system
              Email Marketing Listmonk Newsletter & bulk‑email campaigns
              Analytics Metabase BI dashboards and reporting

              Exportar

              Copiar
              External services we need to connect:

              Z‑API – WhatsApp gateway (to be called from Chatwoot and n8n)
              Amazon SES – high‑deliverability SMTP for Listmonk
              The core open question is how to provide a single PostgreSQL database that can be used by both NocoDB and Metabase (and optionally by n8n for its own data). We have identified three possible approaches, but we need confirmation on whether each is supported on Cloudron, and, if so, the exact steps to implement them:

              1️⃣ Use the internal PostgreSQL instance that NocoDB runs on (the one that is not exposed in the Cloudron UI).
              Is it possible to expose that internal database to other apps (Metabase, n8n) via a network‑allowed hostname/port?
              If it is possible, what configuration changes (e.g., Cloudron networking, app permissions, environment variables) are required?

              2️⃣ Deploy a dedicated PostgreSQL app on Cloudron (the “PostgreSQL” addon) and configure both NocoDB and Metabase to connect to it.
              What are the exact steps to:

              Create the PostgreSQL app (or enable the addon) on Cloudron Pro
              Retrieve the connection credentials (host, port, database, user, password) from the Cloudron UI
              Configure NocoDB to use this external PostgreSQL (via its Settings → Database page)
              Configure Metabase (Admin → Databases → Add database) with the same credentials
              Optionally point n8n to the same PostgreSQL instance (if we want to store workflow data there)
              3️⃣ Use an external PostgreSQL service (e.g., Supabase, Amazon RDS, Neon) and have all Cloudron apps connect to it.
              What is the recommended way to store the external credentials securely in each app (environment variables, Cloudron Secrets, etc.)?
              Are there any Cloudron‑specific networking restrictions we need to be aware of when an app connects to an external host?

              Additional integration questions
              n8n ↔ Chatwoot – We want n8n to listen to Chatwoot webhook events (new tickets, status changes) and also to push updates back to Chatwoot. Is there a built‑in “Chatwoot” node in n8n, or do we need to use generic HTTP/Webhook nodes? Any documentation for the required authentication (API token, JWT) would be appreciated.

              Chatwoot ↔ Z‑API (WhatsApp) – We plan to forward incoming WhatsApp messages from Z‑API to Chatwoot and send replies back through Z‑API. What is the recommended webhook configuration on Z‑API, and does Chatwoot support a custom “WhatsApp” channel out‑of‑the‑box, or must we use the generic “API” channel?

              Listmonk ↔ Amazon SES – We intend to use Amazon SES as the SMTP relay for Listmonk. Are there any Cloudron‑specific steps (e.g., adding SES credentials as a “Mail Server” addon, or setting environment variables) to make this work reliably?

              Metabase ↔ NocoDB tables – Once the PostgreSQL connection is established (options 1‑3 above), will Metabase automatically discover the NocoDB tables (including the separate tables we will create for each funnel: Captação, Oportunidades, Follow‑up, Relacionamento, Gestão)? If not, what is the minimal configuration needed in NocoDB to expose those tables to external queries?

              Automation of “Responsável” field – In NocoDB we need the “Responsável” column to be automatically populated based on the ticket owner in Chatwoot (or the workflow owner in n8n). Is there a native NocoDB trigger we can use, or should we create an n8n workflow that updates the record via NocoDB’s REST API? Any example workflow would be helpful.

              Documentation request – Could you provide (or point us to) a consolidated Cloudron documentation page that covers:

              Managing app‑to‑app networking and permissions (especially for database sharing)
              Storing and retrieving secret credentials for external services (SES, Z‑API, external PostgreSQL)
              Exporting/importing NocoDB schemas so that we can version‑control our funnel tables
              Summary of what we need
              Confirmation on whether Option 1 (internal NocoDB PostgreSQL) can be exposed, and the exact steps if it is possible.
              Full, step‑by‑step guide for Option 2 (dedicated Cloudron PostgreSQL), including how to point NocoDB, Metabase, and optionally n8n to it.
              Guidance for Option 3 (external PostgreSQL), especially regarding secret handling and network policies.
              Answers to the integration questions (n8n ↔ Chatwoot, Chatwoot ↔ Z‑API, Listmonk ↔ SES, Metabase ↔ NocoDB tables, automation of “Responsável”).
              Links to any relevant Cloudron documentation or example repositories that cover the above topics.
              We prefer to keep everything inside Cloudron whenever possible to reduce external dependencies, but we are open to using external services (SES, Z‑API, external PostgreSQL) if they are required for robustness.

              Thank you for your help – we look forward to a detailed response so we can move forward without further trial‑and‑error.

              Best regards,
              Luis

              1 Reply Last reply
              0
              • J Offline
                J Offline
                joseph
                Staff
                wrote last edited by joseph
                #7

                @luisegundo I think what you are looking for is https://docs.cloudron.io/guides/connect-postgresql/ . Using that you can get the NocoDB postgresql addon credentials. Then, you would add it into metabase .

                We don't have docs on how to configure metabase, you have to check the metabase docs for that. For exmaple, https://www.metabase.com/docs/latest/databases/connections/postgresql

                L 1 Reply Last reply
                0
                • J joseph

                  @luisegundo I think what you are looking for is https://docs.cloudron.io/guides/connect-postgresql/ . Using that you can get the NocoDB postgresql addon credentials. Then, you would add it into metabase .

                  We don't have docs on how to configure metabase, you have to check the metabase docs for that. For exmaple, https://www.metabase.com/docs/latest/databases/connections/postgresql

                  L Offline
                  L Offline
                  luisegundo
                  wrote last edited by
                  #8

                  @joseph Hi again,

                  Thanks for your previous reply and for sending the documentation link.
                  I read the full guide you mentioned (https://docs.cloudron.io/guides/connect-postgresql/) and also checked the Metabase documentation for PostgreSQL connections.

                  However, I still cannot identify where exactly Cloudron exposes the PostgreSQL addon credentials for NocoDB. The UI layout on my server does not look like the one shown in the guide, and no credentials or addon entries appear under the app settings.

                  Since you mentioned that NocoDB does not use SQLite on Cloudron, I want to follow the official and supported path, but I need your help to understand the correct steps.

                  Could you please provide a clear step‑by‑step explanation of the process below?

                  Where exactly do I find the PostgreSQL addon credentials for the NocoDB app in the current Cloudron UI?
                  If the addon must be enabled manually, what is the exact procedure to enable it?
                  Once I have the credentials, what is the correct sequence to connect Metabase to the NocoDB PostgreSQL database?
                  If NocoDB requires a re‑installation to activate PostgreSQL, can you confirm that and describe the correct way to perform it?
                  I want to make sure I am following the supported method, and since I did not find the steps in the documentation, I would appreciate a detailed walkthrough.

                  Thank you very much.

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search