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
Update to v0.3.0 failed, services start but are not reachable, docker-compose problem? #379
Comments
Also having issues with updating. The updating icon is sat spinning and my update-status json looks like this
|
Same Problem here. Update to 0.3.0 - starting over the web-login. Then the update is starting and about ~ 5Minut all stops. And the Umbrel is not reachable... I can not conect over WEB and not over Putty |
Same here. Attempted 0.3.0 over GUI, now I cannot access the GUI at umbrel.local, but update-status.json says: |
Is it ok to download a new image of umbrel and overwrite your existing image on the SD card? |
@robertclarkson @paulo03 can you please check your docker-compose.yml file if there are actual IP addresses and ports in it? |
Yes, that works |
@esackbauer My issue has been resolved. The solution was to run this (got it from @umbrel over twitter):
|
Sorry about the failed update, guys. There's a networking issue in the latest release regarding IP collisions. Here’s an intermediary fix to get it working: Step 1. SSH into your Umbrel (on Umbrel OS):
Password: Step 2. Manually OTA update to the repo with intermediary fix: If your Umbrel's local IP address is 10.0.x.x, run:
Otherwise, run:
|
Tried the first command, seemed to work, but after rebooting the node is unreachable on the web interface. Trying the second command - it didnt work
|
@robertclarkson Run this instead of the second command:
|
That worked for me, thanks!! |
Thanks for the help, same error as before. |
@robertclarkson you said the first command worked for you, right? Can you please try that again? If it doesn't work after a reboot, can you please run the debug script and paste the links to the logs it generates?
|
Original issue solved by 0.3.1 update. |
@mayankchhabra I think my issues are actually steming from a problem with my external SSD drive, which might be caused by an underpowered power supply. I havent had time to resolve yet and will be re-imaging from scratch. Thanks for the help! |
I tried the update over the GUI, from v0.2.15. The progress bar was stuck, and after like 30 minutes I had a look, I have a fast machine and starting/stopping Umbrel usually takes like 30 seconds.
Content of update-status.json:
The logs indicate that everything "0?-run.sh" went through without throwing errors:
When inspecting the docker-compose.yml something seems wrong, no $variables like IP addresses were replaced with actual IP addresses or ports.
Could this be the culprit? How to recreate a proper docker-compose file?
Debian 10.7 amd64
Docker 20.10.1 (via debian repository)
docker-compose 1.27.4
The text was updated successfully, but these errors were encountered: