Depploy Baserow with Docker Compose

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

3.4 image docker

If you are self-hosting, which installation method do you use to run Baserow?

Docker 28.0.1

What are the exact steps to reproduce this issue?

  1. create a compose.yaml file with pasted lines from here : Install with Docker compose
    2 . docker compose up -d
  2. open http://thesystemip in browser. Site not found error.

Attach screenshots, videos, or logs that demonstrate the issue.

Capture.PNG
Capture.PNG1126×517 17.9 KB

Capture.PNG
Capture.PNG1126×517 17.9 KB

Capture.png
Capture.png1126×517 17.9 KB

2

Hi @BambosD, welcome to the community.

Could you open your terminal and run the command docker ps to ensure the container is up and running.

Did you make any adjustments to the compose.yaml file at all? Are you running anything else locally, perhaps with caddy?

Could you also try opening using the url localhost instead of your internal ip and see if that works.

3

hello @cwinhall
the docker ps command shows that baserow container is up (healthy) like below:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
70e5c70f7ad8 baserow/baserow:1.31.1 “/baserow.sh start” 7 minutes ago Up 7 minutes (healt hy) 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp baserow

The compose file is like the guide, no change. i’m not much experience with docker anyway.
I don’t run caddy, i don’t know even what that is.

the localhost is not working , because i run the docker in a VM, is not running locally. The VM is debian 12.9 , fresh install.
docker is installed with the official guide in docker website.

thanks for any guidance.

4

Thanks @BambosD. Here are a few other things to troubleshoot through:

  1. Are you sure that is the correct IP for your VM? Try running ip addr show to double check that. Also check the firewall status sudo ufw status - if it is enabled then you may need to allow http traffic using sudo ufw allow 80/tcp

  2. In your compose.yaml file did you update the defaults for the env variables for the IP because it defaults to localhost and you would need to update that to your VM’s IP.

PUBLIC_BACKEND_URL=http://192.168.10.61
PUBLIC_WEB_FRONTEND_URL=http://192.168.10.61
BASEROW_PUBLIC_URL=http://192.168.10.61

After making those changes stop the container and start it again and see if that works now.

  1. If this hasn’t solved it, can you run docker logs baserow and pass that along so we can continue to troubleshoot.
5

Thank you my friend.

in my compose file there is only BASEROW_PUBLIC_URL:
what would be the setting for listening to all IP ? 0.0.0.0 ? or http://0.0.0.0 ?

6

It’s not advisable to use 0.0.0.0.

If you run the command ip addr show you will get the correct address for what you want to use in this variable. It should be a valid IP or domain name.

7

ok fixed, i have used the dns name of the VM and is working.

but why there are many features locked for payment ? i thought this was the open source version of the app.