Share feedback, ideas and get community help

Updated 2 months ago

issue with minIO on raspberrypi

At a glance

The community member is developing a chatbot that they want to run locally for an art project. They are using Typebot.io and minIO in Docker on their Raspberry Pi 4 (Raspberry OS 64-bit). The community member is encountering issues with the setup, specifically an "INTERNAL_SERVER_ERROR" related to an "InvalidEndpointError" when trying to connect to minIO. They have provided their Docker Compose file and .env file, and other community members have responded with suggestions, such as providing the Docker Compose file and addressing a CORS access issue.

I am developing a chatbot that I want to run locally for an art project. on my RP4 (raspberry os 64bit) I am running Typebot.io and minIO in docker.

Both are accesible via their webUI. typebot on localhost:8080 and minIO on localhost:9000

In minIO I can see that the database is properly generated and public.

The docker compose logs state the following:

typebot-builder-1 | code: 'INTERNAL_SERVER_ERROR',typebot-builder-1 | name: 'TRPCError',typebot-builder-1 | [cause]: InvalidEndpointError: Invalid endPoint : http://minio:9000typebot-builder-1 | at new TypedClient (file:///app/node_modules/minio/dist/esm/internal/client.mjs:42:13)typebot-builder-1 | at new Client (file:///app/node_modules/minio/dist/esm/minio.mjs:44:8)typebot-builder-1 | at o (/app/apps/builder/.next/server/chunks/5370.js:92:4225)typebot-builder-1 | at n (/app/apps/builder/.next/server/pages/api/trpc/[trpc].js:1:13381)typebot-builder-1 | at /app/apps/builder/.next/server/pages/api/trpc/[trpc].js:1:10792typebot-builder-1 | at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30)typebot-builder-1 | at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)typebot-builder-1 | at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)typebot-builder-1 | at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)typebot-builder-1 | at async resolve (file:///app/node_modules/@trpc/server/dist/index.mjs:486:24)typebot-builder-1 | }

I can give you the .env content and the docker-compose.yml file if necessary
B
m
5 comments
Yes please docker compose file πŸ™‚
Hi! thanks for your reply! I got a little bit further. Now I am having a CORS access issue. this is my docker compose file:
version: '3.3' volumes: db-data: s3_data: services: typebot-db: image: postgres:16 restart: always volumes: - db-data:/var/lib/postgresql/data environment: - POSTGRES_DB=typebot - POSTGRES_PASSWORD=typebot healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres"] interval: 5s timeout: 5s retries: 5 typebot-builder: image: baptistearno/typebot-builder:latest restart: always depends_on: typebot-db: condition: service_healthy ports: - '8080:3000' extra_hosts: - 'host.docker.internal:host-gateway' env_file: .env typebot-viewer: image: baptistearno/typebot-viewer:latest depends_on: typebot-db: condition: service_healthy restart: always ports: - '8081:3000' env_file: .env minio: image: minio/minio command: server /data --console-address ":9001" ports: - '9000:9000' - '9001:9001' environment: MINIO_ROOT_USER: minio MINIO_ROOT_PASSWORD: minio123 volumes: - s3_data:/data # This service just make sure a bucket with the right policies is created createbuckets: image: minio/mc depends_on: - minio entrypoint: > /bin/sh -c " sleep 10; /usr/bin/mc config host add minio http://minio:9000 minio minio123; /usr/bin/mc mb minio/typebot; exit 0; "
and this is my .env:
ENCRYPTION_SECRET=xUb9fz3YKjxHyq9MRV18yL0G/G1G0vHI DATABASE_URL=postgresql://postgres:typebot@typebot-db:5432/typebot NODE_OPTIONS=--no-node-snapshot NEXTAUTH_URL=http://typebot.local:8080 NEXT_PUBLIC_VIEWER_URL=http://typebot.local:8081 ADMIN_EMAIL=(myemail) SMTP_USERNAME=(myemail) SMTP_PASSWORD=(myemailpw) SMTP_HOST=smtp-auth.mailprotect.be SMTP_PORT=465 SMTP_SECURE=true NEXT_PUBLIC_SMTP_FROM=(myemail) S3_ACCESS_KEY=minio S3_SECRET_KEY=minio123 S3_BUCKET=typebot S3_PORT=9000 S3_ENDPOINT=minio S3_SSL=false
Thanks in advance:)
I added the S3_SSL=false which changed the error from the first error I mentioned initially. But now I am getting Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://minio:9000/typebot. (Reason: CORS request did not succeed). Status code: (null).
Add a reply
Sign up and join the conversation on Discord