Skip to content
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

Open
TKone7 opened this issue Feb 7, 2025 · 3 comments
Open

Pi Zero could not bind to port 80 after upgrade to v1.13.0 #1075

TKone7 opened this issue Feb 7, 2025 · 3 comments

Comments

@TKone7
Copy link

TKone7 commented Feb 7, 2025

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:

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.

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.

@rolznz
Copy link
Contributor

rolznz commented Feb 7, 2025

@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!

@TKone7
Copy link
Author

TKone7 commented Feb 7, 2025

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?

@rolznz
Copy link
Contributor

rolznz commented Feb 12, 2025

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants