Closed DazeEnd closed 3 months ago
I just noticed that LibreSign creates a filename.signed.pdf
file, even though the signature fails, and the document status is "available for signature".
Internal server error (422 error code), when trying to sign the document
Originally posted by @glimz in https://github.com/LibreSign/libresign/issues/2109#issuecomment-2005054930
@glimz is this reported related with this issue? Did you made the same steps?
Making a quick look at your log I identified that:
Error at JSignPdf side. LibreSign can not do nothing. Follow the error message: Certificate is Empty or Invalid.
The messageCertificate is Empty or Invalid
is made by JSignPdf and is because JSignPdf don't found the .pfx file. The default folder of .pfx file is LibreSign/signature.pfx
. I will check if have a point that don't cover the scenario to get the content of signature.pfx file to generate the problem that JSignPdf receive an empty or not found certificate file.
This is a good start point, I will look more to identify what happening.
So do you think this is a bug, or is this a configuration problem with my installation? I can try to reinstall if you think the problem is on my end.
I need to make more tests because you aren't the unique reporting this problem. I will check what I can do to give best reports to prevent this internal error.
An error that I also need to try to reproduce that stay in your log is this:
Undefined array key \"profileElementId\"
In my development environment I already put a breakpoint at the point that this error was trigged but I don't identified a way to reproduce this error.
I think that haven't relation with certificate but, since that visible elements is stored at filesystem, could have relation.
Just an update: I reinstalled Nextcloud and LibreSign v8.0.0-rc8. After reinstalling, I still get the same error.
I think that this is the same that was solved by:
Was a logic problem when try to sign without password certificate.
This:
Fixes:
An error that I also need to try to reproduce that stay in your log is this:
Undefined array key \"profileElementId\"
In my development environment I already put a breakpoint at the point that this error was trigged but I don't identified a way to reproduce this error.
I think that haven't relation with certificate but, since that visible elements is stored at filesystem, could have relation.
This is fixed for me in v8.0.0-rc9.
Describe the bug When a logged in user attempts to sign a document (using "click to sign"), an internal error prevents the document from being signed.
To Reproduce
Expected behavior The document should be successfully signed.
Actual behavior A message appears that reads, "Internal error. Contact admin."
Screenshots
![image](https://github.com/LibreSign/libresign/assets/2699247/6706208d-6ee3-428f-8ef1-371d6b7b8575)
Environment information (please complete the following information):
Additional context N/A