Baserow App Setup

Apps and Virtualization
1

Hi,
Very new to TrueNas just trying to get some Apps setup but I have hit a problem with the Baserow App from the catalogue and wondering if anyone else had problems deploying this.
I believe I got everything correct and the setup is very similar to NocoDB which is running correctly.
Baserow doesn’t seem to full deploy correctly.
If I try and browse to it I get a baserow page throwing an error.
The log didn’t seem to throw anything useful I was able to gleam as to what was wrong.
I need to take another look at it and when I do I can gather more information.

If anyone else has had a possible similar problem I would be grateful if you can throw any ideas of a fix my way in the mean time?

Thanks

Tom

1 Like
2

Forgot to say I originally tried to set it up on 25.4.1 and have since upgraded to 25.4.2 and tried again.

3

What error are you getting from the webpage? Also what is the app status at this time? Is it running, stuck deploying, or not starting at all?

4

image
image539×291 10.9 KB

image
image232×210 2.59 KB

image

image
image145×153 2.15 KB

It is stuck deploying, I have create a nested dataset like other apps and mapped the data and db to the respective datasets and all 3 are set to app.
Looks like something is working as I would not expect to get the baserow web ui error if not.

1 Like
5

Interesting. What do the logs from the baserow container say? It should be a button right next to the container name. If you hover over the buttons it should tell you if it logs or not.

6

@Tom_McGuire did you solved this?, i have the same issue

1 Like
7

No, this has been on the back burner for a while.
I noticed I have the same issue with any of the Database apps so not sure if I am not understanding how to set them up or something about my system.
I will take another look at it in the next few days and see what I can figure out.
The app normally shuts down too fast to grab the log from it

1 Like
8

i faced same issue…still waiting for solution

9

Just to make sure: Postgres needs permissions for user id 999 on the mounted dataset (if you’re using hostpaths). Are permissions for user id 999 set correctly?

10

I got it working like this:
I started with the ixvolumes instead of hostpath.
In the Public URL (Optional, Used for External Access) i put in my localIP adn the port I’m using this is the example
192.168.12.200:30163
It does take forever and a day to load baserow the first time.

I will update with instructions to set up using hostpath once i figure that out

11

Title: [Guide] How to Install Baserow with Host Path (Permissions & URL Fix)

Hey everyone,

I was able to get an instance of Baserow up and running using host paths, but it requires a few specific permission and URL settings. The app kept crashing with Permission denied errors until I did this.

Here’s a quick guide to save you the headache.

1. Create Your Datasets

First, create your datasets in TrueNAS. Using the apps pool is recommended, but you can put them anywhere. Make a note of your paths.

I used:

  • /mnt/tank/baserow/data (for the main app data)
  • /mnt/tank/baserow/pg_data (for the Postgres database)

2. Set Host Path Permissions (The Critical Step)

Before you start the app, you must set the correct ownership from the TrueNAS shell. The app’s built-in permission script can’t change ownership on host paths, so we have to do it manually.

Stop the app if it’s running, then go to System Settings > Shell and run these commands.

`Shell# Why? The main Baserow container runs as root (0)

but in the ‘apps’ group (568).

chown -R 0:568 /mnt/tank/baserow/data

chmod -R 775 /mnt/tank/baserow/data

Why? The Postgres container runs as user 999 and group 999.

It’s also very strict about permissions.

chown -R 999:999 /mnt/tank/baserow/pg_data

chmod -R 700 /mnt/tank/baserow/pg_data\`

3. Install/Configure the App

Now, install the Baserow app (or Edit your existing one):

  1. Storage: In the “Storage” section, set your “Baserow Data” and “Postgres Data” paths to the host paths you just created (e.g., /mnt/tank/baserow/data).
  2. Environment Variables (The URL Fix): This is the second place people get stuck. You need to tell Baserow what its URL is.

Scenario A: You ONLY use the local IP

If you just want to access Baserow at http://YOUR-NAS-IP:PORT:

  • Find BASEROW_PUBLIC_URL.
  • Set it to your IP and port. (My port was 30163, yours might be different).
    • BASEROW_PUBLIC_URL: http://192.168.1.546:30163

Scenario B: You use a Public Domain (like Cloudflare)

This is the best setup. It makes your public domain the “official” URL but still lets you access the app from the local IP.

  1. Set the main URL to your public domain:
  • BASEROW_PUBLIC_URL: https://baserow.youdomain.com
  1. Click Add to create a new variable to allow your local IP: This did not work for me for both public and local access but if you can figure it out please let us know
  • Variable Name: BASEROW_EXTRA_ALLOWED_HOSTS
  • Variable Value: 192.168.1.546 (Note: no http:// or port here)

4. Save and Start

Click Save and start the app. The containers will now have the correct permissions to your host paths, and the frontend will be able to connect to the backend without any “Not Found” or “API” errors.

Hope this helps!

It takes a really long time for this app to start the first time. Go make dinner in the meantime!!

1 Like