parseable icon indicating copy to clipboard operation
parseable copied to clipboard

Parseable fails to run with ceph s3 instances

Open mahdiG opened this issue 11 months ago • 2 comments

Hi. Parseable works fine with Minio s3 but I tried to run parseable docker with two different Ceph s3 instances but it gives error:

Error: Unhandled Error: response error "<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>
", after 0 retries: HTTP status client error (400 Bad Request) for url (https://s3.ir-thr-at1.arvanstorage.ir/parseable/.parseable.json)

the s3 works fine when used with s3cmd, mc, filestash, golang and python. I'm able to get, put, make bucket etc.

My env file looks like this:

P_STAGING_DIR=/staging
P_ADDR=0.0.0.0:8000
P_USERNAME=myuser
P_PASSWORD=mypass
P_S3_URL=https://s3.ir-thr-at1.arvanstorage.ir/
P_S3_BUCKET=parseable
P_S3_ACCESS_KEY=47xxxxxxa2
P_S3_SECRET_KEY=cdbxxxxxx5c
P_S3_REGION=default

Run command: docker run -p 8000:8000 --env-file parseable-env -v /parseable/staging:/staging parseable/parseable:v0.8.1 parseable s3-store

Bucket is empty so that isn't the problem. I tried making the bucket public but it didn't make a difference

mahdiG avatar Mar 12 '24 10:03 mahdiG

Thanks for reporting @mahdiG we'll take a look at this and get back.

nitisht avatar Mar 12 '24 15:03 nitisht

I'm having the same issue with MinIO. The error shows up in the Nginx access log instead of error, which makes me think the error is from MinIO, not Nginx.

vrelk-net avatar Mar 14 '24 17:03 vrelk-net