starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1720] Error: "Create document is not available without S3 transport." #492

New issue

Open

opened 2026-02-26 18:47:16 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:47:16 +03:00

Owner

Originally created by @Intern621 on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1720

Hi,

I have successfully set up a self-hosted instance of Documenso using Docker. However, when I attempt to create a document via the API, I receive the following error:

I understand that PostgreSQL is used for storing metadata while document files require S3-compatible storage. However, I would like clarification on whether:

It is possible to create and store documents without configuring S3.
There are alternative storage options for local file handling instead of an S3 bucket.
Any specific environment variables need to be set to enable local storage.

Here is my current setup:

Hosting: Self-hosted on Ubuntu
Deployment: Docker + PostgreSQL
API Request: POST /api/v1/documents

Any guidance on resolving this issue would be greatly appreciated. Thank you!

Originally created by @Intern621 on GitHub (Mar 22, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1720 Hi, I have successfully set up a self-hosted instance of Documenso using Docker. However, when I attempt to create a document via the API, I receive the following error: ![Image](https://github.com/user-attachments/assets/2ccc7802-bc7d-4330-a439-26f0a278f98c) I understand that PostgreSQL is used for storing metadata while document files require S3-compatible storage. However, I would like clarification on whether: 1. It is possible to create and store documents without configuring S3. 2. There are alternative storage options for local file handling instead of an S3 bucket. 3. Any specific environment variables need to be set to enable local storage. Here is my current setup: - Hosting: Self-hosted on Ubuntu - Deployment: Docker + PostgreSQL - API Request: POST /api/v1/documents Any guidance on resolving this issue would be greatly appreciated. Thank you!

kerem added the

status: triage

label

2026-02-26 18:47:16 +03:00

kerem commented

2026-02-26 18:47:17 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 22, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Mar 22, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:17 +03:00

Author

Owner

@AtumG commented on GitHub (Mar 30, 2025):

@Intern621 I'm not a maintainer or contributor to the project at this time but I think I can help here.

Yes, internal storage is possible, I'm actually using it and trying to migrate to S3 which is how I ended up here
Be sure that you're not setting the NEXT_PUBLIC_UPLOAD_TRANSPORT .env var
I'm currently toggling this variable in my .env file via comment to switch between local and S3 transport

NEXT_PUBLIC_UPLOAD_TRANSPORT=s3
vs
#NEXT_PUBLIC_UPLOAD_TRANSPORT=s3

@AtumG commented on GitHub (Mar 30, 2025): @Intern621 I'm not a maintainer or contributor to the project at this time but I think I can help here. 1. Yes, internal storage is possible, I'm actually using it and trying to migrate to S3 which is how I ended up here 2. Be sure that you're not setting the `NEXT_PUBLIC_UPLOAD_TRANSPORT` .env var 3. I'm currently toggling this variable in my .env file via comment to switch between local and S3 transport `NEXT_PUBLIC_UPLOAD_TRANSPORT=s3` vs `#NEXT_PUBLIC_UPLOAD_TRANSPORT=s3`

kerem commented

2026-02-26 18:47:17 +03:00

Author

Owner

@Muntasir2001 commented on GitHub (Aug 1, 2025):

Hey @AtumG

Did you manage to get documenso working with S3 (Minio)?

If so, could you please share how you have done it

Thanks

@Muntasir2001 commented on GitHub (Aug 1, 2025): Hey @AtumG Did you manage to get documenso working with S3 (Minio)? If so, could you please share how you have done it Thanks

kerem commented

2026-02-26 18:47:17 +03:00

Author

Owner

@Muntasir2001 commented on GitHub (Aug 1, 2025):

I have been facing the same issue as @Intern621

Document upload doesn't seem to be available without configuring S3 storage

A bit off topic but the thing is, when I configure minio with documenso, it doesn't seem to work.

I am selfhosting Documenso and minio. I have set NEXT_PRIVATE_UPLOAD_ENDPOINT to http://minio:3000.

@Muntasir2001 commented on GitHub (Aug 1, 2025): I have been facing the same issue as @Intern621 Document upload doesn't seem to be available without configuring S3 storage A bit off topic but the thing is, when I configure minio with documenso, it doesn't seem to work. I am selfhosting Documenso and minio. I have set `NEXT_PRIVATE_UPLOAD_ENDPOINT` to `http://minio:3000`.

kerem commented

2026-02-26 18:47:17 +03:00

Author

Owner

@robelest commented on GitHub (Aug 13, 2025):

any progress made with this? Ive running to the same problem

in the code base: https://github.com/documenso/documenso/blob/main/packages/api/v1/implementation.ts
this feels like a weird check considering this feature works fine on the UI

     if (process.env.NEXT_PUBLIC_UPLOAD_TRANSPORT !== 's3') {
        return {
          status: 500,
          body: {
            message: 'Create document is not available without S3 transport.',
          },
        };
      }

downloadSignedDocument()
createDocument()
createTemplate()

all run some version of this check

@robelest commented on GitHub (Aug 13, 2025): any progress made with this? Ive running to the same problem in the code base: https://github.com/documenso/documenso/blob/main/packages/api/v1/implementation.ts this feels like a weird check considering this feature works fine on the UI ``` if (process.env.NEXT_PUBLIC_UPLOAD_TRANSPORT !== 's3') { return { status: 500, body: { message: 'Create document is not available without S3 transport.', }, }; } ``` `downloadSignedDocument()` `createDocument()` `createTemplate()` all run some version of this check

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#492

No description provided.

Rows
Columns