LibreSign / LibreSign/libresign
Invalid hash of binaries files - NC AIO 10
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 326
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the LibreSign setup flow on the reported Docker and Ubuntu environment, using the download and validation steps described in the issue. Inspect the related nextcloud.log entries with the provided libresign filter and compare the binary installation and validation results. Done means validation recognizes the downloaded binaries without prompting for another download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php, ubuntu
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100