I can't install Baserow on CasaOS

[NadedrElAhlawy]

The first error was not being able to connect to the API

I think it was because the

BASEROW_PUBLIC_URL

variable was not set

When I searched, I solved the problem, but another problem appeared and I could not find a solution at all

Action not completed.
The action couldn’t be completed because an unknown error has occurred.

name: relaxed_mason
services:
baserow:
cpu_shares: 90
command:
container_name: baserow
deploy:
resources:
limits:
memory: 3871M
environment:
- BASEROW_PUBLIC_URL=http://192.168.186.128:7300/
image: baserow/baserow:1.21.2
labels:
icon: https://github.com/walkxcode/dashboard-icons/blob/main/png/baserow.png?raw=true
ports:
- target: 80
published: “7300”
protocol: tcp
- target: 443
published: “7301”
protocol: tcp
restart: unless-stopped
volumes:
- type: bind
source: /DATA/AppData/baserow/data
target: /baserow/data
devices:
cap_add:
network_mode: bridge
privileged: false
x-casaos:
author: self
category: self
hostname: “”
icon: https://github.com/walkxcode/dashboard-icons/blob/main/png/baserow.png?raw=true
index: /
port_map: “7300”
scheme: http
store_app_id: relaxed_mason
title:
custom: baserow

These are the details of the application

This is an image of the CasaOS interface along with its IP

Please help me because I searched a lot and did not find anything, and note that the first error is also found in Docker Desktop.

[bram]

Hi @NadedrElAhlawy, do you have some Baserow backend output logs that you can share? It will help us to identify the problem.

[NadedrElAhlawy]

@bram yes, sure

sorry for the late. but i don’t understand anything from it.

baserow-baserow-1 | e[1m [BASEROW-WATCHER][2023-12-11 11:42:34] e[32mBaserow is now available at http://192.168.186.128:7300/e[0m e(Be[m
baserow-baserow-1 | e[34m [BACKEND][2023-12-11 11:42:55] 127.0.0.1:50204 - “GET /api/_health/ HTTP/1.1” 200 e(Be[m
baserow-baserow-1 | e[34m [BACKEND][2023-12-11 11:42:55] 127.0.0.1:48952 - “GET /api/_health/ HTTP/1.1” 200 e(Be[m
baserow-baserow-1 | e[34m [BACKEND][2023-12-11 11:42:55] 127.0.0.1:48956 - “GET /api/settings/ HTTP/1.1” 200 e(Be[m
baserow-baserow-1 | e[34m [BACKEND][2023-12-11 11:42:55] 127.0.0.1:48966 - “GET /api/settings/ HTTP/1.1” 200 e(Be[m
baserow-baserow-1 | e[36m [BEAT_WORKER][2023-12-11 11:43:00] [2023-12-11 11:42:13,723: INFO/MainProcess] beat: Starting… e(Be[m
baserow-baserow-1 | e[36m [EXPORT_WORKER][2023-12-11 11:43:00] [2023-12-11 11:42:19,680: INFO/ForkPoolWorker-1] Task baserow.core.tasks.sync_templates_task[8abe1790-a6d0-4fe5-845e-77277d811672] succeeded in 4.782120819000056s: None e(Be[m
baserow-baserow-1 | e[36m [EXPORT_WORKER][2023-12-11 11:43:00] [2023-12-11 11:43:00,035: INFO/MainProcess] Task baserow.core.notifications.tasks.beat_send_instant_notifications_summary_by_email[50915f98-990c-4969-8f30-31ee72c9d0c2] received e(Be[m
baserow-baserow-1 | e[36m [EXPORT_WORKER][2023-12-11 11:43:00] [2023-12-11 11:43:00,061: INFO/MainProcess] Task baserow.core.notifications.tasks.singleton_send_instant_notifications_summary_by_email[74654868-fac6-4bb3-83c1-a11ef5bb98e0] received e(Be[m
baserow-baserow-1 | e[36m [EXPORT_WORKER][2023-12-11 11:43:00] [2023-12-11 11:43:00,062: INFO/ForkPoolWorker-1] Task baserow.core.notifications.tasks.beat_send_instant_notifications_summary_by_email[50915f98-990c-4969-8f30-31ee72c9d0c2] succeeded in 0.023593262999952458s: None e(Be[m
baserow-baserow-1 | 2023-12-11 11:43:02,124 INFO success: beatworker entered RUNNING state, process has stayed up for > than 100 seconds (startsecs)
baserow-baserow-1 | 2023-12-11 11:43:02,124 INFO success: beatworker entered RUNNING state, process has stayed up for > than 100 seconds (startsecs)

[bram]

Hi @NadedrElAhlawy, the logs you’ve provided don’t tell me anything about why signing up is failing, to be honest. Would if be possible if you copy the logs directly after you’re trying to sign up? I need to see exactly that error.

[NadedrElAhlawy]

The problem here is that when I click on create an account, nothing new appears in the logs

[NadedrElAhlawy]

Error in File field

I “solved” my problem by changing folder permissions. But I am unsure why this was required in the first place, and I am wondering if I did the appropriate thing. For reference, here is my docker compose stack in Portainer: version: '3.3' services: baserow: container_name: baserow network_mode: bridge environment: - 'BASEROW_PUBLIC_URL=http://192.168.86.200:9988' volumes: - '/volume2/docker/baserow/data:/baserow/data' ports: …

In this comment, the problem was solved by changing the path of some files

But unfortunately I do not know how to do this in CasaOS because I changed the path within compose and the result was that the program was not built due to many errors…

Could the solution be here, but I don’t know how to do it? @bram

[bram]

It’s a bit difficult to help you debug the problem here because I don’t have much experience with CasaOS. It seems like Baserow is running, but it’s not possible to make a public API request. Would you be able to share the network console output after making the request? In Firefox, this can be opened using the following command. It would be really useful if you can click on the request, and then open the response tab so that we can have better insight into what’s going wrong.