You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not exactly sure, but I think I ran v1.11.x before (initial install).
After the upgrade the service did not start up anymore and I detected an error in the logs:
listen tcp :80: bind: permission denied
After a bit of research I figured that non root users are not allowed to bind to "privileged" ports. So I added the permission manually, which fixed the issue for me.
Not sure why it worked before, and if my situation is unique or if there is a general issue and other users might be affected as well. Just wanted to report in case.
The text was updated successfully, but these errors were encountered:
@TKone7 the installation and update scripts were updated a bit to reduce the amount of permissions required. Unfortunately it was a breaking change so existing users will need to manually run the command as you did.
@TKone7 unfortunately only a very few users run RPI and putting it in the release notes the change will be seen by all users, which will be irrelevant to most. The commit would have been shown in one of the release notes, inside the commits section.
I am running my hub on a Raspberry Pi Zero and just performed the upgrade via the upgrade script I found in this repo:
/bin/bash -c "$(curl -fsSL https://getalby.com/install/hub/pi-zero-update.sh)"
I am not exactly sure, but I think I ran v1.11.x before (initial install).
After the upgrade the service did not start up anymore and I detected an error in the logs:
After a bit of research I figured that non root users are not allowed to bind to "privileged" ports. So I added the permission manually, which fixed the issue for me.
sudo setcap 'cap_net_bind_service=+ep' /opt/albyhub/bin/albyhub
Not sure why it worked before, and if my situation is unique or if there is a general issue and other users might be affected as well. Just wanted to report in case.
The text was updated successfully, but these errors were encountered: