-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nextcloud AIO 29.0.3 and LibreSign 9.1.3 can't get past 'Invalid hash of binaries files.' error #3324
Comments
It's getting better but weird : I had the idea to try earlier version of LibreSign. Could not get any of 9.1.x version working but 9.0.2 installed and got me passed the webUI LibreSign Wizard. I can still see the 'Invalid hash of binaries files.' error when visiting |
These dependencies are no longer necessary in LibreSign, they have been replaced by pdftk.
|
Could you provide more information about the files that stay at log? Sounds that PHP haven't access to these files. Other possible points to check is about this issue: Another point to check is a |
@t3cneo I identified a problem at build process and created a new release with fixes. Could ou test again with the newest release? |
All good now with 9.2.2, thanks a lot @vitormattos |
Describe the bug
NC AIO 29.0.3 here with LibreSign 9.1.3, can't get past the 'Invalid hash of binaries files.' error
To Reproduce
Steps to reproduce the behavior:
Install LibreSign 9.1.3 from webUI, click 'Download Binaries' and get the error.
Install from cli (from inside the container) lead to the same error.
Expected behavior
Binaries installed and LibreSign ready to work..
Screenshots
Environment information (please complete the following information):
Additional context
I read all topics related to AIO, especially #1409 and #3026, here are a few things you might ask :
NEXTCLOUD_ADDITIONAL_APKS
is set toimagemagick ghostscript
and the output ofgs --version
is10.03.1
Java seams to install as expected :
EDIT:
Don't think it could be related but alpine has been bumped since #3026
The text was updated successfully, but these errors were encountered: