[GH-ISSUE #1651] Signed Document Shows 'Uncompleted' #464

Closed
opened 2026-02-26 18:47:09 +03:00 by kerem · 7 comments
Owner

Originally created by @codersboutique on GitHub (Feb 17, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1651

Issue Description

after both people signed it still says the uncompleted but the hover over pop-up says signed.

also, the view button is disable and not able to click. i would like to download the signed pdf now but not able to do. what am i missing?

Steps to Reproduce

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

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 @codersboutique on GitHub (Feb 17, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1651 ### Issue Description after both people signed it still says the uncompleted but the hover over pop-up says signed. also, the view button is disable and not able to click. i would like to download the signed pdf now but not able to do. what am i missing? ### Steps to Reproduce ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### 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. - [ ] I have provided steps to reproduce the issue. - [ ] I have included relevant environment information. - [x] 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
kerem 2026-02-26 18:47:09 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 17, 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:2662286796 --> @github-actions[bot] commented on GitHub (Feb 17, 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

@ephraimduncan commented on GitHub (Feb 18, 2025):

Are you running it locally? or its selfhosted?

<!-- gh-comment-id:2666187394 --> @ephraimduncan commented on GitHub (Feb 18, 2025): Are you running it locally? or its selfhosted?
Author
Owner

@tankerkiller125 commented on GitHub (Feb 27, 2025):

Doing some digging, it seems that the frontend isn't showing any errors, but in the backend the signing is actually failing. In my case the it's not reading the private key for some reason (despite it working fine on previous versions)

<!-- gh-comment-id:2686687192 --> @tankerkiller125 commented on GitHub (Feb 27, 2025): Doing some digging, it seems that the frontend isn't showing any errors, but in the backend the signing is actually failing. In my case the it's not reading the private key for some reason (despite it working fine on previous versions)
Author
Owner

@codersboutique commented on GitHub (Feb 27, 2025):

Are you running it locally? or its selfhosted?

selfhosted on docker

<!-- gh-comment-id:2687158983 --> @codersboutique commented on GitHub (Feb 27, 2025): > Are you running it locally? or its selfhosted? selfhosted on docker
Author
Owner

@codersboutique commented on GitHub (Feb 27, 2025):

Doing some digging, it seems that the frontend isn't showing any errors, but in the backend the signing is actually failing. In my case the it's not reading the private key for some reason (despite it working fine on previous versions)

i think the cert keys are not properly installed :(

<!-- gh-comment-id:2687161183 --> @codersboutique commented on GitHub (Feb 27, 2025): > Doing some digging, it seems that the frontend isn't showing any errors, but in the backend the signing is actually failing. In my case the it's not reading the private key for some reason (despite it working fine on previous versions) i think the cert keys are not properly installed :(
Author
Owner

@Novapixel1010 commented on GitHub (Oct 23, 2025):

Did you ever get this fixed. So far I got everything working, so I could share my config/process of setting it up. Also I thinks the docs have been updated

<!-- gh-comment-id:3438540713 --> @Novapixel1010 commented on GitHub (Oct 23, 2025): Did you ever get this fixed. So far I got everything working, so I could share my config/process of setting it up. Also I thinks the docs have been updated
Author
Owner

@codersboutique commented on GitHub (Oct 24, 2025):

i used cursor later and it fixed for me. forgot to update here!

<!-- gh-comment-id:3440873769 --> @codersboutique commented on GitHub (Oct 24, 2025): i used cursor later and it fixed for me. forgot to update here!
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#464
No description provided.