Closed zagub59 closed 2 months ago
Is the 500 error from minio or from ChiefOnboarding? If it's ChiefOnboarding, then what's the url that gives the 500 error (remove/mask your domain)?
Thanks for your quick answer :)
The 500 error comes from ChiefOnboarding when I try to upload a picture in a profile or a logo. In the browser console, I get this :
That api endpoint gets hit before minio gets hit, so this isn't relevant to minio. Can you try uploading a different file? Only the filename gets passed to that endpoint and I am wonder if there are characters in the filename that ChiefOnboarding is unable to process.
Oh, actually, the ALLOWED_S3_ENDPOINT_URL
isn't correct. That doesn't exist. It should be AWS_S3_ENDPOINT_URL
and
AWS_ACCESS_KEYD_ID
has a typo in it KEYD
.
I tried several filetypes with Chrome and Firefox but I get the same Server 500 issue.
When I try to browse to https://welcome.mydomain.com/api/org/file, I have Server Error (500). Is it a normal behavior ?
Geez I feel stupid. It's been a long day and I did not see the typo !
It's all working good now, thank you so much for your quick and efficient help and keep up the good work with this nice tool !
No worries. Glad it got resolved! Thanks for letting me know.
Hello everyone,
I've just set up ChiefOnboarding and everything is working great except for object storage.
I'm using Nginx Proxy Manager as my reverse proxy. A minio docker is set up and I've added environments variable in my docker-compose.yml but when I try uploading a file, I always get an error 500 and I don't know where it's coming from.
When I test minio with a python script, it's working OK so it seems minio is not the root cause ?
Here is docker-compose.yml of Chiefonboarding : `version: '3'
services: db: image: postgres:latest restart: always volumes:
POSTGRES_PASSWORD=postgres
app: image: chiefonboarding/chiefonboarding:latest restart: always ports:
Here is my minio docker-compose.yml : `version: '2' services: minio: image: 'bitnami/minio:latest' ports:
volumes: minio_storage: {} `
As for Nginx Proxy Manager:
Any idea what can cause this issue ?
Thank you for your help!