-
Notifications
You must be signed in to change notification settings - Fork 34
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
Pi Zero could not bind to port 80 after upgrade to v1.13.0 #1075
Comments
@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. Thanks for reporting this! |
Oh I see. Anything else I should adapt/change to my setup or was this the only breaking change? Maybe worth adding to the release notes? |
@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. |
Had the same issue. Took me a while to find the fix to this. Glad it's documented now here. Thanks! |
same issue on raspberry pi 4, while updating to 1.15.0 . The fix by OP still works. |
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: