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

Better handling of multiple umbrel nodes on the network #1797

Open
knorrium opened this issue Apr 23, 2024 · 1 comment
Open

Better handling of multiple umbrel nodes on the network #1797

knorrium opened this issue Apr 23, 2024 · 1 comment

Comments

@knorrium
Copy link
Contributor

The documentation says that when there are multiple Umbrel instances on the network, they can be accessed through umbrel-2.local, umbrel-3.local etc.

That seems to work fine, but I believe the actual hostname could be updated to prevent collisions and it would also fix the connection instructions in the apps:

Note the address on the nav bar vs the hostname reported by the console:

Screenshot 2024-04-22 at 9 53 52 AM

Core and Electrs instructions:

Screenshot 2024-04-22 at 9 51 03 AM
Screenshot 2024-04-22 at 9 50 45 AM

I'm not sure if this is due to the collision but my latest Umbrel Home node becomes unresponsive after a few days.

@highghlow
Copy link
Contributor

Umbrel apps source the device's hostname through an env variable passed to them, so probably that should be updated to reflect the dns change

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