@gdeflaux Can you check with the latest package? The latest one has sockpuppetbrowser which supposedly fixes the problem.

Hello @CaeruleusAqua @pepicrft linked the workaround here @pepicrft said in Documenso does not come up after update to 1.6.0: For anyone running into this, it seems the migration assumes that all teams have a subscription. Until the migration is fixed, you can workaround it by faking a subscription. Either you can apply this yourself or you will have to wait until Documenso releases a new Update fixing this issue.

Closed due to inactivity

Hello @Isaac This is the Cloudron Community. Since you stated you are hosting Documenso on proxmox we are unable to assist you any further. But since you found us, maybe Cloudron can help you to host Documenso so it works out of the box!

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?

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

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