Invalid Endpoint Error: http://typebot-minio:9000 During File Import
Hello team,
We are encountering an “Invalid Endpoint: http://typebot-minio:9000” error every time we attempt to import a file into Typebot’s builder. We have already:
Verified that the MinIO service is running and healthy on port 9000.
Confirmed network connectivity between the builder container and the MinIO container.
Updated S3_ENDPOINT to both typebot-minio:9000 (backend) and NEXT_PUBLIC_S3_ENDPOINT to http://<host-IP>:9000 (frontend).
Ensured S3_ACCESS_KEY, S3_SECRET_KEY, and related S3 configuration variables are correctly set.
Despite these efforts, the import process continues to fail with the same endpoint error. Could you please advise on the proper configuration or any additional steps needed to resolve this issue?
Thank you for your assistance.
4 Replies
This endpoint is used on the browser to upload the file, so it needs to be reachable by anyone
I'm facing a persistent issue when trying to import files into the Typebot Builder. I keep getting this error:
"Invalid endPoint : http://typebot-minio:9000"
What I've tried and checked so far:
MinIO Configuration: MinIO is running and accessible locally via http://10.100.1.233:9000 (the console works fine).
Environment Variables:
S3_ENDPOINT is set to typebot-minio:9000 (for internal Docker communication).
NEXT_PUBLIC_S3_ENDPOINT is set to http://10.100.1.233:9000 (for browser access).
Ngrok Attempt:
I exposed MinIO (port 9000) via Ngrok (both HTTPS and HTTP tunnels).
Even when using the public Ngrok domain for both S3_ENDPOINT and NEXT_PUBLIC_S3_ENDPOINT, the error persists, now showing the Ngrok domain.
Cleanup and Restart: I consistently use docker compose down -v and docker compose up -d to ensure variables are applied and caches are cleared.
Logs and Browser: Logs confirm the error is related to the MinIO endpoint. The browser also attempts to access this endpoint directly during the import.
It seems that for some reason, the Typebot Builder's frontend import process tries to access MinIO with an endpoint that isn't publicly resolvable, despite my configurations.
I'd appreciate any guidance on alternative configurations or workarounds for the Typebot Builder to correctly handle file imports, bypassing this persistent endpoint issue.
Thanks for your help!
It seems that for some reason, the Typebot Builder's frontend import process tries to access MinIO with an endpoint that isn't publicly resolvable, despite my configurations.That is what I am saying, your endpoint needs to be publicly resolvable. The endpoint is used by the browser to upload the file
Hey Baptiste,
I'm still encountering the "Invalid endPoint: http://<MY_AZURE_PUBLIC_IP>:9000" error when trying to import files into the Typebot Builder.
Situation Summary:
Typebot is running on an Azure VM (Ubuntu) with Docker Compose.
Infrastructure is OK:
VM is running, and ports 3000, 3002, 9000, 9001 are open in the NSG (confirmed by telnet and MinIO console access).
MinIO is accessible, and the typebot bucket is created.
MinIO credentials verified and work for console login.
Typebot Configurations:
PUBLIC_HOST_IP in .env is set to my Azure public IP.
Both S3_ENDPOINT and NEXT_PUBLIC_S3_ENDPOINT in docker-compose.yml are set to http://<MY_AZURE_PUBLIC_IP>:9000 (forced to public IP).
S3_FORCE_PATH_STYLE: "true" and S3_SIGNATURE_VERSION: v2 are correct.
The Problem:
When importing a file, Typebot returns the "Invalid endPoint: http://<MY_AZURE_PUBLIC_IP>:9000" error.
CRITICAL: MinIO logs (docker compose logs -f typebot-minio) show NO INCOMING REQUESTS or activity at the moment of the import attempt. This means the request isn't even reaching MinIO, despite confirmed TCP connectivity.
Browser cache cleared, containers rebuilt multiple times.
It appears the S3 request for the file upload is either being interrupted or malformed before it reaches MinIO, even though all network and endpoint configurations seem correct.
Any thoughts on what else might be causing this "Invalid endPoint" specifically for file imports, if the infrastructure appears to be working?
hi