starred/documenso

Fork 0

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

[GH-ISSUE #2293] Unable to sign PDF files despite a valid certificate #653

New issue

Closed

opened 2026-02-26 18:47:55 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @techsupportkoeln on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2293

Issue Description

I used the following guide https://github.com/documenso/documenso/issues/1892 to create the certificate. When starting Documenso, it indicates that the certificate is valid. However, PDF files still cannot be signed. I am getting the following error in the Docker logs.

documenso-1 | [JOBS:task-5cf8e8c4afcbf1e962c0efd6d5fbedb388db34051291cb5429d917fc5be56381--cmiuo7ep50017m924i0yo7u45] Task failed TypeError: fetch failed documenso-1 | at node:internal/deps/undici/undici:13510:13 documenso-1 | at process.processTicksAndRejections (node:internal/process/task_queues:105:5) documenso-1 | at async flattenForm (file:///app/apps/remix/build/server/hono/packages/lib/server-only/pdf/flatten-form.js:15:20) documenso-1 | at async decorateAndSignPdf (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:254:3) documenso-1 | at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:146:22 documenso-1 | at async Object.runTask (file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:204:26) documenso-1 | at async Module.run (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:47:7) documenso-1 | at async Object.handler (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.js:26:5) documenso-1 | at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:101:9 documenso-1 | at async dispatch (file:///app/node_modules/hono/dist/compose.js:22:17) { documenso-1 | [cause]: Error: certificate has expired documenso-1 | at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34) documenso-1 | at TLSSocket.emit (node:events:518:28) documenso-1 | at TLSSocket._finishInit (node:_tls_wrap:1078:8) documenso-1 | at ssl.onhandshakedone (node:_tls_wrap:864:12) documenso-1 | at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) { documenso-1 | code: 'CERT_HAS_EXPIRED'

Docker Log from the start sequenz:

`🚀 Starting Documenso...

🔐 Checking certificate configuration...
✅ Certificate file found and readable - document signing is ready!

📚 Useful Links:
📖 Documentation: https://docs.documenso.com
🐳 Self-hosting guide: https://docs.documenso.com/developers/self-hosting
🔐 Certificate setup: https://docs.documenso.com/developers/self-hosting/signing-certificate
🏥 Health check: http://localhost:3000/api/health
📊 Certificate status: http://localhost:3000/api/certificate-status
👥 Community: https://github.com/documenso/documenso

🗄️ Running database migrations...
Prisma schema loaded from ../../packages/prisma/schema.prisma
Datasource "db": PostgreSQL database "documenso", schema "public" at "database:5432"

144 migrations found in prisma/migrations

No pending migrations to apply.
🌟 Starting Documenso server...
[Telemetry] Telemetry is enabled. Documenso collects anonymous usage data to help improve the product.
[Telemetry] We collect: app version, installation ID, and node ID. No personal data, document contents, or user information is collected.
[Telemetry] To disable telemetry, set DOCUMENSO_DISABLE_TELEMETRY=true in your environment variables.
[Telemetry] Learn more: https://documenso.com/docs/developers/self-hosting/telemetry`

Steps to Reproduce

Create the document, both parties sign the document.

Expected Behavior

After both parties have signed, the PDF document should be digitally signed.

Current Behavior

After both parties have signed, a window opens stating that the PDF file is currently being signed. Nothing else happens after that.

Screenshots (optional)

Operating System [e.g., Windows 10]

Ubuntu 24.04

Browser [e.g., Chrome, Firefox]

Brave

Version [e.g., 2.0.1]

Documenso 2.2.4

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 @techsupportkoeln on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2293 ### Issue Description I used the following guide https://github.com/documenso/documenso/issues/1892 to create the certificate. When starting Documenso, it indicates that the certificate is valid. However, PDF files still cannot be signed. I am getting the following error in the Docker logs. `documenso-1 | [JOBS:task-5cf8e8c4afcbf1e962c0efd6d5fbedb388db34051291cb5429d917fc5be56381--cmiuo7ep50017m924i0yo7u45] Task failed TypeError: fetch failed documenso-1 | at node:internal/deps/undici/undici:13510:13 documenso-1 | at process.processTicksAndRejections (node:internal/process/task_queues:105:5) documenso-1 | at async flattenForm (file:///app/apps/remix/build/server/hono/packages/lib/server-only/pdf/flatten-form.js:15:20) documenso-1 | at async decorateAndSignPdf (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:254:3) documenso-1 | at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:146:22 documenso-1 | at async Object.runTask (file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:204:26) documenso-1 | at async Module.run (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:47:7) documenso-1 | at async Object.handler (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.js:26:5) documenso-1 | at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:101:9 documenso-1 | at async dispatch (file:///app/node_modules/hono/dist/compose.js:22:17) { documenso-1 | [cause]: Error: certificate has expired documenso-1 | at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34) documenso-1 | at TLSSocket.emit (node:events:518:28) documenso-1 | at TLSSocket._finishInit (node:_tls_wrap:1078:8) documenso-1 | at ssl.onhandshakedone (node:_tls_wrap:864:12) documenso-1 | at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) { documenso-1 | code: 'CERT_HAS_EXPIRED'` Docker Log from the start sequenz: `🚀 Starting Documenso... 🔐 Checking certificate configuration... ✅ Certificate file found and readable - document signing is ready! 📚 Useful Links: 📖 Documentation: https://docs.documenso.com 🐳 Self-hosting guide: https://docs.documenso.com/developers/self-hosting 🔐 Certificate setup: https://docs.documenso.com/developers/self-hosting/signing-certificate 🏥 Health check: http://localhost:3000/api/health 📊 Certificate status: http://localhost:3000/api/certificate-status 👥 Community: https://github.com/documenso/documenso 🗄️ Running database migrations... Prisma schema loaded from ../../packages/prisma/schema.prisma Datasource "db": PostgreSQL database "documenso", schema "public" at "database:5432" 144 migrations found in prisma/migrations No pending migrations to apply. 🌟 Starting Documenso server... [Telemetry] Telemetry is enabled. Documenso collects anonymous usage data to help improve the product. [Telemetry] We collect: app version, installation ID, and node ID. No personal data, document contents, or user information is collected. [Telemetry] To disable telemetry, set DOCUMENSO_DISABLE_TELEMETRY=true in your environment variables. [Telemetry] Learn more: https://documenso.com/docs/developers/self-hosting/telemetry` ### Steps to Reproduce Create the document, both parties sign the document. ### Expected Behavior After both parties have signed, the PDF document should be digitally signed. ### Current Behavior After both parties have signed, a window opens stating that the PDF file is currently being signed. Nothing else happens after that. ### Screenshots (optional) <img width="1761" height="1130" alt="Image" src="https://github.com/user-attachments/assets/c34eeb48-4e9d-4c06-be1d-553aa86cd95a" /> ### Operating System [e.g., Windows 10] Ubuntu 24.04 ### Browser [e.g., Chrome, Firefox] Brave ### Version [e.g., 2.0.1] Documenso 2.2.4 ### 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. - [ ] I want to work on creating a PR for this issue if approved

kerem

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

closed this issue
added the
status: triage
label

kerem commented

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

Author

Owner

@techsupportkoeln commented on GitHub (Dec 8, 2025):

with Version 2.2.5 the problem is solved.

@techsupportkoeln commented on GitHub (Dec 8, 2025): with Version 2.2.5 the problem is solved.

kerem referenced this issue

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

[PR #653] [MERGED] chore: remove share button from top level, texts #1101

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

No description provided.

Rows
Columns