starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Updating Documenso using "update" deletes your existing signing certs #1706

New Issue
Closed
opened 2026-02-05 02:02:05 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 02:02:05 +03:00
Owner
Copy Link

Originally created by @samwathegreat on GitHub (Oct 1, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Documenso

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9

📝 Provide a clear and concise description of the issue.

If you update a working documenso lxc, it deletes the signing certs in /opt/documenso

I had to restore my backup, use SCP to copy over my certs, update, then copy the certs back to /opt/documenso

🔄 Steps to reproduce the issue.

type 'update' into an existing, working documenso instance that already has signing certs installed. If the certs are in /opt/documenso, it will delete them.

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

Existing signing certificates should be retained. Simply updating should not have nuked the certs.

The .env file, which was also located in /opt/documenso was unaffected and still contained the path to the (now missing) signing certs.

Originally created by @samwathegreat on GitHub (Oct 1, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Documenso ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9 ### 📝 Provide a clear and concise description of the issue. If you update a working documenso lxc, it deletes the signing certs in /opt/documenso I had to restore my backup, use SCP to copy over my certs, update, then copy the certs back to /opt/documenso ### 🔄 Steps to reproduce the issue. type 'update' into an existing, working documenso instance that already has signing certs installed. If the certs are in /opt/documenso, it will delete them. ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). Existing signing certificates should be retained. Simply updating should not have nuked the certs. The .env file, which was also located in /opt/documenso was unaffected and still contained the path to the (now missing) signing certs.
OVERLORD added the bug label 2026-02-05 02:02:05 +03:00
OVERLORD commented 2026-02-05 02:02:13 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 1, 2025):

Can you please tell us where are we making/setting the certificates?

@tremor021 commented on GitHub (Oct 1, 2025): Can you please tell us where are we making/setting the certificates?
OVERLORD commented 2026-02-05 02:02:17 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 1, 2025):

Can you please tell us where are we making/setting the certificates?

You have to create the certificates manually and reference their location in the .env file: https://docs.documenso.com/developers/local-development/signing-certificate

@samwathegreat commented on GitHub (Oct 1, 2025): > Can you please tell us where are we making/setting the certificates? You have to create the certificates manually and reference their location in the .env file: https://docs.documenso.com/developers/local-development/signing-certificate
OVERLORD commented 2026-02-05 02:02:21 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 1, 2025):

Why do you Store certs in this dir? The App will full cleaned at every Update, otherwise you get massive Node Issues

@MickLesk commented on GitHub (Oct 1, 2025): Why do you Store certs in this dir? The App will full cleaned at every Update, otherwise you get massive Node Issues
OVERLORD commented 2026-02-05 02:02:24 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 1, 2025):

Seemed like a good place to store them -- that is where the .env file is. Where do you suggest we put them? There is no instruction on where specifically to put them. Let me know and I'll move them and update path in .env

@samwathegreat commented on GitHub (Oct 1, 2025): Seemed like a good place to store them -- that is where the .env file is. Where do you suggest we put them? There is no instruction on where specifically to put them. Let me know and I'll move them and update path in .env
OVERLORD commented 2026-02-05 02:02:27 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 1, 2025):

/etc/ssl/certs/ for .crt file
/etc/ssl/private for .key file

Set right permissions and you're all set

@tremor021 commented on GitHub (Oct 1, 2025): /etc/ssl/certs/ for .crt file /etc/ssl/private for .key file Set right permissions and you're all set
OVERLORD commented 2026-02-05 02:02:29 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 1, 2025):

/etc/ssl/certs/ for .crt file /etc/ssl/private for .key file

Set right permissions and you're all set

I've moved the files and updated .env, so hopefully this won't happen on the next update. Thanks!

@samwathegreat commented on GitHub (Oct 1, 2025): > /etc/ssl/certs/ for .crt file /etc/ssl/private for .key file > > Set right permissions and you're all set I've moved the files and updated .env, so hopefully this won't happen on the next update. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1706
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?