Baserow Docker Setup <> Issues with Webhooks, CSV Export, and Public View

Technical Help
,
1

Hello everyone,

I am experiencing issues with my Docker Compose setup for Baserow and am seeking help to resolve them. Here are the problems I am facing:

  1. Non-functional Webhooks: Despite creating, modifying, or deleting data in Baserow, the webhooks intended to trigger workflows in n8n are not working. There are no triggers visible in the logs.
  2. CSV Export Issue: When trying to export data in CSV, the process remains stuck at 0%, even though I can see the GET requests in the backend logs.
  3. Error in Public Views: When grouping columns and sharing a view publicly, I receive an “error loading view” message.

My Docker Compose configuration is as follows :

version: "3.4"

services:
  db:
    image: postgres:11
    restart: unless-stopped
    environment:
      POSTGRES_USER: baserow
      POSTGRES_PASSWORD: your_password
      POSTGRES_DB: baserow
    volumes:
      - db_data:/var/lib/postgresql/data

  backend:
    image: baserow/backend:latest
    restart: unless-stopped
    environment:
      SECRET_KEY: your_secret_key
      DATABASE_HOST: db
      DATABASE_PORT: 5432
      DATABASE_NAME: baserow
      DATABASE_USER: baserow
      DATABASE_PASSWORD: your_password
      REDIS_HOST: redis
      BASEROW_PUBLIC_URL: http://XX.XXX.XX.XXX:8000
      PRIVATE_BACKEND_URL: http://backend:8000
      PUBLIC_BACKEND_URL: http://XX.XXX.XX.XXX:8000
    depends_on:
      - db
      - redis
    ports:
      - "8000:8000"

  web-frontend:
    image: baserow/web-frontend:latest
    restart: unless-stopped
    environment:
      PUBLIC_WEB_FRONTEND_URL: http://XX.XXX.XX.XXX:3000
      PUBLIC_BACKEND_URL: http://XX.XXX.XX.XXX:8000
    depends_on:
      - backend
    ports:
      - "3000:3000"

  redis:
    image: redis:6
    restart: unless-stopped

volumes:
  db_data:

networks:
  default:
    driver: bridge

I previously attempted a configuration with Traefik, encountering the same issues. Consequently, I’ve reverted to the more basic local setup shown below, currently managed via Portainer. I have ensured that the necessary ports are open. Any help or suggestions would be greatly appreciated.

Thank you in advance for your assistance :slight_smile:

2

Hi @Preview7282, I’m sorry to hear that you’re having some problems.

It sounds as if the Non-functional Webhooks and CSV Export Issue are related to each other. Both of these tasks are handled by a background worker. When taking a look at your docker-compose file, it looks like you’re trying to run Baserow in multiservice mode, but in that case, caddy, celery, celery-export-worker celery-beat-worker and redis have not been added. Any reason for that? Please look at this docker compose file docker-compose.yml · develop · Baserow / baserow · GitLab for an example.

It might be easier to use the quick-start steps from our docs here Install with Docker compose // Baserow, which is hinting at using the all-in-one image baserow/baserow. All the services are bundled into one image, and that’s easier to run.

I suspect that the Error in Public Views is related to a big we recently fixed. Please ensure you’re running the latest version, which is 1.23.2 at the time of writing. It should then work as expected.

3

Hello @bram ,

Thank you for your prompt and insightful response. After reflecting on your suggestions, I realize that I hadn’t included services like caddy, celery, and celery-export-worker in my Docker Compose setup. This oversight likely contributed to the non-functional webhooks and the CSV export issue I’ve been experiencing. I appreciate your pointing me towards the multiservice mode configuration in the GitLab repository.

Regarding the error in public views, I’ll make sure to update to the latest version, 1.23.2, as per your recommendation. Hopefully, this should resolve the issue.

In light of your advice, I’ve also considered the quick-start steps and the all-in-one image (baserow/baserow). I’ve now implemented this solution and am happy to report that it works perfectly for my needs. It’s indeed much easier to manage, and I appreciate you highlighting this option.

Thank you once again for your help. Your guidance has been invaluable in resolving these issues.

4

Glad to hear that it’s working now!