# Can only connect to Umbrel on TOR

**URL:** <https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457>\
**Category:** Support and Troubleshooting\
**Created:** [November 27, 2022, 3:18am UTC](https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457 "2022-11-27T03:18:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![quantumavs](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@quantumavs](https://community.umbrel.com/u/quantumavs)\
**Post date:** [November 27, 2022, 3:18am UTC](https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457/1 "2022-11-27T03:18:25Z")

</div>

I’ve been operating my Umbrel node for months without problem, but in the past few weeks I haven’t been able to ssh in or connect to it via umbrel.local. However, I am able to connect to it through its onion address on TOR. Anyone have ideas what’s going on?

---

<div class="post-metadata">

**Author:** ![quantumavs](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@quantumavs](https://community.umbrel.com/u/quantumavs)\
**Post date:** [December 4, 2022, 7:31pm UTC](https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457/2 "2022-12-04T19:31:57Z")

</div>

Bumping since I’m still having trouble with this

---

<div class="post-metadata">

**Author:** ![WalletInspector](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/walletinspector/32/375_2.png) [@WalletInspector](https://community.umbrel.com/u/WalletInspector)\
**Post date:** [December 7, 2022, 10:45pm UTC](https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457/3 "2022-12-07T22:45:00Z")

</div>

maybe the ip address changed

---

<div class="post-metadata">

**Author:** ![quantumavs](https://avatars.discourse-cdn.com/v4/letter/q/cdc98d/32.png) [@quantumavs](https://community.umbrel.com/u/quantumavs)\
**Post date:** [December 16, 2022, 11:34pm UTC](https://community.umbrel.com/t/can-only-connect-to-umbrel-on-tor/10457/4 "2022-12-16T23:34:11Z")

</div>

Yes, this was basically correct. Looks like the mDNS name had changed when I had installed the new update and restarted. Thanks!
