[GH-ISSUE #1807] internal.sealdocument fails with "Unknown font format" #520

Open
opened 2026-02-26 18:47:25 +03:00 by kerem · 2 comments
Owner

Originally created by @CallMeSteve297 on GitHub (May 21, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1807

Issue Description

When I create a document to sign, with a single signer and a single "CC only" (not sure if that's relevant) and send off the document, upon the signer completing the document, I get an infinite "Pending" with "Waiting on 0 recipients". Docker logs return the following:

[JOBS]: Triggering job internal.seal-document with payload {
  documentId: 4,
  requestMetadata: {
    ipAddress: '<redacted>',
    userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36 Edg/135.0.0.0'
  }
}
[JOBS:task-06292354c47ced55f2e4d03bfb7e63bc9b46a8180d6f46eb02d23d3ebb8b8a45--cmayepmi9003fv18xs64bcg0l] Task failed Error: Unknown font format
    at Object.create (/app/node_modules/@pdf-lib/fontkit/dist/fontkit.umd.js:17842:12)
    at Function.<anonymous> (/app/node_modules/pdf-lib/cjs/core/embedders/CustomFontEmbedder.js:39:58)
    at step (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:141:27)
    at Object.next (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:122:57)
    at /app/node_modules/pdf-lib/node_modules/tslib/tslib.js:115:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:111:16)
    at CustomFontEmbedder.for (/app/node_modules/pdf-lib/cjs/core/embedders/CustomFontEmbedder.js:35:24)
    at PDFDocument.<anonymous> (/app/node_modules/pdf-lib/cjs/api/PDFDocument.js:883:79)
    at step (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:141:27)
[JOBS]: Job internal.seal-document failed BackgroundTaskFailedError: Task failed
    at Object.runTask (file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:231:17)
    at async Module.run (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:125:21)
    at async Object.handler (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.js:25:5)
    at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:101:9
    at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17)
    at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17)
    at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17)
    at async contextStorage2 (file:///app/node_modules/hono/dist/middleware/context-storage/index.js:6:5)
    at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17)
    at async file:///app/node_modules/hono/dist/hono-base.js:195:25
Submitting job to endpoint: http://localhost:3000/api/jobs/internal.seal-document/cmayepmi9003fv18xs64bcg0l

I checked through issues and found some stuff regarding the signing certificate, but I've followed all the requirements for that, including setting correct permissions, verifying mapping location to docker, and setting a passphrase (both on the cert and in the env variables in docker-compose). The issue also very much points to a font issue.

Steps to Reproduce

Multiple documents, with different fonts inside the document, all return the same hanging. I'm currently at a 100% failure rate.

Expected Behavior

Upon signing, the document should change to completed and present the signers and other participants with the signed document.

Current Behavior

Nothing happens after signing, the signed document cannot be downloaded, it's forever "Pending"

Screenshots (optional)

Image

Operating System [e.g., Windows 10]

Debian 12 (running on Docker using official Docker Compose)

Browser [e.g., Chrome, Firefox]

Firefox & Edge

Version [e.g., 2.0.1]

I think docker image v1.11.1 (the latest one as of 21 May 2025)

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 @CallMeSteve297 on GitHub (May 21, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1807 ### Issue Description When I create a document to sign, with a single signer and a single "CC only" (not sure if that's relevant) and send off the document, upon the signer completing the document, I get an infinite "Pending" with "Waiting on 0 recipients". Docker logs return the following: ``` [JOBS]: Triggering job internal.seal-document with payload { documentId: 4, requestMetadata: { ipAddress: '<redacted>', userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36 Edg/135.0.0.0' } } [JOBS:task-06292354c47ced55f2e4d03bfb7e63bc9b46a8180d6f46eb02d23d3ebb8b8a45--cmayepmi9003fv18xs64bcg0l] Task failed Error: Unknown font format at Object.create (/app/node_modules/@pdf-lib/fontkit/dist/fontkit.umd.js:17842:12) at Function.<anonymous> (/app/node_modules/pdf-lib/cjs/core/embedders/CustomFontEmbedder.js:39:58) at step (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:141:27) at Object.next (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:122:57) at /app/node_modules/pdf-lib/node_modules/tslib/tslib.js:115:75 at new Promise (<anonymous>) at Object.__awaiter (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:111:16) at CustomFontEmbedder.for (/app/node_modules/pdf-lib/cjs/core/embedders/CustomFontEmbedder.js:35:24) at PDFDocument.<anonymous> (/app/node_modules/pdf-lib/cjs/api/PDFDocument.js:883:79) at step (/app/node_modules/pdf-lib/node_modules/tslib/tslib.js:141:27) [JOBS]: Job internal.seal-document failed BackgroundTaskFailedError: Task failed at Object.runTask (file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:231:17) at async Module.run (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.handler.js:125:21) at async Object.handler (file:///app/apps/remix/build/server/hono/packages/lib/jobs/definitions/internal/seal-document.js:25:5) at async file:///app/apps/remix/build/server/hono/packages/lib/jobs/client/local.js:101:9 at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17) at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17) at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17) at async contextStorage2 (file:///app/node_modules/hono/dist/middleware/context-storage/index.js:6:5) at async dispatch (file:///app/node_modules/hono/dist/compose.js:30:17) at async file:///app/node_modules/hono/dist/hono-base.js:195:25 Submitting job to endpoint: http://localhost:3000/api/jobs/internal.seal-document/cmayepmi9003fv18xs64bcg0l ``` I checked through issues and found some stuff regarding the signing certificate, but I've followed all the requirements for that, including setting correct permissions, verifying mapping location to docker, and setting a passphrase (both on the cert and in the env variables in docker-compose). The issue also very much points to a font issue. ### Steps to Reproduce Multiple documents, with different fonts inside the document, all return the same hanging. I'm currently at a 100% failure rate. ### Expected Behavior Upon signing, the document should change to completed and present the signers and other participants with the signed document. ### Current Behavior Nothing happens after signing, the signed document cannot be downloaded, it's forever "Pending" ### Screenshots (optional) <img width="525" alt="Image" src="https://github.com/user-attachments/assets/0ebd4efb-1670-4cbc-ab05-bc9506f0b60e" /> ### Operating System [e.g., Windows 10] Debian 12 (running on Docker using official Docker Compose) ### Browser [e.g., Chrome, Firefox] Firefox & Edge ### Version [e.g., 2.0.1] I think docker image v1.11.1 (the latest one as of 21 May 2025) ### 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
Author
Owner

@github-actions[bot] commented on GitHub (May 21, 2025):

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

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

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

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

@itfs-steve commented on GitHub (Sep 26, 2025):

Any update to this?

<!-- gh-comment-id:3338710904 --> @itfs-steve commented on GitHub (Sep 26, 2025): Any update to this?
Sign in to join this conversation.
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#520
No description provided.