Hi Team,
I am facing issues while configuring the MinIO bucket with NocoDB. I am deploying NocoDB in a self-hosted environment on Kubernetes using a Helm chart. The MinIO application is installed on the same cluster.
I have provided the following environment variables via the Helm chart and also attempted to connect through the UI. However, both approaches result in the same error: “Some internal error occurred.”
Additionally, the NocoDB pod is going into a CrashLoopBackOff state and then restarting, making it difficult to retrieve any meaningful error logs.
Here are the steps I have taken so far:
- Verified that the MinIO bucket exists and is accessible.
- Confirmed that the environment variables for MinIO (e.g.,
NC_S3_BUCKET
,NC_S3_ACCESS_KEY
,NC_S3_ACCESS_SECRET
, etc.) are correctly set in the Helm chart. - Ensured that the MinIO service is reachable from the NocoDB pod within the cluster.
- Attempted to enable debugging in NocoDB by setting
NC_LOG_LEVEL
todebug
, but no additional logs were captured due to the pod’s crash.
Could you please assist in identifying the root cause of this issue? Any guidance on how to capture detailed logs or resolve the CrashLoopBackOff state would be greatly appreciated.
extraSecretEnvs:
NC_AUTH_JWT_SECRET: secretString
NC_DB: “pg://postgres-:5432?u=nocodb&p=*******d=nocodb"
NC_S3_BUCKET: “nocodb”
NC_S3_ACCESS_KEY: “nocodb”
NC_S3_ACCESS_SECRET: "***********************************”
NC_S3_FORCE_PATH_STYLE: “true”
NC_S3_ENDPOINT: “https://minio.infra.vite/”
NC_S3_PORT: “9000”
storage:
enabled: true
size: 10Gi
storageClassName: “manual”
accessModes:
- ReadWriteMany
nfs:
server: PDC00isiNFS01.oh.com
path: /ifs/pdcdata/nfs/devtest/nocodb
persistentVolumeReclaimPolicy: Retain
Thank you for your support!
Regards,
Devika