Typebot not conect Minio
I uploaded a minio and I can transfer files to it via AWS CLI using the path http://s3.domain.com:9000
I can also get a list of files via AWS CLI
I can also access it publicly at http://s3.domain.com:9001
I configured the variables in typebot:
S3_ACCESS_KEY=minio
S3_SECRET_KEY=Su3epn3X3H6pgmenoQfX
S3_BUCKET=typebot
S3_ENDPOINT=s3.domain.com
S3_PORT=9000
S3_SSL=false
Folow docker-compose minio:
Version: "3.8"
volumes:
s3_data:
networks:
net_services:
external:
name: net_services
services:
minio:
labels:
virtual.host: 's3.domain.com' # change to your domain
virtual.port: '9000'
virtual.tls-email: '[email protected]' # change to your email
container_name: minio-gen
image: minio/minio
command: ["server", "--console-address", ":9001", "/data"]
ports:
- '9000:9000'
- '9001:9001'
environment:
MINIO_ROOT_USER: minio
MINIO_ROOT_PASSWORD: Su3epn3X3H6pgmenoQfX
volumes:
- s3_data:/data
networks:
- net_services
However, he can't save anything in the minio.
Can someone help me?8 Replies
What's the error?
Can you provide the server logs? There should be a clear error there.
If you are self-hosting it with docker. Type this command in your terminal:
Paste all the logs here so that we can help you properly!
However, he can't save anything in the minio.What is the error? What does it say?
Hi @Baptiste thanks!
Follow logs.
Minio:
MinIO Object Storage Server
Copyright: 2015-2024 MinIO, Inc.
License: GNU AGPLv3 - https://www.gnu.org/licenses/agpl-3.0.html
Version: RELEASE.2024-06-22T05-26-45Z (go1.22.4 linux/amd64)
API: http://172.22.0.8:9000 http://127.0.0.1:9000
WebUI: http://172.22.0.8:9001 http://127.0.0.1:9001
Docs: https://min.io/docs/minio/linux/index.html
Status: 1 Online, 0 Offline.
STARTUP WARNINGS:
- The standard parity is set to 0. This can lead to data loss.
You are running an older version of MinIO released 3 days before the latest release
Update: Run mc admin update ALIAS
Typebuilder:
- event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
- ready [next-runtime-env] wrote browser runtime environment variables to '/app/apps/builder/public/__ENV.js'.
Waiting for 15s for database to be ready...
Prisma schema loaded from packages/prisma/postgresql/schema.prisma
Datasource "db": PostgreSQL database "typebot", schema "public" at "postgres_lideri:5432"
67 migrations found in prisma/migrations
No pending migrations to apply.
▲ Next.js 14.1.0
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Ready in 1406ms
prisma:info Starting a postgresql pool with 113 connections.
TypeView:
- event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
- ready [next-runtime-env] wrote browser runtime environment variables to '/app/apps/viewer/public/__ENV.js'.
▲ Next.js 14.1.0
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Ready in 134ms
prisma:info Starting a postgresql pool with 113 connections.
prisma:info Starting a postgresql pool with 113 connections.Follow Inspects:
Minio:
TypeBuild:
not show error..
Then why do you say "can't save anything in the minio." How does that translates visually? 😅
Did you see the video I uploaded?
definitely typebot is not working with minio!
it doesn't generate logs.. it doesn't generate errors.. it just doesn't upload images to the minio.
I can via AWS CLI download, upload and even list files in the minio.. but typebot doesn't save images.. it also doesn't generate logs to help with trobleshoting
Resolve!
The solution was:
1 - Minio is running on https.
2 - Use traefik or ngnix to redirect from port 9000 to 443.
Thanks