LibreSign
Invalid hash of binaries files - NC AIO 10
This is a fairly fresh install of the nextcloud AIO as of this week. The docker host is ubuntu 24.04.2 lts
when trying to setup libresign i get the button to download binaries, once the binaries download i have the option to validate setup, but after attempting to validate setup i am once again prompted to download binaries.
I have tried the following
occ libresign:uninstall --all then disabled and removed the libresign app then rebuilt the master container with imagick ghostscript and poppler-utils then rebooted the server then downloaded and enable the libresign app then occ files:scan-app-data libresign then occ libresign:install --all
issue persist.
Environment information (please complete the following information):
- OS: Docker
- Browser chrome
- LibreSign Version 11.0.4
- Nextcloud Server Version [31.0.2]
- Logs (get the entries from nextcloud.log related with LibreSign i.e
tail -f data/nextcloud.log|grep libresign)
Additional context
more that it is the same issue that seems to come back, i also have this issue and i'm on NC AIO 10
have you tried just running libresign:install --all using occ web?
more that it is the same issue that seems to come back, i also have this issue and i'm on NC AIO 10
have you tried just running
libresign:install --allusing occ web?
I used sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ libresign:install --all
when i check config this is what returns
i think that should be fine, try
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ libresign:install --java
i used this: https://apps.nextcloud.com/apps/occweb
OCC web is not compatible with NC 31
if you look at the repo you'll see an PR to fix that
but that's another difference, while we are both on NC AIO 10, mine is still on NC 30 🤔 not sure to what extend that matters tho—
I am also having this issue, even after the very latest update. Also running NC AIO 10 with NC 30.
for subscribing to the issue you can also just click subscribe on the right, so show you have the same issue you can add a 👍 on the first post
This way we keep the relevant information easier to find for the people looking into the issue
I have done all of this as well and its completely broken. When someone goes to sign it says there is a server error and wont let them sign. Getting all the same error and nothing above was able to fix it.
At the moment, we don't have any customers using LibreSign with Nextcloud AIO, so we haven't prioritized specific support for it yet.
Our focus is on delivering features and improvements based on the needs of our current users and GitHub Sponsors, whose support plays a key role in helping us grow the project.
If LibreSign is useful to you and you'd like to see expanded support for Nextcloud AIO, consider supporting us — even a small contribution makes a big difference! 💚
Thank a lot by your for your interest in LibreSign and your help at this issue!
@vitormattos @yourITMatters I actually use this for my small business. We have given a contribution Thank you!
If LibreSign is useful to you and you'd like to see expanded support for Nextcloud AIO, consider supporting us — even a small contribution makes a big difference! 💚
@vitormattos Hi, I don't think this issue is only from nextcloud AIO. We have the same error with nextcloud 31.0.4 and libresign 11.1.2. Thanks!
At the moment, we don't have any customers using LibreSign with Nextcloud AIO, so we haven't prioritized specific support for it yet.
Our focus is on delivering features and improvements based on the needs of our current users and GitHub Sponsors, whose support plays a key role in helping us grow the project.
If LibreSign is useful to you and you'd like to see expanded support for Nextcloud AIO, consider supporting us — even a small contribution makes a big difference! 💚
Thank a lot by your for your interest in LibreSign and your help at this issue!
I appreciate that. is there a dollar amount that would sponsor this bug fix?
Thank you so much for your interest in supporting LibreSign. It truly means a lot to us! 💚
Even a small recurring contribution at GitHub Sponsors helps us cover development costs and focus on improvements like this one, including better support for Nextcloud AIO.
We’d be grateful for any support you can offer. It helps us keep making LibreSign better for everyone.
If its a matter of money the system will not allow me to donate again until the payment clears. I will be happy to become a full time sponsor after we get this resolved. Thank you! @vitormattos
Thank you so much, @Computermaster20! 💚 I appreciate your donation a lot and your willingness to support LibreSign. That kind of commitment makes a huge difference to us.
Your support motivate new contributors, help us to improve features, and ensure LibreSign stays strong and sustainable for everyone.
This project is maintained by community sponsoring and we haven't a fixed funding from other places.
Let’s keep in touch, and thank you again for being part of this with us!
I started to make more tests to try to reproduce this because I can't reproduce this at any place. I already made a small improvement here:
- #4874
Every when we get the message Invalid hash of binaries files., is generated a log with the result of hash validation:
https://github.com/LibreSign/libresign/blob/0f9f70c96744a0bcb44cf45d7f206457201f0cf7/lib/Service/Install/ConfigureCheckService.php#L326-L330
This will write into nextcloud.log file an entry with this message and the result.
Could you put here the entire row from nextcloud.log file that have this message?
{"reqId":"6qZ4SzfGZAerhficXyRe","level":3,"time":"2025-04-23T15:59:36+00:00","remoteAddr":"REDACTED-FOR-SECURITY","user":"admin","app":"libresign","method":"GET","url":"/ocs/v2.php/apps/libresign/api/v1/admin/install-and-validate?requesttoken=hR%2ByNoniae8uxy0uOhxwZ5UU7GP3NVuODUEv7so%2BVI0%3D%3A4nPme8C7HrZ7iUZramQ4LPZh1FazAxLtbDBXvIARY7k%3D","message":"Invalid hash of binaries files","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36","version":"31.0.2.1","data":{"app":"libresign","result":"{"FILE_MISSING":{"legal/java.base/ADDITIONAL_LICENSE_INFO":{"expected":"9f658dfea71bdc3cc1549edfb5ad3171dbfa0082b2d91e820c09abe0b376b6bcd8b5170442a5e25e72274e98f130176bbdecfa7997c59705782b214f02136a20","current":""},"legal/java.base/ASSEMBLY_EXCEPTION":{"expected":"5516e2e9eb3a555562f600cc3cd85ae01004962a8af8c49d2598281ce622bcbee7a4bc513b94b05e3b611bb50611360171e21bae9c1b3ed7d05a0867de7d3bb2","current":""},"legal/java.base/LICENSE":{"expected":"6732288c682a39ed9edf11a151f6f48e742696f4a762c0c7d8872b99b9f6d5ab6c305064d4910b1a254862a873129f11fd0fa56ff11bc577d29303f4fb492673","current":""},"legal/java.base/aes.md":{"expected":"4d14b5ddbb4d09797264ed29ba71fab6986b4a9e75efb9402c1476e0a9e2884813d6a922dea125643b4f74e1f3e458f4e48d6c840e0f4d16ed72ffbc4611dbb2","current":""},"legal/java.base/asm.md":{"expected":"2fcf1da50a53858e5e68db51996b59ebeb8f07b698f72b67a827d4fd302f757c5c0d0479b37128d239268b635b20177a27557c1dba920fa9f12f1bec2b7f6d40","current":""},"legal/java.base/c-libutl.md":{"expected":"ae459d8ce5581ea57e203088373c1ce86d122d0e27eb871ee1383e0e64cd8a184fa207eee0e835347316e70afa24a1c95aec30def3e09d15ee19a0b2c3ad2095","current":""},"legal/java.base/cldr.md":{"expected":"8ab32a80deb12dd1f3a54a38b3335a76feb44e20fcf5ee897d47511e0acedbbedf51a241768441c56259a54c7303ddf7b57be7693c5cddb30f90741ca3257190","current":""},"legal/java.base/icu.md":{"expected":"0b31bcbdb578ac448dd145c0160c83e24ff4f1b48cada692d213e026155f5a44fc0e7b01444c5af0649e49ffd100421a890a6ed0c60722b15c4a4938a0c99b67","current":""},"legal/java.base/public_suffix.md":{"expected":"f99698fcaf492acd8bface4ca43fdf52a8baf65947e0fb82baaf953998344a01fc5f752f2b3e78e9482e8a438f91136810b82cc60ea212346800944615ad3c95","current":""},"legal/java.base/siphash.md":{"expected":"4dc96c93e28152c6a832bf58bc912ada7d399d0e3180ae5a53a30de0332672c25a2606ea9ea5333a9b6a83f9f42428a08f761b68d41ba087d7e8eee65dab45c6","current":""},"legal/java.base/unicode.md":{"expected":"06f8cd7233ab0e6d2db403765aa543f153b611fa6d1cdc571fa98dc8ff9a908c14034e31305b14c6f80ee8de5bb5e6e49dcd18c030d5b5772dc93153ea16fc19","current":""},"legal/java.base/zlib.md":{"expected":"d5441b256ea55b68fb28a3546a8d5bd24d89a551222745933c23c02b917a3955469064eeed3ccbe2764ff158f2a472aad5b9b3f91190ffefab9f6b2682a75a4d","current":""},"legal/java.compiler/ADDITIONAL_LICENSE_INFO":{"expected":"9f658dfea71bdc3cc1549edfb5ad3171dbfa0082b2d91e820c09abe0b376b6bcd8b5170442a5e25e72274e98f130176bbdecfa7997c59705782b214f02136a20","current":""},"legal/java.compiler/ASSEMBLY_EXCEPTION":{"expected":"5516e2e9eb3a555562f600cc3cd85ae01004962a8af8c49d2598281ce622bcbee7a4bc513b94b05e3b611bb50611360171e21bae9c1b3ed7d05a0867de7d3bb2","current":""},"legal/java.compiler/LICENSE":{"expected":"6732288c682a39ed9edf11a151f6f48e742696f4a762c0c7d8872b99b9f6d5ab6c305064d4910b1a254862a873129f11fd0fa56ff11bc577d29303f4fb492673","current":""},"legal/java.datatransfer/ADDITIONAL_LICENSE_INFO":{"expected":"9f658dfea71bdc3cc1549edfb5ad3171dbfa0082b2d91e820c09abe0b376b6bcd8b5170442a5e25e72274e98f130176bbdecfa7997c59705782b214f02136a20","current":""},"legal/java.datatransfer/ASSEMBLY_EXCEPTION":{"expected":"5516e2e9eb3a555562f600cc3cd85ae01004962a8af8c49d2598281ce622bcbee7a4bc513b94b05e3b611bb50611360171e21bae9c1b3ed7d05a0867de7d3bb2","current":""},"legal/java.datatransfer/LICENSE":{"expected":"6732288c682a39ed9edf11a151f6f48e742696f4a762c0c7d8872b99b9f6d5ab6c305064d4910b1a254862a873129f11fd0fa56ff11bc577d29303f4fb492673","current":""},"legal/java.desktop/ADDITIONAL_LICENSE_INFO":{"expected":"9f658dfea71bdc3cc1549edfb5ad3171dbfa0082b2d91e820c09abe0b376b6bcd8b5170442a5e25e72274e98f130176bbdecfa7997c59705782b214f02136a20","current":""},"...":"Over 20 items, aborting normalization"}}"},"id":"68090ee314375"}
Hello, I want to join this thread because I have the same issue, and I hope to help by providing information that may help resolve it.
To begin with, my Nextcloud AIO v10.12.0 is running with Nextcloud Hub version 9 (30.0.9). I have had the LibreSign app installed and configured in version 10.7.2 for the past 6 months, and it worked fine until last week. The errors I am encountering are exactly the same as those in this thread. After running libresign:install -all, some errors are fixed, but the final error "Invalid hash of binaries files" remains.
In the log, the error "Invalid hash of binaries files" reports the following:
[libresign] Error: Invalid hash of binaries files
GET /ocs/v2.php/apps/libresign/api/v1/admin/install-and-validate?requesttoken=C5VjceJj%2FyHNdXFs7TwDn3%2BzDAubRWdKBXMCzC9Earw%3D%3APMwNEIlRzm2GGSQ6lVkzqCrZZHLIJjdzagU2onULCOo%3D from 181.55.22.218 by adaniieel on 23/04/2025, 3:31:09 p.m.
I noticed something that I don't see reported here: when performing the "Download binaries" process and then "Validate configuration," right after clicking the latter option, the following appears in the log:
[PHP] Error: hash_file(/mnt/ncdata/appdata_oco0bnnmfaw3/libresign/x86_64/jsignpdf/jsignpdf-2.3.0.zip): Failed to open stream: No such file or directory at /var/www/html/custom_apps/libresign/lib/Service/Install/SignSetupService.php#498
GET /ocs/v2.php/apps/libresign/api/v1/admin/install-and-validate?requesttoken=C5VjceJj%2FyHNdXFs7TwDn3%2BzDAubRWdKBXMCzC9Earw%3D%3APMwNEIlRzm2GGSQ6lVkzqCrZZHLIJjdzagU2onULCOo%3D from 181.55.22.218 by adaniieel on 23/04/2025, 3:31:07 p.m.
I see this is related to the error because it concerns the same jsignpdf.
I hope this helps in finding a solution.
Hi @vitormattos,
I hope you're doing well. I wanted to follow up on the issue I previously reported. I've tried several solutions, such as reinstalling the application, rebuilding the master container, and enabling the necessary dependencies, but the problem persists.
I understand you're busy, but I would greatly appreciate any guidance or suggestions to resolve this issue. I'm available to provide more information or perform additional tests if needed.
Thank you for your time and support.
I have an update on this. I saw an update was pushed out and most of the issues are fixed but the error shown is still there. I have had to completely stop using Libresign as it doesn't work for my customers for weeks. This sucks to say the least. Looks like I am going to have to find a new solution if this doesn't get fixed soon. Please note it is now saying Poppler is not installed and it is.
error | Invalid hash of binaries files.
I have an update on this. I saw an update was pushed out and most of the issues are fixed but the error shown is still there. I have had to completely stop using Libresign as it doesn't work for my customers for weeks. This sucks to say the least. Looks like I am going to have to find a new solution if this doesn't get fixed soon. Please note it is now saying Poppler is not installed and it is.
error | Invalid hash of binaries files.
Get the same result. I hope this has a solution.
@Computermaster20 What other app did you look for for this?
I have an update on this. I saw an update was pushed out and most of the issues are fixed but the error shown is still there. I have had to completely stop using Libresign as it doesn't work for my customers for weeks. This sucks to say the least. Looks like I am going to have to find a new solution if this doesn't get fixed soon. Please note it is now saying Poppler is not installed and it is.
error | Invalid hash of binaries files.
Get the same result. I hope this has a solution.
@Computermaster20 What other app did you look for for this?
Opensign looks promising**
At the moment, we don't have any clients or partners using Nextcloud AIO who also help fund LibreSign. That’s why providing specific support for this setup is, unfortunately, not a current priority.
We truly love LibreSign, this excelent FLOSS and privacy-focused digital signature solution. But the reality is that we're working with far fewer resources than needed to sustain our team and expand support for different use cases like Nextcloud AIO. The project is not going anywhere as you can see looking our frequent commits, new features, and regular releases. Today is a Saturday and I'm here, working. We love what we do. We just need to find ways to make this work sustainable in the long run, so we can cover our basic needs and bring more people on board to help develop and maintain the project.
Having access to a working Nextcloud AIO environment might help, but what truly enables us to invest time in this issue and many others is ongoing financial support from the community. As much as we love this project, love alone doesn't pay the bills. We need at least the essentials covered to keep moving forward.
If LibreSign has been useful to you helping cut licensing costs or replacing proprietary tools, please consider giving back a bit of that value by supporting the project. You can contribute through GitHub Sponsors, or reach out to us about recurring support plans for organizations.
LibreSign is going ahead thanks to people who believe in the power of free software. Your continued support makes all the difference.
@vitormattos It is not a problem of AIO. We don't use it and we have the same errors so we have also stopped using Libresing.
@moblesmarti If is about poppler, this isn't an error and also have a tip with instructions about how to remove this information.
If is about message of invalid hashes, we already implemented a lot of checks to identify what's happening and give best feedback to sysadmins. If your environment isn't with Nextcloud AIO, isn't related to this issue because here, is specific to Nextcloud AIO. This wasn't identified in none other environments.