# Unable to configure minio
**URL:** https://community.nocodb.com/t/unable-to-configure-minio/1859
**Category:** Self-Host
**Created:** [May 8, 2025, 10:33am UTC](https://community.nocodb.com/t/unable-to-configure-minio/1859 "2025-05-08T10:33:08Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@devika](https://community.nocodb.com/u/devika)
#### Post date: [May 8, 2025, 10:33am UTC](https://community.nocodb.com/t/unable-to-configure-minio/1859/1 "2025-05-08T10:33:08Z")
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:
1. Verified that the MinIO bucket exists and is accessible.
2. 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.
3. Ensured that the MinIO service is reachable from the NocoDB pod within the cluster.
4. Attempted to enable debugging in NocoDB by setting `NC_LOG_LEVEL` to `debug`, 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/](https://minio.infra.vite/)”
NC\_S3\_PORT: “9000”
storage:
enabled: true
size: 10Gi
storageClassName: “manual”
accessModes:
- ReadWriteMany
nfs:
server: [PDC00isiNFS01.oh.com](http://PDC00isiNFS01.oh.com)
path: /ifs/pdcdata/nfs/devtest/nocodb
persistentVolumeReclaimPolicy: Retain
Thank you for your support!
Regards,
Devika
---
### Author:  [@devika](https://community.nocodb.com/u/devika)
#### Post date: [May 12, 2025, 9:39am UTC](https://community.nocodb.com/t/unable-to-configure-minio/1859/2 "2025-05-12T09:39:17Z")
@DarkPhoenix2704 , Could you please look into this issue and provide some solutions?
---
### Author:  [@Navi](https://community.nocodb.com/u/Navi)
#### Post date: [May 12, 2025, 9:41am UTC](https://community.nocodb.com/t/unable-to-configure-minio/1859/3 "2025-05-12T09:41:44Z")
It would be easier if you can run [auto upstall](https://docs.nocodb.com/getting-started/self-hosted/installation/auto-upstall/#notes-on-auto-upstall) and figure how the minio setup is done on a small VM and work backwards to your helm chart.
---
### Author:  [@devika](https://community.nocodb.com/u/devika)
#### Post date: [May 16, 2025, 3:47am UTC](https://community.nocodb.com/t/unable-to-configure-minio/1859/4 "2025-05-16T03:47:38Z")
Hi @Navi , I don’t see any environment variable specific to minio in document. [https://docs.nocodb.com/getting-started/self-hosted/environment-variables/#storage](https://docs.nocodb.com/getting-started/self-hosted/environment-variables/#storage) . Could you please review and confirm if this works with by placing **MINIO** instead of **S3**
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/”](https://minio.infra.vite/%E2%80%9D)
NC\_S3\_PORT: “9000”
[/quote]