Seems like an app internal issue, but maybe some packaging side-effect, hard to tell without any server side logs. Are you able to create signature fields using the UI itself?

@girish Thanks so much.

@wheez good idea, I have fixed up the package.

This sounds like a bug in documenso then if it can't find expected objects in the storage. But if we want to investigate here, maybe not use a Beta S3 storage on top of a feature in Documenso for a start. @kbtonmoy how are you configuring Documenso? Is this the S3 backend configs around NEXT_PRIVATE_UPLOAD_BUCKET around https://docs.documenso.com/developers/self-hosting/how-to#advanced-configuration ? Have you already looked for help from Documenso as it most likely is not a Cloudron related issue.

Thanks @CptPlastic & @nebulon for working through this. I've got mine up and running now. Best, Jon

As with the feedback from @CptPlastic at https://forum.cloudron.io/topic/12281/create-new-cert this shoud be solved then if you follow the adjusted docs https://docs.cloudron.io/apps/documenso/#signing-certificate

@nebulon Thank you nebulon! I realized I was in the wrong directory and got it working. Best, Jon

This should be fixed with package version 0.2.0 published by now. This will redirect the link from the success share card to the upstream project URL for https://documenso.com https://git.cloudron.io/cloudron/documenso-app/-/commit/23d52ca75fb33ee10d1ad5ef965dc387ebb5f6c9

Mail template (with their company address) is hardcoded at https://github.com/documenso/documenso/blob/main/packages/email/template-components/template-footer.tsx#L22