mnbro
mnbro
### Before you start please confirm the following. - [X] Yes, I've searched similar issues on [GitHub](https://github.com/portainer/portainer/issues). - [X] Yes, I've checked whether this issue is covered in the Portainer...
https://github.com/documenso/documenso/blob/909c38f47e9cc2e852d78ca7f6187d8659d866cf/packages/signing/transports/local-cert.ts#L32 If `NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH` is empty the above line determines the default location, so a new/fresh install will fail even if in the documentation is specified the [next](https://docs.documenso.com/developers/self-hosting/how-to#:~:text=NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH,documenso/cert.p12)
### Issue Description Inside the docker container, Documenso server only listens on eth0 on $PORT(3000). If I connect the container to multiple networks (one of this network being connected to...
### Issue Description For a fresh install I setup OIDC and `NEXT_PUBLIC_DISABLE_SIGNUP="true"` and `NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true"`. A new OIDC user successfully authenticates but will not be provisioned (the app will redirect him...
### Issue Description My understanding is that setting `NEXT_PRIVATE_OIDC_SKIP_VERIFY` to `true` will skip mail verification for an OIDC authenticated user. If the above assumption is true, this is not the...
### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Public Roadmap ### Why should this be worked on? The pace of...