Umbrel 0.5.1 is out with app release notes and bug fixes

Umbrel 0.5.1 is now out with several bug fixes, performance improvements, up-to-date Tor (0.4.7.8, that also patches the recent DDoS attack vulnerability in Tor), and the ability to see what’s changed in new app updates. Simply login to your Umbrel to update. :rocket:

PS: If you’re on Umbrel 0.4.x, you’d need to update to Umbrel 0.5 first to see this update.

Twitter announcement: https://twitter.com/umbrel/status/1547558601929408512

2 Likes

patch notes?

1 Like

You can find them on our GitHub. Since we use atomic commit philosophy, the entire git history acts like a changelog. So for instance, the notes for 0.5.1 would be the commit titles between 0.5.0 and 0.5.1.

1 Like

Is anyone else having issues updating to 0.5.1? My install gets stuck at “Pulling new containers” then times-out and goes back to the settings page (still at 0.5.0). Once that fails over selecting “Install” again from the settings page simply errors out and requires a node restart for the install option to try and work again.

Update1: The 1st issue I’ve found is that DNS is hardcoded in the update so that it will always try to resolve at 8.8.8.8. If you run a private DNS (Pi-Hole, etc) you’ll need to punch a hole in your FW to allow Google DNS at 8.8.8.8 and not use the DNS configured on the server.

Update2: I’m currently stuck with the following errors:

Configuring permissions…

Configuration successful
You can now start Umbrel by running:
sudo ./scripts/start

Pulling new containers
Pulling tor_proxy … done
Pulling dashboard … done
Pulling manager … error
Pulling nginx … done
Pulling auth … error

ERROR: for manager Get “https://registry-1.docker.io/v2/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

ERROR: for auth Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
ERROR: Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: context deadline exceeded
Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Get “https://registry-1.docker.io/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
== End Update Script 01-run.sh ==

== Begin Update Script 02-run.sh ==

Update3: FIX: Hardcoded DNS is the problem here but it oddly only shows as errors on a few containers when updating. You absolutely need to allow full DNS out to either one.one.one.domain or Google. Local DNS will only work for about 85% of update as this is currently coded! Once I opened up FW rules to allow Google DNS to flow everything updated as normal.

2 Likes

Good job team Umbrel!! Congrats on the release of the 0.5.1 update!

I did the update from 0.4.16 to 0.5.0 and am updating subsequently to 0.5.1 right now.

The “Check for Updates” in the GUI didn’t show any available updates neither in my 0.4.xx versions nor in the 0.5.0 version, so I used

cd ~/umbrel && sudo ./scripts/update/update --repo getumbrel/umbrel#v0.5.0

and

cd ~/umbrel && sudo ./scripts/update/update --repo getumbrel/umbrel#v0.5.1

for both updates.

Question:
Does(did) the GUI update work for any of you? If yes, any idea on how to troubleshoot it at my side?

I managed to install via command line to 0.5.1 and it runs seemingly correctly now. Will play more with it soonest. Didn’t encounter any issues. Actually, my local network has the Umbrel Raspberry Pi and Pi-Hole configured as DHCP-announced DNS server. But I don’t think I block custom DNS servers via the home router. I didn’t notice any irregularities.

Thanks for the command line help to get me a little more output to troubleshoot better than what the GUI offered. I didn’t know the “–repo getumbrel/umbrel#v0.5.1” flag which made all the difference! The really odd part is that only a few containers are effected by this issue. It was fun to TS though! :slight_smile:

1 Like

the problem with the login for for example RTL or LNDg is not fixed. You still have to log in to Umbrel including 2FA

Sorry know this is reviving an old thread, but I’m trying out Umbrel and have had a few issues. Looks like DNS is hard-coded which causes a number of issues if you’re running your own DNS server and blocking external DNS. That meant the GUI update didn’t work, and neither did the scripts until I edited resolve.conf with my nameserver IP’s. Unfortunately these get overwritten on reboot so I need to set up a job to keep updating it, otherwise trackers fail etc.

Also note that the update script backs up the entire directory structure!? That seems pretty insane, considering media libraries etc. Watching it run through a ton of huge MKV files at the moment which is painful to say the least. I would assume/hope it won’t try to back up the Blockchain data if you’re running a node?

It does remove the backup thankfully - but I can imagine the update will take longer and longer as data grows.

It should be in the settings to establish the connection via Tor, clearet or hybrid