Tried to upgrade a Pi 4 to the new version. It was so messed up I decided to re-download the blockchain and start from scratch. I only use Umbrel for my BTC node. If I used it for anything else I would be pissed off. Really pissed off. Clearly this software was not thoroughly tested.
1 Like
REGRETS! Umbrel 1.0 is up an running. But I CANNOT get my node back. And NONE of my apps are working. Tryed all the easy options, restarting, disconnecting from power. I’m a little tech savvy but not comfortable troubleshooting without a GUI.
NOBODY SHOULD ATTEMPT AN UPGRADE UNLESS YOU KNOW HOW TO NAVIGATE OUTSIDE THE PLATFORM! THIS LAUNCH WAS BUNGLED HARD! FIRE THE QA TEAM
UGH. I’M SO PISSED.
4 Likes
Hi @yesvanessa sorry to hear about your issues here.
Please give the dashboard some time, and after a while the apps should be accessible again.
If you’re still having any issues, please reach out to support@umbrel.com or our support chat at umbrel.com
We believe we managed to find the culprit to the user losing data and app access.
We checked the bash script from the Umbrel repo, probably upgrading to v1.0 causes the user.json conf file to update to user.json.migrated, so Umbrel can’t create docker containers for these apps based on json content, hence the need for a new user setup in some cases.
This might not apply to all issues and uses cases, but this is what we did when we reverted from the 1.0 install back to 0.5.4, and couldn’t access anything at all any more.
So if you do have issues, have a look at user.json and user.json.migrated, and do a diff on them.
For what its worth, the other two Pi’s that have upgraded to 1.0 are still dead ducks, no Bitcoin node running yet and neither App store access / System Update or working yet. Will let you now if we figure that one out.
All credit to my team mate Vinh Lam here in Saigon.
Hope the above helps some of you out!
Saigon out…
1 Like
Hey everyone I’m really sorry to hear about your issues. Most users seem to be updating fine but there’s a small number of Pi users that appear to be having issues. We did test the update on Pi 4 extensively and didn’t encounter this issue ourselves, the team has been trying to recreate it but we’re unable to. I’m really sorry again for the inconvenience, completely understand the frustration.
We’re currently investigating further, it’s our top priority right now.
For anyone hitting this issue I’d really appreciate some more information so we can try understand what’s going on 
. I’ve create a new thread here to keep track of everything: Raspberry Pi issues on 1.0
1 Like
@Hasher
Read the reply to my original post, check user.json and user.json,migrated!
Should all be ok.
@djmeistro @ronbdoe @yair @SaigonMike @Hasher @toddhigg @yesvanessa if you have the time to post some logs on the thread I linked above I’d really appreciate it
I’ve also included simple instructions for those of you that have reverted back to 0.5.4 on how to get your apps running again.
1 Like
How do we downgrade to 0.5.4?
1 Like
Are you able to DM me on Telegram (Telegram: Contact @lukechilds) so we can have faster back and forth? I can walk you through it. Also if you’re still currently on 1.0 it would be great if I can get some logs from you to see what went wrong.
I lost my lightning wallet since the update…
1 Like
Think you and I along with many others experience the same issue. Your Lightning Node also just keeps saying “Starting” and nothing happens and nothing shows?
Yes. How to solve that, there was a lot of money on it
I don’t know. @lukechilds says that we should not go back to old SD card with the previous version. I am waiting for further instructions on what to do.
Why ? Where did he say that?
I sent him a message on Telegram. Got me confused as they state in the FAQ and Troubleshooting that no data other than the ios is on the SD card but apparently now after having migrated to 1.0 we should not go back to previous version.
So we f*cked?
I have no idea, I am surprised that they do not come forward with any communication on these issues.
Where did you have that ?
I finally was able to run the images again and it seems a problem with docker so I diced to re-flash the SD card again and it worked. Maybe something failed during the flashing time.