Skip to content

Conversation

@NodeDiver
Copy link
Contributor

  • Turned on PROXY_AUTH_ADD so Alby Hub now sits behind Umbrel’s app proxy.

This forces anyone visiting the app to authenticate with their Umbrel account even if the Alby Hub unlock password is known. Adds a safety layer when users mismanage credentials, requiring both the Umbrel password and the Alby Hub unlock password to gain access.

APP_HOST: albyhub_server_1
APP_PORT: 8080
PROXY_AUTH_ADD: "false"
PROXY_AUTH_ADD: "true"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't true the default here so you can omit the whole line?

From the docs:

The Umbrel App Proxy automatically protects an app by requiring the user to enter their Umbrel password

Suggested change
PROXY_AUTH_ADD: "true"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is the default. Also I just test it locally and indeed the whole line is unnecessary, it's removed now.

@NodeDiver NodeDiver force-pushed the fix/albyhub-proxy-auth branch from 32f5f2b to c4aa414 Compare November 12, 2025 14:54
@NodeDiver
Copy link
Contributor Author

@nmfretz I thank you in advance for reviewing and merging this 🙏

@nmfretz
Copy link
Contributor

nmfretz commented Nov 17, 2025

Awesome @NodeDiver, really glad to see Alby Hub utilizing the auth proxy.

This forces anyone visiting the app to authenticate with their Umbrel account even if the Alby Hub unlock password is known. Adds a safety layer when users mismanage credentials, requiring both the Umbrel password and the Alby Hub unlock password to gain access.

And in addition to needing to enter the umbrel password if not signed in, if a user has 2FA set up on their Umbrel then Alby also sits behind that!

In order for existing users to get an app update notification the version field in the umbrel-app.yml needs to be updated. As-is, only fresh installs of Alby Hub would site behind the auth proxy.

What's better for you guys:

  1. We wait until the next version of Alby Hub is released, and then merge this PR with updated image, version, and release notes. This means users would continue to not have the auth proxy enabled until then.

  2. Merge this PR now with only the auth proxy added. We change the version to something like

version: 1.20.0-auth

or

version: 1.20.0-hotfix.1

And then add release notes like:

releaseNotes: >-
  This release adds additional security to your Alby Hub app on umbrelOS by ...
  

  No other changes to Alby Hub are included in this release.


  Full release notes are found at https://github.com/getAlby/hub/releases

@NodeDiver
Copy link
Contributor Author

NodeDiver commented Nov 17, 2025

Hey, @nmfretz ,
Since this change is independent of the next version of Alby Hub and it is an enhancement on security, you are welcome to merge it now.

You can use version: 1.20.0-auth

releaseNotes: >-
  This release adds additional security to your Alby Hub app on UmbrelOS by adding existing UmbrelOS security measures
  

  No other changes to Alby Hub are included in this release.


  Full release notes are found at https://github.com/getAlby/hub/releases

Thanks!!!

@github-actions
Copy link

🎉   Linting finished with no errors or warnings   🎉

Thank you for your submission! This is an automated linter that checks for common issues in pull requests to the Umbrel App Store.

@nmfretz
Copy link
Contributor

nmfretz commented Nov 18, 2025

Excellent, thanks again @NodeDiver! Here's what I've done for the release notes:

image

Reviewed and tested connections. If a user is not logged in to their Umbrel they would be met with this screen if trying to access the Alby Hub app directly:

image

@nmfretz nmfretz merged commit 7d2d9dd into getumbrel:master Nov 18, 2025
1 check passed
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

Successfully merging this pull request may close these issues.

3 participants