1
I want to report a bug, but I can't find the bug report board. All links I find lead back to this Request a Feature board.
C
c.edwards.consultingJun 20, 2025
Hi, I just ran the update script to update my Albu hub on RaspberryPi Zero, but it failed to verify with the error/bin/bash: Line 16: ./verify.sh: no such file or directory. Verification failed, aborting installation. I can no longer connect to my node/wallet. I can ssh into the pi but I'm not sure how to fix the issue. Any advice appreciated.
Kommentare
For the next time, and anyone else reading, support issues can be sent to support@getalby.com & support.getalby.com
jeanpaul Thanks
Hi, you should be able to run the existing update script locally saved in your hub working directory rather than running the update script from github
roland thanks for the reply. Can you be a bit more specific, where is the update script stored locally? Are you able to provide me a line of code that I can cut and paste? Thanks.
c.edwards.consulting it should be in
/opt/albyhub. If you cd into that directory then you should be able to runupdate.shroland I don't have an update.sh in the /opt/albyhub directory. I have backup and data folders and server-linux-arm6.tar.bz2 (and two other copies of that file) presumably from running the update script from github a couple of times.
c.edwards.consulting ah, ok. Then you will need to download both the update.sh and verify.sh and put them in that folder. The verify script is here: https://github.com/getAlby/hub/tree/master/scripts
And you can get the update script either from inside the pi-arm folder in the above url.
roland I'm getting closer... I now have both files on the opt/albyhub directory. But when I run the update script it still fails at line 16. However now it says ./verify. sh : permission denied. When I look at file ownership using ls -l it shows albyhub as the owner with -rw-r--r--
c.edwards.consulting can you try
chmod +x ./verify.shroland one step closer... Now verify runs but fails. Can't check signatures : No public key
c.edwards.consulting you can see how to add the key in https://github.com/getAlby/hub/releases if you would like to verify it.
roland thanks for your help with this. I have now been able to successfully run the update script and it verifies and completes but I still can't connect to the server on a web browser, using the ip address or albyhub.local. I can ssh into the server at the ip address without issue. Any ideas what to try next?
c.edwards.consulting This is the output of sudo journalctl -u albyhub -f -n 250 if that helps.
c.edwards.consulting unfortunately this issue is caused by an upstream dependency. We've merged a fix and hopefully the issue will be solved in Alby Hub 1.18 which will be released in 1-2 weeks.
roland okay, thanks. Should I just wait until the update is released? I'm in no rush, but will my channels be forced closed if my hub is offline for an extended period?