[Bug]: S3 Bucket are not working with docker compose

[Bambijow]

Issue Description

After installing and configuring OpenSign with docker in local to use bucket OpenSign is not working. When uploading a file app returns error 400 with {"code":130,"error":"UnknownError"} as a response.

Expected Behavior

OpenSign should be able to upload and read from the bucket

Current Behavior

OpenSign returns a 400 bad request response with this body : {"code":130,"error":"UnknownError"}

Steps to reproduce

Install OpenSign in local with Docker Compose, use local storage -> everything is okay.
Use S3 Bucket configuration -> OpenSign returns a 400 bad request response with {"code":130,"error":"UnknownError"} as a body.

Screenshots of the issue(optional)

No response

Operating System [e.g. MacOS Sonoma 14.1, Windows 11]

Ubuntu 24.04.2

What browsers are you seeing the problem on?

Chrome, Firefox, Safari, Microsoft Edge

What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]

2.15.0 (With 1.4.2 everything works)

What environment are you seeing the problem on?

Dev (localhost or vercel)

Please check the boxes that apply to this issue report.

• I have searched the existing issues & discussions to make sure that this is not a duplicate.

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the existing issues & discussions to make sure that this is not a duplicate.

[andrew-opensignlabs]

Did you configure the storage options in your .env.prof file correctly? The simplest way to get going is to set "uselocal" to true.

[Bambijow]

Yes, here is my storage option in my .env

DO_SPACE=bucket name
DO_ENDPOINT=s3.eu-west-1.amazonaws.com
DO_BASEURL=https://s3.eu-west-1.amazonaws.com/
DO_ACCESS_KEY_ID=access key
DO_SECRET_ACCESS_KEY=secret
DO_REGION=eu-west-1
USE_LOCAL=false

I already tried changing DO_BASEURL with https://bucket-name.s3.eu-west-1.amazonaws.com/

[NicolasDierick]

@andrew-opensignlabs

Hello
Any news ?

I have the same issue on s3

Thank you

[andrew-opensignlabs]

@Bambijow @NicolasDierick can you share the OpenSign server logs?

[Bambijow]

My Opensign Server logs :

> open_sign_server@1.4.0 start
> node index.js

Please provide valid SMTP credentials
opensign-server running on port 8080.
Command output: 
Parse DBTool v1.2.0 - Parse server tool for data migration and seeding.

Run migration on parse-server at http://localhost:8080/app

 INFO  No migrations were executed, database schema was already up to date.

 SUCCESS  Successfully run migrations.


 INFO  No migrations were executed, database schema was already up to date.
 SUCCESS  Successfully ran indexed migrations directly on db.

The error sent to my browser :
Request URL : https://localhost:3001/app/files/ntTnEoxFXXDOm5fY.pdf
{"code":130,"error":"UnknownError"}

[NicolasDierick]

same thing on my side,

strange behaviour, seems that he request does'nt know what to do at all

It works with "USE_LOCAL" "true", but on my side, I can't deploy a persistent volume and need to work with Bucket.

@andrew-opensignlabs Do you have the same issue with a bucket ?

[mrcleanandfresh]

I'm having the same issue when trying to upload a new template.

https://{my public domain}/api/app/files/x3ECLqNq4II99MON.pdf

POST 400 Bad Request {"code":130,"error":"UnknownError"}

I'm also using Docker Compose and S3. Same Server logs. My config is:

DO_SPACE=bucket-name
DO_ENDPOINT=s3.us-east-1.amazonaws.com
DO_BASEURL=https://bucket-name.s3.us-east-1.amazonaws.com
DO_ACCESS_KEY_ID=access key
DO_SECRET_ACCESS_KEY=secret
DO_REGION=us-east-1
USE_LOCAL=false

When I saw this error I was trying to upload a new PDF template document.

I don't know if this is significant or not, but I noted when trying to upload a PDF it had the correct content type in the payload:

_ContentType: "application/pdf"

I thought maybe I couldn't upload PDFs, so I considered another MIME type that might work. I tried uploading a random PNG, but it failed again with the same error. However, the content type still indicated it was a PDF. Curious. Does it attempt to convert any provided content to a PDF for this endpoint? For example, if I had a scan and provided it as my document, is it trying to convert that to a PDF format before sending it off?

Then wondered if just this portion of the app is broken with uploading. So I tried replacing the default profile picture with a random PNG, but it failed with the same error:

POST 400 Bad Request {"code":130,"error":"UnknownError"}

But this time, I noted the MIME type was correct:

_ContentType: "image/png"

Curious that when uploading a template document, it seems to be "stuck" on application/pdf.

Regardless of that fact, multiple endpoints are not allowing me to upload and are failing with the same error. I'll happily provide any debug logs if I can get some guidance on changing the logging level.

[donny26utama]

yeah same on me. I named my minio service as "minio.service".
so in .env file "DO_ENDPOINT=http://minio.service:9000" but it doesn't work if "DO_SPACE" not blank. error will be raise like this, "NOTFOUND opensign.minio.service" if I fill "DO_SPACE=opensign"

[EDIflyer]

Same issue here - had to nuke my install recently and get it going again but getting the same 400 error for S3. Nothing in OpenSign or OpenSignServer logs but same console error.

[mrcleanandfresh]

@andrew-opensignlabs, it appears that this is a serious and widespread issue that has been ongoing for two months now. Have you made any progress on a fix? Would you like some help? If you point me to the contribution documentation, I can get up and running locally and see what I can find.

[andrew-opensignlabs]

You can find the detailed steps to setup AWS S3 storage here.

[EDIflyer]

@andrew-opensignlabs have there been any changes to the steps/requirements? It used to work fine for me but now has the errors above.