App store is blank no matter what I do

Support and Troubleshooting
1

I got my Umbrel home yesterday and the first thing it asked me to do was update it. Once done, I started it (I’m using it on my laptop ubuntu 22.04) and opened the app store, it was blank.

I googled around and tried everything I could find on the community forum but the issue still persists.

Tried this as well
First SSH into your Umbrel, when you are executing commands on your Umbrel (and you’re sure you’re in the Umbrel directory on Linux) run this command:

sudo ~/umbrel/scripts/repo update

Then another reboot should resolve the issue.

If you receive an index.lock error run this command:

sudo rm repos/https—github-com-getumbrel-umbrel-apps-git/.git/index.lock

Then

sudo docker compose restart manager

After ~5 minutes your App Store should populate with all available updates, please let me know if you have any other questions

I get “WARNING: The PWD variable is not set. Defaulting to a blank string.
ERROR: Version in “./docker-compose.yml” is unsupported. You might be seeing this error because you’re using the wrong Compose file version. Either specify a supported version (e.g “2.2” or “3.3”) and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see Overview | Docker Docs” when trying docker-compose restart.

Here’s my logs

= Umbrel debug info =

Umbrel version

0.5.4

Memory usage

           total        used        free      shared  buff/cache   available

Mem: 15G 763M 14G 1.0M 828M 14G
Swap: 0B 0B 0B

total: 4.8%
system: 4.8%

Memory monitor logs

2023-09-29 14:18:44 Memory monitor running!
2023-09-29 14:19:59 Memory monitor running!
1419 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-09-29 14:26:20 Memory monitor running!
2023-09-29 14:26:33 Memory monitor running!
2023-09-29 06:22:24 Memory monitor running!
4382 ? R 0:00 bash ./scripts/memory-monitor
4385 ? R 0:00 bash ./scripts/memory-monitor
Memory monitor is already running

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p2 9.7G 2.1G 7.2G 22% /
/dev/nvme0n1p4 1.8T 1.6G 1.8T 1% /home

Karen logs

Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: backup
karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
8377 bytes (8.4 kB, 8.2 KiB) copied, 8.1748e-05 s, 102 MB/s
Creating encrypted tarball…
backup/
backup/.padding
gpg: directory ‘/root/.gnupg’ created
gpg: keybox ‘/root/.gnupg/pubring.kbx’ created
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0
100 8925 0 0 100 8925 0 2267 0:00:03 0:00:03 --:–:-- 2266
100 9071 100 146 100 8925 30 1856 0:00:04 0:00:04 --:–:-- 1887
100 9071 100 146 100 8925 30 1856 0:00:04 0:00:04 --:–:-- 2516
{“message”:“Successfully uploaded backup 1695979480741.tar.gz.pgp for backup ID ee2c381449307712fb9ff8075565608b13464c6b9517af9139519f041ceba831”}

====== Backup success =======

Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
nginx Up 10 hours
tor_proxy Up 10 hours
tor_server Up 10 hours
dashboard Up 10 hours
manager Up 10 hours
auth Up 10 hours

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:28 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:28 GMT] “GET /v1/system/memory HTTP/1.0” 200 85 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:28 GMT] “GET /v1/system/storage HTTP/1.0” 200 89 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:29 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:31 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:31 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:31 GMT] “GET /v1/system/memory HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:31 GMT] “GET /v1/system/storage HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:31 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 29 Sep 2023 16:20:33 GMT] “POST /v1/system/debug HTTP/1.0” 200 17 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Sep 29 06:42:13.000 [notice] Bootstrapped 100% (done): Done
tor_proxy | Sep 29 08:37:05.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.
tor_proxy | Sep 29 10:03:04.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.
tor_proxy | Sep 29 10:58:05.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.
tor_proxy | Sep 29 12:04:05.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.
tor_proxy | Sep 29 12:37:55.000 [notice] Heartbeat: Tor’s uptime is 6:00 hours, with 0 circuits open. I’ve sent 1.31 MB and received 13.97 MB. I’ve received 1 connections on IPv4 and 0 on IPv6. I’ve made 23 connections with IPv4 and 0 with IPv6.
tor_proxy | Sep 29 12:37:55.000 [notice] While bootstrapping, fetched this many bytes: 710000 (consensus network-status fetch); 14348 (authority cert fetch); 12532008 (microdescriptor fetch)
tor_proxy | Sep 29 12:37:55.000 [notice] While not bootstrapping, fetched this many bytes: 40427 (consensus network-status fetch); 252 (authority cert fetch); 43890 (microdescriptor fetch)
tor_proxy | Sep 29 13:26:05.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.
tor_proxy | Sep 29 15:28:06.000 [warn] Received http status code 404 (“Not found”) from server 65.108.198.216:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”.

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

2

Hi, I have run into the same issue. Did you manage to fix this?

I am trying to run repo update after I delete the https---github-com-getumbrel-umbrel-apps-git folder,
however I am running into git merge error following:

sudo ~/umbrel/scripts/repo update
Processing: https://github.com/getumbrel/umbrel-apps.git
Updating repo: https://github.com/getumbrel/umbrel-apps.git (master)
Updating c91dae1..18568ba
error: Your local changes to the following files would be overwritten by merge:
	README.md
	bitcoin/docker-compose.yml
	bitcoin/exports.sh
	bitcoin/umbrel-app.yml
	btcpay-server/docker-compose.yml
	btcpay-server/umbrel-app.yml
	chatpad-ai/docker-compose.yml
	chatpad-ai/umbrel-app.yml
	circuitbreaker/docker-compose.yml
	circuitbreaker/umbrel-app.yml
	core-lightning-rtl/docker-compose.yml
	core-lightning-rtl/umbrel-app.yml
	core-lightning/docker-compose.yml
	core-lightning/umbrel-app.yml
	file-browser/docker-compose.yml
	file-browser/umbrel-app.yml
	ghostfolio/docker-compose.yml
	ghostfolio/umbrel-app.yml
	gitea/docker-compose.yml
	gitea/umbrel-app.yml
	heimdall/docker-compose.yml
	heimdall/umbrel-app.yml
	helipad/docker-compose.yml
	helipad/umbrel-app.yml
	home-assistant/docker-compose.yml
	home-assistant/umbrel-app.yml
	immich/docker-compose.yml
	immich/umbrel-app.yml
	invidious/docker-compose.yml
	invidious/umbrel-app.yml
	jam/docker-compose.yml
	jam/umbrel-app.yml
	jellyfin/docker-compose.yml
	jellyfin/umbrel-app.yml
	librespeed/umbrel-app.yml
	lightning-terminal/docker-compose.yml
	lightning-terminal/umbrel-app.yml
	n8n/docker-compose.yml
	n8n/umbrel-app.yml
	oak-node/docker-compose.yml
	oak-node/umbrel-app.yml
	photoprism/docker-compose.yml
	photoprism/umbrel-app.yml
	plex/docker-compose.yml
	plex/umbrel-app.yml
	radarr/docker-compose.yml
	radarr/umbrel-app.yml
	ride-the-lightning/docker-compose.yml
	ride-the-lightning/umbrel-app.yml
	robosats/docker-compose.yml
	robosats/umbrel-app.yml
	rotki/docker-compose.yml
	rotki/umbrel-app.yml
	snort/docker-compose.yml
	snort/umbrel-app.yml
	syncthing/docker-compose.yml
	syncthing/umbrel-app.yml
	tailscale/docker-compose.yml
	tailscale/umbrel-app.yml
	thunderhub/docker-compose.yml
	thunderhub/umbrel-app.yml
	torq/docker-compose.yml
	torq/umbrel-app.yml
	uptime-kuma/docker-compose.yml
	uptime-kuma/umbrel-app.yml
	urbit/docker-compose.yml
	urbit/umbrel-app.yml
	vaultwarden/docker-compose.yml
	vaultwarden/umbrel-app.yml
	whoogle-search/docker-compose.yml
	whoogle-search/umbrel-app.yml
	woofbot-lnd/docker-compose.yml
	woofbot-lnd/umbrel-app.yml
	woofbot/docker-compose.yml
	woofbot/umbrel-app.yml
Please commit your changes or stash them before you merge.
error: The following untracked working tree files would be removed by merge:
	alby-nostr-wallet-connect/images/nwc_1.png
	alby-nostr-wallet-connect/images/nwc_2.png
	alby-nostr-wallet-connect/images/nwc_3.png
	alby-nostr-wallet-connect/images/nwc_icon.svg
Please move or remove them before you merge.
Aborting

Is there a bug lurking?
I am on ver 0.5.4

3

try this

sudo ~/umbrel/scripts/repo remove GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme
sudo ~/umbrel/scripts/repo add GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme
sudo ~/umbrel/scripts/repo checkout GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme

4

I did… i got this error Error: The default Umbrel app repo must be setup first.

5

My App store is also blank. Just got an Umbrel Home and struggling.

I followed the troubleshooting guide and did the below steps:
"If for any reason apps are not loading in your App Store, or you don’t see certain applications populating correctly, run the following command. If you are on a Linux machine, you may need to replace ~/umbrel with the path to your installation directory, as described in Troubleshooting on Linux:

sudo rm -f ~/umbrel/repos/https—github-com-getumbrel-umbrel-apps-git/.git/index.lock && sudo rm -f ~/umbrel/repos/https—github-com-getumbrel-umbrel-apps-git/.git/ORIG_HEAD.lock && sudo ~/umbrel/scripts/repo update
"

The error i then get in terminal is as below:
"
Processing: htt ps://github.com/getumbrel/umbrel-apps.git
Updating repo: GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme (master)
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
error: cannot lock ref ‘refs/remotes/origin/Update-Prowlarr-to-v1.7.4’: unable to resolve reference ‘refs/remotes/origin/Update-Prowlarr-to-v1.7.4’: reference broken
From GitHub - getumbrel/umbrel-apps: The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme
! [new branch] Update-Prowlarr-to-v1.7.4 → origin/Update-Prowlarr-to-v1.7.4 (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/lightning-0.17.0’: unable to resolve reference ‘refs/remotes/origin/lightning-0.17.0’: reference broken
! [new branch] lightning-0.17.0 → origin/lightning-0.17.0 (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/rtl-core’: unable to resolve reference ‘refs/remotes/origin/rtl-core’: reference broken
! [new branch] rtl-core → origin/rtl-core (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-autobrr’: unable to resolve reference ‘refs/remotes/origin/update-autobrr’: reference broken
! [new branch] update-autobrr → origin/update-autobrr (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-bazarr’: unable to resolve reference ‘refs/remotes/origin/update-bazarr’: reference broken
! [new branch] update-bazarr → origin/update-bazarr (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-btcpay’: unable to resolve reference ‘refs/remotes/origin/update-btcpay’: reference broken
! [new branch] update-btcpay → origin/update-btcpay (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-calibre’: unable to resolve reference ‘refs/remotes/origin/update-calibre’: reference broken
! [new branch] update-calibre → origin/update-calibre (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-codeserver’: unable to resolve reference ‘refs/remotes/origin/update-codeserver’: reference broken
! [new branch] update-codeserver → origin/update-codeserver (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-file-browser’: unable to resolve reference ‘refs/remotes/origin/update-file-browser’: reference broken
! [new branch] update-file-browser → origin/update-file-browser (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-firefly’: unable to resolve reference ‘refs/remotes/origin/update-firefly’: reference broken
! [new branch] update-firefly → origin/update-firefly (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-firefox’: unable to resolve reference ‘refs/remotes/origin/update-firefox’: reference broken
! [new branch] update-firefox → origin/update-firefox (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-freshrss’: unable to resolve reference ‘refs/remotes/origin/update-freshrss’: reference broken
! [new branch] update-freshrss → origin/update-freshrss (unable to update local ref)
error: cannot lock ref ‘refs/remotes/origin/update-rtl’: unable to resolve reference ‘refs/remotes/origin/update-rtl’: reference broken
! [new branch] update-rtl → origin/update-rtl (unable to update local ref)
​"

For whatever reason its not able to connect to the github repository.

Any help here is appreciated, I am not technically savvy :frowning: thanks!