TRPCClientError: We were unable to sign this field. Please try again later. about documenso HOT 5 CLOSED

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

from documenso.

In the meantime, things I tried but no luck with the same problem to persist.

1. Recreating all the required files with the commands bellow
2. openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes
3. used the phrasekey: taxes
4. openssl pkcs12 -export -out cert.p12 -inkey myKey.pem -in cert.pem
5. then I chmod 777 the cert.p12 file
6. Logged in to container console and check if it was accessible. After chmod the file it was accessible by the container
7. Redeployed my server with the new envs changing the following:
   NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH = /opt/documenso/cert.p12
NEXT_PRIVATE_SIGNING_PASSPHRASE = taxes

from documenso.

In the meantime, what I also tried but with no luck.

1. Recreating all the required files with the commands bellow from the let's encrypt certificates by navigating to /etc/nginx/ssl-certificates
2. Updating env file paths for the generated p12 file
3. Reading about generating a p12 file from existing certs. Also using this url for info.
4. chmod the certs recursively so the container can access p12 generated from this command openssl pkcs12 -export -in docs.domain.com.crt -inkey docs.domain.com.key -out cert.p12
5. Confirming that the file is accessible from the container sh terminal
6. Reloading and redeploying the server
7. Issue persists

from documenso.

Completely my bad. Everything for the solution is on signing.md, I thought it was a file to be ignored then I read the contents.

from documenso.

Hey awesome to know that you were able to resolve this yourself ❤️

from documenso.