# Socks5() connect to ... failed: general failure

**URL:** <https://community.umbrel.com/t/socks5-connect-to-failed-general-failure/1365>\
**Category:** Support and Troubleshooting\
**Created:** [June 10, 2021, 6:15pm UTC](https://community.umbrel.com/t/socks5-connect-to-failed-general-failure/1365 "2021-06-10T18:15:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![J0nsan](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/j0nsan/32/61_2.png) [@J0nsan](https://community.umbrel.com/u/J0nsan)\
**Post date:** [June 10, 2021, 6:15pm UTC](https://community.umbrel.com/t/socks5-connect-to-failed-general-failure/1365/1 "2021-06-10T18:15:31Z")

</div>

Hi there,

I already had this problem about 10 days ago. Now it happend for the second time. It went like this:  
The node cant be reached via umbrel.local on Chrome anymore and apps are not reachable (thats the browser i have the mempool app and the umbrel site always open on)  
When I open the same links in another browser I’m able to login/show the mempool. But it seems to have gotten stuck some hours ago. The node shows 0 peers.

If I produce the logs the following is listed under Bitcoin Core logs:

```
bitcoin | 2021-06-10T12:57:45Z Socks5() connect to ...:8333 failed: general failure
bitcoin | 2021-06-10T13:00:06Z UpdateTip: new best=0000000000000000000c315079c9390cd0df9fc3c21151372b619ead840b4fbf height=687059 version=0x3fffe004 log2_work=92.931823 tx=648287437 date='2021-06-10T12:59:54Z' progress=1.000000 cache=120.4MiB(848897txo)
bitcoin | 2021-06-10T13:07:26Z UpdateTip: new best=000000000000000000018ac8360de976c4af0eec504754c6ae15f84c5b81cca0 height=687060 version=0x20c00004 log2_work=92.931837 tx=648288902 date='2021-06-10T13:07:11Z' progress=1.000000 cache=120.9MiB(852795txo)
bitcoin | 2021-06-10T13:16:03Z UpdateTip: new best=000000000000000000007b1adb713bec946ef2f25527220aab48c370f1f69a2e height=687061 version=0x20000004 log2_work=92.931851 tx=648290286 date='2021-06-10T13:15:41Z' progress=1.000000 cache=121.1MiB(854364txo)
bitcoin | 2021-06-10T13:16:03Z Pre-allocating up to position 0x700000 in fltr00404.dat
bitcoin | 2021-06-10T13:46:35Z Socks5() connect to ...:8333 failed: connection refused
bitcoin | 2021-06-10T13:47:23Z Pre-allocating up to position 0x1000000 in rev02615.dat
bitcoin | 2021-06-10T13:47:23Z UpdateTip: new best=00000000000000000001ee66ebf42ed5561a6afb6b14a4b32df5c9ce241b1ccf height=687062 version=0x20c00004 log2_work=92.931864 tx=648293064 date='2021-06-10T13:46:45Z' progress=1.000000 cache=122.7MiB(867800txo)
bitcoin | 2021-06-10T13:47:23Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2021-06-10T13:52:49Z Socks5() connect to ...:8333 failed: general failure
bitcoin | 2021-06-10T14:22:41Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2118 seconds 

```

The Tor logs show the following:

```
tor | Jun 10 17:22:18.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:9735. Giving up. (waiting for circuit)
tor | Jun 10 17:22:36.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.

```

Any ideas how to fix that? Sure rebooting seems to fix it, but thats no long time solution.  
Is Tor simply down for everyone?

Thank you! 😁

---

<div class="post-metadata">

**Author:** ![josferr19](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@josferr19](https://community.umbrel.com/u/josferr19)\
**Post date:** [January 4, 2022, 7:31pm UTC](https://community.umbrel.com/t/socks5-connect-to-failed-general-failure/1365/2 "2022-01-04T19:31:06Z")

</div>

Hi, did you get any fix here?  
I have the same issue.  
thanks