Cloudron Forum

@pavelalonso you have an invalid Timestamp URL provided - removing Timestamp server URL should fix the download/signing

@girish in the latest 1.6.2 app version there is a new dependency introduced - redis-server which also should be installed here: https://git.cloudron.io/cloudron/docuseal-app/-/blob/main/Dockerfile?ref_type=heads#L10

@jfrere can you please forward that email to security@docuseal.co to see if it can be somehow linked to the DocuSeal hosted on Cloudron ?

@girish could we add this package to have it fixed in the next release?

@chetbaker @girish it has been fixed in the upstream repo

https://git.cloudron.io/cloudron/docuseal-app/-/blob/main/Dockerfile?ref_type=heads#L10

apt-get install -y poppler-utils package should be added here in order to render documents with 15+ pages (the app uses pdftocairo cli util to generate page images previews for large pdf files)

@avatar1024 this issue has been fixed in the latest version:
https://github.com/docusealco/docuseal/commit/7b15111e8f2f202f5fffdbcf445517dd92d1e533

@girish autogenerated secret is stored in the docuseal.env file in the code folder by default.
Also the root code folder contains attachments folder with all files ever uploaded to the app.
Maybe a better solution would be to use WORKDIR=/app/data to store .env file and attached files there ?
It feels like generating a secret key base in the start.sh is not necessary since the app does that already.

@girish https://git.cloudron.io/cloudron/docuseal-app/-/commit/40dbb6272dae9bdad11b8bd13f3032aadc25b86f#9dcf658ee8180c343527e6fa4612975d22036004_7_10

I think this line breaks DocuSeal for existing users. At DocuSeal secret key base is automatically generated by the app itself on the first run. With this new update a new key has been generated for users and so the old data that seats in the DB can't be decrypted with that new key.

Btw DocuSeal accept WORKDIR= env variable to specify where the app data should be stored (possibly /app/data ?) But setting this variable without moving all the data to a new folder will also break the app for existing users.

@lukas @nichu42 OPT should work - you just need to wait 60 seconds to get a new code to sign in (the same code you used to set up OTP wont work on the sign in form)