starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #1048] S3 storage Path #317

New issue

Closed

opened 2026-02-26 18:46:28 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:46:28 +03:00

Owner

Originally created by @Hexcah on GitHub (Mar 22, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1048

Originally assigned to: @Hexcah on GitHub.

Issue Description

Hi,
I'm testing Documenso on Docker, but I have a problem with S3 storage,
I have a minio in version 2023-03-24T21:41:23Z And when I try to upload a document via Documenso, I get an error, because it points to https://documenso.minio.domain.com/3/xxxxxxxxxxxx/my-pdf.pdf instead of something like https://minio.domain.com/documenso/xxxxxxxxxxxx/my-pdf.pdf (documenso is my bucket name).
Can you enlighten me a little here?

Steps to Reproduce

Production docker compose, image: documenso/documenso:v1.5.3-rc.1
S3 Storage, minio 2023-03-24T21:41:23Z

# [[STORAGE]]
# OPTIONAL: Defines the storage transport to use. Available options: database (default) | s3
NEXT_PUBLIC_UPLOAD_TRANSPORT="s3"
# OPTIONAL: Defines the endpoint to use for the S3 storage transport. Relevant when using third-party S3-compatible providers.
NEXT_PRIVATE_UPLOAD_ENDPOINT="https://minio.domain.com"
# OPTIONAL: Defines the region to use for the S3 storage transport. Defaults to us-east-1.
NEXT_PRIVATE_UPLOAD_REGION="unknown" # Not set in Minio
# REQUIRED: Defines the bucket to use for the S3 storage transport.
NEXT_PRIVATE_UPLOAD_BUCKET="documenso"
# OPTIONAL: Defines the access key ID to use for the S3 storage transport.
NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID="xxxxxxxxxxx"
# OPTIONAL: Defines the secret access key to use for the S3 storage transport.
NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Expected Behavior

Being able to change bucket_name/URL order? 🥲

Current Behavior

Can't

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Linux Mint 21.3

Browser [e.g., Chrome, Firefox]

Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0

Version [e.g., 2.0.1]

v1.5.3-rc.1

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @Hexcah on GitHub (Mar 22, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1048 Originally assigned to: @Hexcah on GitHub. ### Issue Description Hi, I'm testing Documenso on Docker, but I have a problem with S3 storage, I have a minio in version `2023-03-24T21:41:23Z` And when I try to upload a document via Documenso, I get an error, because it points to https://documenso.minio.domain.com/3/xxxxxxxxxxxx/my-pdf.pdf instead of something like https://minio.domain.com/documenso/xxxxxxxxxxxx/my-pdf.pdf (documenso is my bucket name). Can you enlighten me a little here? ### Steps to Reproduce Production docker compose, `image: documenso/documenso:v1.5.3-rc.1` S3 Storage, minio `2023-03-24T21:41:23Z` ```bash # [[STORAGE]] # OPTIONAL: Defines the storage transport to use. Available options: database (default) | s3 NEXT_PUBLIC_UPLOAD_TRANSPORT="s3" # OPTIONAL: Defines the endpoint to use for the S3 storage transport. Relevant when using third-party S3-compatible providers. NEXT_PRIVATE_UPLOAD_ENDPOINT="https://minio.domain.com" # OPTIONAL: Defines the region to use for the S3 storage transport. Defaults to us-east-1. NEXT_PRIVATE_UPLOAD_REGION="unknown" # Not set in Minio # REQUIRED: Defines the bucket to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_BUCKET="documenso" # OPTIONAL: Defines the access key ID to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID="xxxxxxxxxxx" # OPTIONAL: Defines the secret access key to use for the S3 storage transport. NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ``` ### Expected Behavior Being able to change bucket_name/URL order? 🥲 ### Current Behavior Can't ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Linux Mint 21.3 ### Browser [e.g., Chrome, Firefox] Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 ### Version [e.g., 2.0.1] v1.5.3-rc.1 ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [x] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:28 +03:00

closed this issue
added the
type: bug

status: assigned
labels

kerem commented

2026-02-26 18:46:29 +03:00

Author

Owner

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

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, 2024): 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:46:29 +03:00

Author

Owner

@elosi commented on GitHub (Mar 22, 2024):

👍

@elosi commented on GitHub (Mar 22, 2024): :+1:

kerem commented

2026-02-26 18:46:29 +03:00

Author

Owner

@Hexcah commented on GitHub (Mar 22, 2024):

Perhaps to look at the aws-sdk/client-s3 library and the s3ForcePathStyle parameter?

@Hexcah commented on GitHub (Mar 22, 2024): Perhaps to look at the `aws-sdk/client-s3` library and the `s3ForcePathStyle` parameter?

kerem commented

2026-02-26 18:46:29 +03:00

Author

Owner

@Hexcah commented on GitHub (Mar 27, 2024):

Thanks for the speed, it works perfectly 👌

@Hexcah commented on GitHub (Mar 27, 2024): Thanks for the speed, it works perfectly 👌

kerem commented

2026-02-26 18:46:29 +03:00

Author

Owner

@jasjastone commented on GitHub (Mar 14, 2025):

Hello @Mythie
Sorry to bother you, but am running minio on localhost(docker to be specific) and the end point URL is http://192.168.1.149:9000 the ip is the ip of my local computer and minio is accessible on the web and i have created a bucket name documenson but in documenson doesn't seems to work

here is the example request to http://localhost:3000/api/v1/documents
{
"title": "Testing title",
"externalId": "1234",
"recipients": [
{
"name": "James",
"email": "james@example.com",
"role": "SIGNER"
},
{
"name": "Stivie",
"email": "stivie@example.com",
"role": "SIGNER"
}
],
"meta": {
"subject": "Testing",
"message": "Test docu",
"timezone": "Etc/UTC",
"redirectUrl": "http://127.0.0.1:8000/app/sign-request",
"signingOrder": "PARALLEL"
},
"authOptions": {
"globalAccessAuth": "ACCOUNT",
"globalActionAuth": "ACCOUNT"
},
"formValues": {}
}
return this response

{
"message": "An error has occured while uploading the file"
}
here is the documenson variables for s3 on env
"NEXT_PUBLIC_UPLOAD_TRANSPORT=s3",
"NEXT_PRIVATE_UPLOAD_ENDPOINT=http://192.168.1.149:9000",
"NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE=true",
I haven't set region on minio so i put this based on your example on the PR_
"NEXT_PRIVATE_UPLOAD_REGION=unknown",
"NEXT_PRIVATE_UPLOAD_BUCKET=documenso",
"NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID=documenson@123",
"NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY=documenson@123",

Your guidance is appreciated

@jasjastone commented on GitHub (Mar 14, 2025): Hello @Mythie Sorry to bother you, but am running minio on localhost(docker to be specific) and the end point URL is http://192.168.1.149:9000 the ip is the ip of my local computer and minio is accessible on the web and i have created a bucket name documenson but in documenson doesn't seems to work here is the example request to **http://localhost:3000/api/v1/documents** { "title": "Testing title", "externalId": "1234", "recipients": [ { "name": "James", "email": "james@example.com", "role": "SIGNER" }, { "name": "Stivie", "email": "stivie@example.com", "role": "SIGNER" } ], "meta": { "subject": "Testing", "message": "Test docu", "timezone": "Etc/UTC", "redirectUrl": "http://127.0.0.1:8000/app/sign-request", "signingOrder": "PARALLEL" }, "authOptions": { "globalAccessAuth": "ACCOUNT", "globalActionAuth": "ACCOUNT" }, "formValues": {} } return this response { "message": "An error has occured while uploading the file" } here is the documenson variables for s3 on env "NEXT_PUBLIC_UPLOAD_TRANSPORT=s3", "NEXT_PRIVATE_UPLOAD_ENDPOINT=http://192.168.1.149:9000", "NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE=true", I haven't set region on minio so i put this based on your example on the PR_ "NEXT_PRIVATE_UPLOAD_REGION=unknown", "NEXT_PRIVATE_UPLOAD_BUCKET=documenso", "NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID=documenson@123", "NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY=documenson@123", Your guidance is appreciated

kerem referenced this issue

2026-02-26 19:30:54 +03:00

[PR #337] [MERGED] feat: add command menu and keyboard shortcuts #890

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#317

No description provided.

Rows
Columns