starred/documenso

Fork 0

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

[GH-ISSUE #2002] Downloadable Certificate after signing is complete Don't get attached to email sent to the signers. #573

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Dvalin21 on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2002

I noticed that under "Preference" this setting by default is set to "Yes", however the certificate is not being sent or uploaded to the emails or being made part of the emails sent out to the signers. Logs didn't show any errors when the process come to "complete"

Originally created by @Dvalin21 on GitHub (Aug 27, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2002 I noticed that under "Preference" this setting by default is set to "Yes", however the certificate is not being sent or uploaded to the emails or being made part of the emails sent out to the signers. Logs didn't show any errors when the process come to "complete"

kerem

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

closed this issue
added the
status: triage
label

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Aug 27, 2025):

It is not sent separately, it is attached at the end of the document.

@ephraimduncan commented on GitHub (Aug 27, 2025): It is not sent separately, it is attached at the end of the document.

kerem commented

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

Author

Owner

@Dvalin21 commented on GitHub (Aug 27, 2025):

It is not sent separately, it is attached at the end of the document.

Yes, its suppose to be attached to the end of the document, but never does.

@Dvalin21 commented on GitHub (Aug 27, 2025): > It is not sent separately, it is attached at the end of the document. Yes, its suppose to be attached to the end of the document, but never does.

kerem commented

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

Author

Owner

@ephraimduncan commented on GitHub (Aug 27, 2025):

This is probably as a result of the chromium, the certificate generation fails because chromium isn't included in the container image.

You can add this to your docker compose

 browserless:
    image: browserless/chrome:latest
    ports:
      - "3001:3000"
    environment:
      - MAX_CONCURRENT_SESSIONS=10
      - MAX_QUEUE_LENGTH=20

Then set

NEXT_PRIVATE_BROWSERLESS_URL="ws://browserless:3000"

@ephraimduncan commented on GitHub (Aug 27, 2025): This is probably as a result of the chromium, the certificate generation fails because chromium isn't included in the container image. You can add this to your docker compose ```yml browserless: image: browserless/chrome:latest ports: - "3001:3000" environment: - MAX_CONCURRENT_SESSIONS=10 - MAX_QUEUE_LENGTH=20 ``` Then set ``` NEXT_PRIVATE_BROWSERLESS_URL="ws://browserless:3000" ```

kerem commented

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

Author

Owner

@Dvalin21 commented on GitHub (Aug 27, 2025):

This is probably as a result of the chromium, the certificate generation fails because chromium isn't included in the container image.

You can add this to your docker compose

browserless:
image: browserless/chrome:latest
ports:
- "3001:3000"
environment:
- MAX_CONCURRENT_SESSIONS=10
- MAX_QUEUE_LENGTH=20
Then set
NEXT_PRIVATE_BROWSERLESS_URL="ws://browserless:3000"

Thanks, Ill give it a try and late you know. Will this be apart of the next update?

@Dvalin21 commented on GitHub (Aug 27, 2025): > This is probably as a result of the chromium, the certificate generation fails because chromium isn't included in the container image. > > You can add this to your docker compose > > browserless: > image: browserless/chrome:latest > ports: > - "3001:3000" > environment: > - MAX_CONCURRENT_SESSIONS=10 > - MAX_QUEUE_LENGTH=20 > Then set > > ``` > NEXT_PRIVATE_BROWSERLESS_URL="ws://browserless:3000" > ``` Thanks, Ill give it a try and late you know. Will this be apart of the next update?

kerem commented

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

Author

Owner

@Dvalin21 commented on GitHub (Aug 28, 2025):

100% WORKED!!! Thanks for the update. Hope to see this in documentation.

@Dvalin21 commented on GitHub (Aug 28, 2025): 100% WORKED!!! Thanks for the update. Hope to see this in documentation.

kerem referenced this issue

2026-02-26 19:31:39 +03:00

[PR #575] [MERGED] fix: error invalid url on main page on self host #573 #1057

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

No description provided.

Rows
Columns