# All apps: onionsite not found

**URL:** <https://community.umbrel.com/t/all-apps-onionsite-not-found/6031>\
**Category:** Support and Troubleshooting\
**Created:** [January 29, 2022, 11:47am UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031 "2022-01-29T11:47:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![relic](https://avatars.discourse-cdn.com/v4/letter/r/3ab097/32.png) [@relic](https://community.umbrel.com/u/relic)\
**Post date:** [January 29, 2022, 11:47am UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/1 "2022-01-29T11:47:04Z")

</div>

Hi All,

All my Umbrel apps don’t open, it says onion site not found.

another thing that’s unusual and might be related: the apps are all stuck in “Starting…” mode, the symbols are flickering as if they are trying to boot up.

Any help is appreciated!

Relic

---

<div class="post-metadata">

**Author:** ![DarthCoin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/darthcoin/32/1628_2.png) [@DarthCoin](https://community.umbrel.com/u/DarthCoin)\
**Post date:** [January 29, 2022, 3:18pm UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/2 "2022-01-29T15:18:45Z")

</div>

restart your node machine.

---

<div class="post-metadata">

**Author:** ![relic](https://avatars.discourse-cdn.com/v4/letter/r/3ab097/32.png) [@relic](https://community.umbrel.com/u/relic)\
**Post date:** [January 29, 2022, 3:48pm UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/3 "2022-01-29T15:48:14Z")

</div>

Thank you for your reply. I tried restarting it, does not work, unfortunately.

---

<div class="post-metadata">

**Author:** ![supriseflash](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/supriseflash/32/2509_2.png) [@supriseflash](https://community.umbrel.com/u/supriseflash)\
**Post date:** [February 24, 2022, 6:53am UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/4 "2022-02-24T06:53:25Z")

</div>

I am also having this problem. I wanted to access the apps while I was away from my home network on TOR. None of the onionsites will load.

"Onionsite Not Found

The most likely cause is that the onionsite is offline. Contact the onionsite administrator.

Details: 0xF0 — The requested onion service descriptor can’t be found on the hashring and therefore the service is not reachable by the client."

---

<div class="post-metadata">

**Author:** ![Eluc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/eluc/32/1883_2.png) [@Eluc](https://community.umbrel.com/u/Eluc)\
**Post date:** [February 25, 2022, 11:29pm UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/5 "2022-02-25T23:29:25Z")

</div>

I have a similar issue since I did the last update. Most app are shown as starting from Onion but from local IP they all works.  
Note that some app still work in onion and when I restart my Umbrel, some app that didn’t work are now working but other that did work are no more working…  
Any idea what I can try next?

---

<div class="post-metadata">

**Author:** ![MacMartin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/macmartin/32/2325_2.png) [@MacMartin](https://community.umbrel.com/u/MacMartin)\
**Post date:** [March 13, 2022, 8:25pm UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/6 "2022-03-13T20:25:01Z")

</div>

Had the same, solution for me (=stupid) was:

i wrote down the .onion-Address. Weeks later I had to restart the Node with my 24 words…  
weeks later (forgot about it) tried to login via Tor remotely. (with the old address) … node restart gives you a new .-onion-adress ! … so check if you really use the up-to-date-onion 🙂

---

<div class="post-metadata">

**Author:** ![miyagi](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@miyagi](https://community.umbrel.com/u/miyagi)\
**Post date:** [March 29, 2022, 2:13am UTC](https://community.umbrel.com/t/all-apps-onionsite-not-found/6031/7 "2022-03-29T02:13:43Z")

</div>

I had this same problem today. Luckily restarting my node corrected it.
