There is only one role: admin. Every user sees every document. There is no whitelabeling No Workflows No conditionals No API A counter on the anonymous start page shows how many documents have been signed with DocuSeal in this instance. All in all, a lot of features that people are interested in. Shame on them that the problem can't be solved by spending money and getting a key/file/license to enable these features on the Floss instance.

Hi everyone, Thanks a lot for your help and suggestions. The issue is now resolved. It turns out the root cause was related to the email configuration — the system was missing a properly defined external SMTP relay. Once a working relay was set up and the sender address was aligned with the authenticated user (e.g. noreply@mail.com), everything started working correctly. This applied to both DocuSeal and another app I tested. One of them required setting environment variables manually to define the SMTP parameters explicitly. Appreciate the time you took to respond. Hopefully this helps others who might encounter the same situation. Thanks again to [@james] and [@luckow] for your support — and hopefully this can help someone else who runs into a similar case in the future. Best, saivie

@pavelalonso can you tell us what is "Timestamp URL" and where did you remove it ? (somehow you understood @docuseal 's commend and fixed it!)

@dsp76 said in Is it just me? Whitelabeling - Logo and Name at the same price as the commercial alternative?: Did I miss something? I don't think so, it does indeed seem like white labelling is only available as part of their pro $20/mo/user plans even if self hosted https://www.docuseal.co/pricing

Thanks so much, @nebulon.

@girish said in Error 500 in DocuSeal After Update to Version 1.5.0: @qwerti said in Error 500 in DocuSeal After Update to Version 1.5.0: The current version is 7.5.2; perhaps we should consider updating it. This is most likely the root cause. redis has changed in versions a lot since. Specifically, the newer versions of redis added acl support and also do not support empty redis usernames. I have set the minBoxVersion for docuseal now so it doesn't get installed. Sorry for the late response. We just installed the latest version yesterday, and now everything is working again. Thank you very much for your help.

@docuseal thanks for the heads up! Cloudron has a redis addon, so I have added that to the package now and configured REDIS_ENV accordingly.

Looks like this is hardcoded upstream (https://github.com/docusealco/docuseal/blob/781ccc701d6ceefa30591b2547026678e067d0f2/app/views/pages/landing.html.erb#L76) . @enerch you should ask upstream to make this configurable .

@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 ?

@docuseal this is great, thanks!

@avatar1024 ah, I missed that part that you restored! Thanks for reporting.

@avatar1024 Might be best to ask this upstream at https://github.com/docusealco/docuseal/discussions For the first question: maybe https://github.com/docusealco/docuseal/issues/132 ?

Thanks! It works again!

Docuseal re-installed, set a 32 characters password and OTP, now it's working

Indeed, typo . Fixed for next release. Thanks for reporting.