starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

[GH-ISSUE #2374] Signing Links sometimes redirect to a 404 Error #667

New issue

Closed

opened 2026-02-26 18:47:59 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @KarloDerEchte on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/documenso/documenso/issues/2374

Issue Description

Sometimes when a User is trying to sign a Document he is getting a 404 Error when opening the Signing Link.

The fix is to set the Email of the Recipiant to a random non existant email and than back to the signers email, seems like the Signing link gets regenerated than.

Steps to Reproduce

Currently i dont really know how to reproduce this issue, it happens randomly. 3x in the last 2-3 Months.

Expected Behavior

No 404 Error

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome,Edge

Version [e.g., 2.0.1]

2.4.0

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 @KarloDerEchte on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/documenso/documenso/issues/2374 ### Issue Description Sometimes when a User is trying to sign a Document he is getting a 404 Error when opening the Signing Link. The fix is to set the Email of the Recipiant to a random non existant email and than back to the signers email, seems like the Signing link gets regenerated than. ### Steps to Reproduce Currently i dont really know how to reproduce this issue, it happens randomly. 3x in the last 2-3 Months. ### Expected Behavior No 404 Error ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome,Edge ### Version [e.g., 2.0.1] 2.4.0 ### 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:47:59 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@KarloDerEchte commented on GitHub (Jan 12, 2026):

Please note, im still try to find out how to reproduce the issue. I opened this issue here as early as possible to see if other users have the same problem as well or if its limited to my environment only

@KarloDerEchte commented on GitHub (Jan 12, 2026): Please note, im still try to find out how to reproduce the issue. I opened this issue here as early as possible to see if other users have the same problem as well or if its limited to my environment only

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@KarloDerEchte commented on GitHub (Jan 19, 2026):

Had a new case with the same Problem today again, thats how the DB Entry looks like

Seems normal for me, but when i try to search for the token i cant get the entry in the database only via the envelope_id...

I decided to set the token to a random token, copy the old token into the editor and than put it back into the DB and than it started to work. It seems like there has been some kind of formatting error...

@KarloDerEchte commented on GitHub (Jan 19, 2026): Had a new case with the same Problem today again, thats how the DB Entry looks like <img width="1780" height="116" alt="Image" src="https://github.com/user-attachments/assets/b2ff9bba-47f5-41ff-ad44-84a6d3542062" /> Seems normal for me, but when i try to search for the token i cant get the entry in the database only via the envelope_id... I decided to set the token to a random token, copy the old token into the editor and than put it back into the DB and than it started to work. It seems like there has been some kind of formatting error...

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@KarloDerEchte commented on GitHub (Jan 26, 2026):

After some investigation we found out that this issue was likely due to a collation version mismatch, after correcting i have been able to find the key inside the database and the user could see the signing page.

We will let this issue open for 1-2 Weeks to see if it happens again but for now it looks good.

@KarloDerEchte commented on GitHub (Jan 26, 2026): After some investigation we found out that this issue was likely due to a collation version mismatch, after correcting i have been able to find the key inside the database and the user could see the signing page. We will let this issue open for 1-2 Weeks to see if it happens again but for now it looks good.

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@KarloDerEchte commented on GitHub (Feb 4, 2026):

Issue didnt reoccur, closing this ticket

@KarloDerEchte commented on GitHub (Feb 4, 2026): Issue didnt reoccur, closing this ticket

kerem referenced this issue

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

[PR #667] [MERGED] #666 feat: disabled resend button for recipients #1111

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

No description provided.

Rows
Columns