# Unable to open channel **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [August 4, 2023, 10:42pm UTC](https://community.umbrel.com/t/unable-to-open-channel/13254 "2023-08-04T22:42:06Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![upmrty](https://avatars.discourse-cdn.com/v4/letter/u/cc9497/32.png) [@upmrty](https://community.umbrel.com/u/upmrty)\ **Post date:** [August 4, 2023, 10:42pm UTC](https://community.umbrel.com/t/unable-to-open-channel/13254/1 "2023-08-04T22:42:06Z")
Good afternoon, I’m trying to open a channel with the Lightning.Watch node, using the Lightning Terminal app, and I’m getting the following error: ‘‘ **rpc error. code = Unknown desc = invalid vertex string length of 134, want 66** ’’ I changed some options and got the following error. **‘‘rpc error. code = Unknown desc = tor general error’’** I used troubleshoting and got the following result: # ===================== = Umbrel debug info = ## Umbrel version 0.5.4 ## Memory usage ``` total used free shared buff/cache available ``` Mem.: 15G 4,1G 360M 21M 11G 11G Swap: 2,0G 21M 2,0G lightning: 331386 3% bitcoin: 49343 3% lndg: 4286% thunderhub: 434 4% lightning-terminal: 43 3% total: 25,9% system: % ## Memory monitor logs 2023-07-22 16:20:45 Memory monitor running! 10360 ? S 0:00 bash ./scripts/memory-monitor Memory monitor is already running 2023-07-22 17:41:28 Memory monitor running! 2023-07-24 12:57:42 Memory monitor running! 2023-07-24 18:35:29 Memory monitor running! 2023-08-02 13:05:05 Memory monitor running! ## Filesystem information Sist. Arq. Tam. Usado Disp. Uso% Montado em /dev/nvme0n1p2 916G 607G 263G 70% / /dev/nvme0n1p2 916G 607G 263G 70% / ## Karen logs Pulling web … extracting (100.0%) Pulling web … pull complete Pulling web … extracting (1.0%) Pulling web … extracting (26.0%) Pulling web … extracting (49.9%) Pulling web … extracting (99.9%) Pulling web … extracting (100.0%) Pulling web … pull complete Pulling web … extracting (1.1%) Pulling web … extracting (20.1%) Pulling web … extracting (36.9%) Pulling web … extracting (68.2%) Pulling web … extracting (100.0%) Pulling web … pull complete Pulling web … extracting (2.2%) Pulling web … extracting (100.0%) Pulling web … extracting (100.0%) Pulling web … pull complete Pulling web … digest: sha256:1260fad6f3930c2933… Pulling web … status: downloaded newer image fo… Pulling web … done Starting app lightning-terminal… Creating lightning-terminal\_app\_proxy\_1 … Creating lightning-terminal\_web\_1 … Creating lightning-terminal\_app\_proxy\_1 … done Creating lightning-terminal\_web\_1 … done Saving app lightning-terminal in DB… Successfully installed app lightning-terminal Got signal: backup karen is getting triggered! Deriving keys… Creating backup… Adding random padding… 1+0 registros de entrada 1+0 registros de saída 620 bytes copiados, 4,3744e-05 s, 14,2 MB/s Creating encrypted tarball… backup/ backup/channel.backup backup/.padding 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 100 1630 0 0 100 1630 0 924 0:00:01 0:00:01 --:–:-- 924 100 1776 100 146 100 1630 59 659 0:00:02 0:00:02 --:–:-- 719 {“message”:“Successfully uploaded backup 1691187315094.tar.gz.pgp for backup ID 20755a4b9c753f1ae6dce1983bb9acc331ade8e3d7432a8b9c14bd6ef4879b1b”} # ====== Backup success ======= Got signal: debug karen is getting triggered! ## Docker containers NAMES STATUS lightning-terminal\_app\_proxy\_1 Up About an hour lightning-terminal\_web\_1 Up About an hour bitcoin\_server\_1 Up 2 days bitcoin\_i2pd\_daemon\_1 Up 2 days bitcoin\_app\_proxy\_1 Up 2 days bitcoin\_bitcoind\_1 Up 2 days bitcoin\_tor\_1 Up 2 days thunderhub\_app\_proxy\_1 Up 2 days thunderhub\_web\_1 Up 2 days lightning\_app\_proxy\_1 Up 2 days lightning\_tor\_1 Up 2 days lightning\_lnd\_1 Up 2 hours lightning\_app\_1 Up 2 days lndg\_app\_proxy\_1 Up 2 days lndg\_web\_1 Up 2 days nginx Up 2 days manager Up 2 days dashboard Up 2 days tor\_proxy Up 2 days auth Up 2 days ## Umbrel logs Attaching to manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:36 GMT] “GET /v1/system/update-status HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:42 GMT] “GET /v1/system/memory HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:42 GMT] “GET /v1/system/storage HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:42 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:43 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:43 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:45 GMT] “POST /v1/system/debug HTTP/1.0” 200 17 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:46 GMT] “GET /v1/system/debug-result HTTP/1.0” 200 23 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:48 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Fri, 04 Aug 2023 22:23:49 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” manager | manager | umbrel-manager ## Tor Proxy logs Attaching to tor\_proxy tor\_proxy | Aug 04 22:22:54.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $547B98B764B0CC7EE454DF1BEE517D2C50B6223B~ForPrivacyNET [ixPVl+9D7zeSH4aJIXMzWn2BhxJjZnELkeMpsqHWyu8] at 185.220.101.37. Retrying on a new circuit. tor\_proxy | Aug 04 22:22:54.000 [notice] Tried for 125 seconds to get a connection to [scrubbed]:9911. Giving up. tor\_proxy | Aug 04 22:23:02.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $67DE7272159CFE628CDF17D2A719A6E395BAA4C8~flokinet2 [lRs0JpZdjFOSf9qVdIg4KZF/AddiVW0uVMgSo3c1N3g] at 185.246.188.74. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:05.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor\_proxy | Aug 04 22:23:30.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $7ABED1F6664D1153F1402838D3B32AF6F2CABE17~ForPrivacyNET [L1DO6JERnLhxKCTstb9Q9ZD/okmRNQxywJ/WYlOGO90] at 185.220.101.39. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:33.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $7ABED1F6664D1153F1402838D3B32AF6F2CABE17~ForPrivacyNET [L1DO6JERnLhxKCTstb9Q9ZD/okmRNQxywJ/WYlOGO90] at 185.220.101.39. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:33.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $7ABED1F6664D1153F1402838D3B32AF6F2CABE17~ForPrivacyNET [L1DO6JERnLhxKCTstb9Q9ZD/okmRNQxywJ/WYlOGO90] at 185.220.101.39. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:45.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $FD162811044DD109E9B9A59242E5975CB8BD67AD~plithismos [iJhLQJIC2wqPs7J3VNqPcngcyAYURy3qyJVB831kpGY] at 198.98.48.128. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:48.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $FD162811044DD109E9B9A59242E5975CB8BD67AD~plithismos [iJhLQJIC2wqPs7J3VNqPcngcyAYURy3qyJVB831kpGY] at 198.98.48.128. Retrying on a new circuit. tor\_proxy | Aug 04 22:23:48.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $FD162811044DD109E9B9A59242E5975CB8BD67AD~plithismos [iJhLQJIC2wqPs7J3VNqPcngcyAYURy3qyJVB831kpGY] at 198.98.48.128. Retrying on a new circuit. ## App logs bitcoin Attaching to bitcoin\_server\_1, bitcoin\_i2pd\_daemon\_1, bitcoin\_app\_proxy\_1, bitcoin\_bitcoind\_1, bitcoin\_tor\_1 bitcoind\_1 | 2023-08-04T21:43:00Z New outbound peer connected: version: 70015, blocks=801689, peer=748 (block-relay-only) bitcoind\_1 | 2023-08-04T21:44:14Z New outbound peer connected: version: 70016, blocks=801689, peer=749 (block-relay-only) bitcoind\_1 | 2023-08-04T21:48:46Z Saw new header hash=00000000000000000003b8518f0b98551462bd1a5765f3fb1d9b02a1c97e375e height=801690 bitcoind\_1 | 2023-08-04T21:48:46Z [net] Saw new cmpctblock header hash=00000000000000000003b8518f0b98551462bd1a5765f3fb1d9b02a1c97e375e peer=388 bitcoind\_1 | 2023-08-04T21:48:46Z UpdateTip: new best=00000000000000000003b8518f0b98551462bd1a5765f3fb1d9b02a1c97e375e height=801690 version=0x20600000 log2\_work=94.340164 tx=874292592 date=‘2023-08-04T21:48:27Z’ progress=1.000000 cache=60.3MiB(304236txo) bitcoind\_1 | 2023-08-04T21:57:30Z New outbound peer connected: version: 70015, blocks=801689, peer=756 (block-relay-only) bitcoind\_1 | 2023-08-04T22:04:14Z Saw new header hash=000000000000000000019093c7a53733d8c3379ca738f12f7aa095102566d34d height=801691 bitcoind\_1 | 2023-08-04T22:04:14Z [net] Saw new cmpctblock header hash=000000000000000000019093c7a53733d8c3379ca738f12f7aa095102566d34d peer=388 bitcoind\_1 | 2023-08-04T22:04:14Z UpdateTip: new best=000000000000000000019093c7a53733d8c3379ca738f12f7aa095102566d34d height=801691 version=0x3fff0000 log2\_work=94.340177 tx=874295568 date=‘2023-08-04T22:03:41Z’ progress=1.000000 cache=61.7MiB(315667txo) app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … i2pd\_daemon\_1 | 21:56:37@661/error - Tunnel: Tunnel with id 3369346787 already exists i2pd\_daemon\_1 | 21:58:55@661/error - Tunnel: Tunnel with id 805250456 already exists i2pd\_daemon\_1 | 22:10:25@661/error - Tunnel: Tunnel with id 2996048378 already exists i2pd\_daemon\_1 | 22:11:46@661/error - Tunnel: Tunnel with id 2553645498 already exists i2pd\_daemon\_1 | 22:12:21@661/error - Tunnel: Tunnel with id 815464207 already exists i2pd\_daemon\_1 | 22:20:56@557/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 22:21:02@717/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 22:21:02@717/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 22:21:11@999/error - SSU2: RelayIntro unknown router to introduce i2pd\_daemon\_1 | 22:21:33@557/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.9 - - [Fri, 04 Aug 2023 22:18:21 GMT] “GET /v1/bitcoind/info/connections HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” server\_1 | server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.9 - - [Fri, 04 Aug 2023 22:18:26 GMT] “GET /v1/bitcoind/info/stats HTTP/1.1” 200 126 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” server\_1 | server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.9 - - [Fri, 04 Aug 2023 22:18:26 GMT] “GET /v1/bitcoind/info/connections HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0” server\_1 | server\_1 | umbrel-middleware tor\_1 | Aug 04 18:19:38.000 [warn] Received http status code 404 (“Not found”) from server 162.19.204.163:9000 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”. tor\_1 | Aug 04 22:05:17.000 [notice] Heartbeat: Tor’s uptime is 2 days 6:00 hours, with 18 circuits open. I’ve sent 465.09 MB and received 1.04 GB. I’ve received 386 connections on IPv4 and 0 on IPv6. I’ve made 740 connections with IPv4 and 0 with IPv6. tor\_1 | Aug 04 22:05:17.000 [notice] While bootstrapping, fetched this many bytes: 662793 (consensus network-status fetch); 14104 (authority cert fetch); 10652905 (microdescriptor fetch) tor\_1 | Aug 04 22:05:17.000 [notice] While not bootstrapping, fetched this many bytes: 1540483 (consensus network-status fetch); 10392 (authority cert fetch); 3860537 (microdescriptor fetch) tor\_1 | Aug 04 22:05:17.000 [notice] Average packaged cell fullness: 38.798%. TLS write overhead: 3% lightning Attaching to lightning\_app\_proxy\_1, lightning\_tor\_1, lightning\_lnd\_1, lightning\_app\_1 app\_1 | Checking LND status… app\_1 | LND already unlocked! app\_1 | Checking LND status… app\_1 | LND already unlocked! app\_1 | Checking LND status… app\_1 | LND already unlocked! app\_1 | [backup-monitor] Checking channel backup… app\_1 | [backup-monitor] Sleeping… app\_1 | Checking LND status… app\_1 | LND already unlocked! app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … lnd\_1 | 2023-08-04 22:20:57.796 [ERR] BTCN: Unable to rebroadcast transaction 0b08b25512fb4968bb8be56dabda39f1e421ff9234f73e69079fd28554e7fa1f: -27: Transaction already in block chain lnd\_1 | 2023-08-04 22:21:55.757 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0) lnd\_1 | 2023-08-04 22:21:55.757 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0) lnd\_1 | 2023-08-04 22:21:57.757 [INF] CRTR: Processed channels=0 updates=48 nodes=0 in last 59.999322338s lnd\_1 | 2023-08-04 22:21:57.796 [ERR] BTCN: Unable to rebroadcast transaction 0b08b25512fb4968bb8be56dabda39f1e421ff9234f73e69079fd28554e7fa1f: -27: Transaction already in block chain lnd\_1 | 2023-08-04 22:22:39.787 [INF] DISC: GossipSyncer(0285a9bdd8f6e510bdd48a5d680574abdfe2a3ca3124367d33cb13c1ed9872023b): applying new update horizon: start=2023-08-04 22:22:39 +0000 UTC, end=2159-09-11 04:50:54 +0000 UTC, backlog\_size=53 lnd\_1 | 2023-08-04 22:22:55.757 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0) lnd\_1 | 2023-08-04 22:22:55.757 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0) lnd\_1 | 2023-08-04 22:22:57.757 [INF] CRTR: Processed channels=0 updates=84 nodes=1 in last 1m0.000549984s lnd\_1 | 2023-08-04 22:22:57.797 [ERR] BTCN: Unable to rebroadcast transaction 0b08b25512fb4968bb8be56dabda39f1e421ff9234f73e69079fd28554e7fa1f: -27: Transaction already in block chain tor\_1 | Aug 04 11:44:29.000 [warn] Received http status code 404 (“Not found”) from server 46.20.35.112:9001 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”. tor\_1 | Aug 04 16:05:15.000 [notice] Heartbeat: Tor’s uptime is 2 days 0:00 hours, with 16 circuits open. I’ve sent 39.63 MB and received 44.25 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 248 connections with IPv4 and 0 with IPv6. tor\_1 | Aug 04 16:05:15.000 [notice] While bootstrapping, fetched this many bytes: 663240 (consensus network-status fetch); 14104 (authority cert fetch); 10647181 (microdescriptor fetch) tor\_1 | Aug 04 16:05:15.000 [notice] While not bootstrapping, fetched this many bytes: 1380366 (consensus network-status fetch); 13125 (authority cert fetch); 2724983 (microdescriptor fetch) tor\_1 | Aug 04 16:51:37.000 [notice] No circuits are opened. Relaxed timeout for circuit 3151 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [3 similar message(s) suppressed in last 25920 seconds] tor\_1 | Aug 04 22:05:15.000 [notice] Heartbeat: Tor’s uptime is 2 days 6:00 hours, with 31 circuits open. I’ve sent 44.08 MB and received 48.96 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 251 connections with IPv4 and 0 with IPv6. tor\_1 | Aug 04 22:05:15.000 [notice] While bootstrapping, fetched this many bytes: 663240 (consensus network-status fetch); 14104 (authority cert fetch); 10647181 (microdescriptor fetch) tor\_1 | Aug 04 22:05:15.000 [notice] While not bootstrapping, fetched this many bytes: 1530719 (consensus network-status fetch); 13125 (authority cert fetch); 3855004 (microdescriptor fetch) lightning-terminal Attaching to lightning-terminal\_app\_proxy\_1, lightning-terminal\_web\_1 web\_1 | 2023-08-04 22:02:15.828 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/ListSessions web\_1 | 2023-08-04 22:02:15.842 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/ListSessions web\_1 | 2023-08-04 22:02:18.080 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/AddSession web\_1 | 2023-08-04 22:02:18.092 [WRN] LITD: Kicking off deadline timer for first connection for session 03c1ed6e0fdd2ee97b6d3cebb127e6b019f460bb53e3dea30f8f434033e5639786. A successful connection must be made in the next 9m59.988539638s web\_1 | 2023-08-04 22:02:18.092 [INF] SESS: Mailbox RPC server listening on mailbox:3896367a9bb657881a6eb8b20bb8faefe7e8ed3ff8f6c5896c4b2fc47f639dab8dba47ecc0f601ca0e869b1a186f5fd3f464e26213b17872f7b8e5637a25668f@mailbox.terminal.lightning.today:443 web\_1 | 2023-08-04 22:02:18.169 [INF] LITD: Handling gRPC web request: /litrpc.Sessions/ListSessions web\_1 | 2023-08-04 22:03:06.033 [INF] LOOPD: Monitor request received web\_1 | 2023-08-04 22:04:15.283 [INF] RPCS: Received new block notification: height=801691 web\_1 | 2023-08-04 22:08:53.946 [WRN] GRPC: [transport] transport: http2Server.HandleStreams failed to read frame: error decrypting payload: error reading from go-back-n: cannot receive, gbn exited web\_1 | 2023-08-04 22:18:27.741 [WRN] GRPC: [transport] transport: http2Server.HandleStreams failed to read frame: error decrypting payload: error reading from go-back-n: cannot receive, gbn exited app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } app\_proxy\_1 | [HPM] Client disconnected app\_proxy\_1 | [HPM] Client disconnected app\_proxy\_1 | [HPM] WebSocket error: Error: read ECONNRESET app\_proxy\_1 | at TCP.onStreamRead (node:internal/stream\_base\_commons:217:20) { app\_proxy\_1 | errno: -104, app\_proxy\_1 | code: ‘ECONNRESET’, app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } lndg Attaching to lndg\_app\_proxy\_1, lndg\_web\_1 app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … web\_1 | [04/Aug/2023 21:06:59] “GET /api/invoices/?state=1&is\_revenue=true&settle\_date\_\_gte=2023-07-28T21%3A06%3A58&limit=100000&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /api/onchain/?time\_stamp\_\_gte=2023-07-28T21%3A06%3A58&limit=100000&format=json HTTP/1.1” 200 1554 web\_1 | [04/Aug/2023 21:06:59] “GET /api/failedhtlcs/?wire\_failure\_\_lt=99&limit=10&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /api/payments/?creation\_date\_\_gte=2023-07-28T21%3A06%3A58&status=2&limit=100000&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /api/closures/?close\_height\_\_gte=800677&limit=100000&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /api/channels/?is\_open=true&limit=100000&format=json HTTP/1.1” 200 1239 web\_1 | [04/Aug/2023 21:06:59] “GET /favicon.ico HTTP/1.1” 302 0 web\_1 | [04/Aug/2023 21:06:59] “GET /api/payments/?creation\_date\_\_lt=2023-07-28T21%3A06%3A58&status\_\_lt=3&limit=10&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /api/forwards/?forward\_date\_\_lt=2023-07-28T21%3A06%3A58&limit=20&format=json HTTP/1.1” 200 52 web\_1 | [04/Aug/2023 21:06:59] “GET /static/favicon.ico HTTP/1.1” 200 15406 thunderhub # Attaching to thunderhub\_app\_proxy\_1, thunderhub\_web\_1 web\_1 | json: { message: ‘Not found’, code: ‘NOT\_FOUND’ }, web\_1 | level: ‘debug’, web\_1 | message: ‘Get userInfo from LnMarkets’, web\_1 | timestamp: ‘2023-08-04T22:15:57.492Z’ web\_1 | } web\_1 | { web\_1 | message: ‘Client disconnected: fQXk0fnufFhCAeM5AAAH’, web\_1 | level: ‘info’, web\_1 | timestamp: ‘2023-08-04T22:16:08.413Z’ web\_1 | } app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … app\_proxy\_1 | Validating token: e7f12fc527c9 … # ==== Result ==== ==== END ===== I would be very grateful if someone can help me. ---
**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\ **Post date:** [August 5, 2023, 1:42pm UTC](https://community.umbrel.com/t/unable-to-open-channel/13254/2 "2023-08-05T13:42:19Z")
Not sure what’s causing this specifically, but I always seem to have issues connecting to my node over RPC too. Have you tried opening the channel via Thunderhub or ride the lightning? If it’s via a node key or URI that’s probably easiest