Remote Terminal connection issue with MeshCore-Proxy #136

New Issue

Closed

opened 2026-10-05 01:59:38 +02:00 by adam · 10 comments

adam commented 2026-10-05 01:59:38 +02:00

Owner

Copy link

Copy source

It seems the TCP connection to MeshCore-Proxy is having an issue?
(i have followed the guides, but no luck)

Running in docker on a Raspberry 5 (64bit)
both docker containers on same host,

i can connect my MeshCore companion app (phone) to the IP:PORT and it works fine.

When trying to connect via Remote Terminal, I get a radio status in top right: Radio Connecting

docker log:
2026-04-13 13:55:35 - meshcore - INFO - TCP Connection started
2026-04-13 13:55:40 - meshcore - ERROR - No response from meshcore node, disconnecting
2026-04-13 13:55:40 - app.radio - WARNING - Reconnection failed: not connected after connect()
2026-04-13 13:55:45 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change
2026-04-13 13:55:45 - app.radio - INFO - Attempting to reconnect to radio...

It seems the TCP connection to MeshCore-Proxy is having an issue? (i have followed the guides, but no luck) Running in docker on a Raspberry 5 (64bit) both docker containers on same host, i can connect my MeshCore companion app (phone) to the IP:PORT and it works fine. When trying to connect via Remote Terminal, I get a radio status in top right: Radio Connecting docker log: 2026-04-13 13:55:35 - meshcore - INFO - TCP Connection started 2026-04-13 13:55:40 - meshcore - ERROR - No response from meshcore node, disconnecting 2026-04-13 13:55:40 - app.radio - WARNING - Reconnection failed: not connected after connect() 2026-04-13 13:55:45 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change 2026-04-13 13:55:45 - app.radio - INFO - Attempting to reconnect to radio... <!-- github-sync-id:4255517861 -->

adam closed this issue 2026-10-05 01:59:38 +02:00

adam commented 2026-10-05 01:59:39 +02:00

Author

Owner

Copy link

Copy source

Hmm I know that there are other folks out there who are able to connect directly to TCP radios fine. My first suspicion would be around network connectivity -- are you using the right host within docker? They'll need to be on the same Docker network, or with an exposed host port and using host.docker.internal to punch up and out to access ports on the host.

I would be curious what you see from the logs on the proxy (is the connection making it to the proxy?), and with more detailed error reporting from our app (you can alter the environment variable section of your docker compose to have MESHCORE_LOG_LEVEL: DEBUG and see what it spits out when it tries to connect.

Hmm I know that there are other folks out there who are able to connect directly to TCP radios fine. My first suspicion would be around network connectivity -- are you using the right host within docker? They'll need to be on the same Docker network, or with an exposed host port and using `host.docker.internal` to punch up and out to access ports on the host. I would be curious what you see from the logs on the proxy (is the connection making it to the proxy?), and with more detailed error reporting from our app (you can alter the environment variable section of your docker compose to have `MESHCORE_LOG_LEVEL: DEBUG` and see what it spits out when it tries to connect. <!-- github-comment-id:4262606174 -->

adam commented 2026-10-05 01:59:39 +02:00

Author

Owner

Copy link

Copy source

i can confirm, it's not working. i'm using ai-written python proxy and it's working okay. socat is working fine too.
all on same host/port, so network connectivity is known good.

cmdline: meshcore-proxy --serial /dev/ttyACM0 --port 44XX --debug --log-events-verbose
output is redacted, i'm not sure if it's contains any sensitive data

INFO:meshcore_proxy.proxy:Client connected: ('172.20.0.2', 42644)
-> CMD_APPSTART: version=3 | app=mccli
   [13 bytes]: 01032020202020206d63636c69
<- SELF_INFO: name=......... | type=client | public_key=... | tx_power=22 | freq_mhz=868.73 | bw_khz=62.50 | sf=7 | cr=7 | lat=.... | lon=....
   [72 bytes]: ....
<- LOG_DATA [92 bytes]: ....
<- LOG_DATA [92 bytes]: ...
<- LOG_DATA [93 bytes]: .....
<- LOG_DATA [93 bytes]: .....
<- LOG_DATA [93 bytes]: ....
<- LOG_DATA [93 bytes]: ....
<- LOG_DATA [94 bytes]: ......
INFO:meshcore_proxy.proxy:Client disconnected: ('172.20.0.2', 42644)

i can confirm, it's not working. i'm using ai-written python proxy and it's working okay. socat is working fine too. all on same host/port, so network connectivity is known good. cmdline: meshcore-proxy --serial /dev/ttyACM0 --port 44XX --debug --log-events-verbose output is redacted, i'm not sure if it's contains any sensitive data ``` INFO:meshcore_proxy.proxy:Client connected: ('172.20.0.2', 42644) -> CMD_APPSTART: version=3 | app=mccli [13 bytes]: 01032020202020206d63636c69 <- SELF_INFO: name=......... | type=client | public_key=... | tx_power=22 | freq_mhz=868.73 | bw_khz=62.50 | sf=7 | cr=7 | lat=.... | lon=.... [72 bytes]: .... <- LOG_DATA [92 bytes]: .... <- LOG_DATA [92 bytes]: ... <- LOG_DATA [93 bytes]: ..... <- LOG_DATA [93 bytes]: ..... <- LOG_DATA [93 bytes]: .... <- LOG_DATA [93 bytes]: .... <- LOG_DATA [94 bytes]: ...... INFO:meshcore_proxy.proxy:Client disconnected: ('172.20.0.2', 42644) ``` <!-- github-comment-id:4268817593 -->

adam commented 2026-10-05 01:59:40 +02:00

Author

Owner

Copy link

Copy source

no clues from debug on remoteterm side too

remoteterm-1  | 2026-04-17 14:20:21 - app.radio - INFO - Attempting to reconnect to radio...
remoteterm-1  | 2026-04-17 14:20:21 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP)
remoteterm-1  | 2026-04-17 14:20:26 - app.radio - DEBUG - TCP connection established
remoteterm-1  | 2026-04-17 14:20:26 - app.radio - WARNING - Reconnection failed: not connected after connect()
remoteterm-1  | 2026-04-17 14:20:31 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change
remoteterm-1  | 2026-04-17 14:20:31 - app.radio - INFO - Attempting to reconnect to radio...
remoteterm-1  | 2026-04-17 14:20:31 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP)
remoteterm-1  | 2026-04-17 14:20:36 - app.radio - DEBUG - TCP connection established
remoteterm-1  | 2026-04-17 14:20:36 - app.radio - WARNING - Reconnection failed: not connected after connect()
remoteterm-1  | 2026-04-17 14:20:41 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change
remoteterm-1  | 2026-04-17 14:20:41 - app.radio - INFO - Attempting to reconnect to radio...
remoteterm-1  | 2026-04-17 14:20:41 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP)

no clues from debug on remoteterm side too ``` remoteterm-1 | 2026-04-17 14:20:21 - app.radio - INFO - Attempting to reconnect to radio... remoteterm-1 | 2026-04-17 14:20:21 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP) remoteterm-1 | 2026-04-17 14:20:26 - app.radio - DEBUG - TCP connection established remoteterm-1 | 2026-04-17 14:20:26 - app.radio - WARNING - Reconnection failed: not connected after connect() remoteterm-1 | 2026-04-17 14:20:31 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change remoteterm-1 | 2026-04-17 14:20:31 - app.radio - INFO - Attempting to reconnect to radio... remoteterm-1 | 2026-04-17 14:20:31 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP) remoteterm-1 | 2026-04-17 14:20:36 - app.radio - DEBUG - TCP connection established remoteterm-1 | 2026-04-17 14:20:36 - app.radio - WARNING - Reconnection failed: not connected after connect() remoteterm-1 | 2026-04-17 14:20:41 - app.services.radio_lifecycle - WARNING - Radio connection lost, broadcasting status change remoteterm-1 | 2026-04-17 14:20:41 - app.radio - INFO - Attempting to reconnect to radio... remoteterm-1 | 2026-04-17 14:20:41 - app.radio - DEBUG - Connecting to radio at 1.2.3.4:44XX (TCP) ``` <!-- github-comment-id:4268872538 -->

adam commented 2026-10-05 01:59:41 +02:00

Author

Owner

Copy link

Copy source

https://github.com/rgregg/meshcore-proxy/issues/14 probably related

https://github.com/rgregg/meshcore-proxy/issues/14 probably related <!-- github-comment-id:4268959723 -->

adam commented 2026-10-05 01:59:41 +02:00

Author

Owner

Copy link

Copy source

Yeah, with that issue and the fact that socat works fine, I'm going to consider this an issue in the upstream. I'll keep this open until things are fixed, but I don't think this is anything that we can do much about.

I'm going to guess that this probably has something to do with some flimsiness within meshcore_py; I know that it is not the most resilient thing in the world to line level weirdness (already pr'd one bug fix for that).

Yeah, with that issue and the fact that socat works fine, I'm going to consider this an issue in the upstream. I'll keep this open until things are fixed, but I don't think this is anything that we can do much about. I'm going to guess that this probably has something to do with some flimsiness within meshcore_py; I know that it is not the most resilient thing in the world to line level weirdness (already pr'd one bug fix for that). <!-- github-comment-id:4269258372 -->

adam commented 2026-10-05 01:59:42 +02:00

Author

Owner

Copy link

Copy source

i can confirm, it's not working. i'm using ai-written python proxy and it's working okay. socat is working fine too. all on same host/port, so network connectivity is known good.

cmdline: meshcore-proxy --serial /dev/ttyACM0 --port 44XX --debug --log-events-verbose output is redacted, i'm not sure if it's contains any sensitive data

INFO:meshcore_proxy.proxy:Client connected: ('172.20.0.2', 42644)
-> CMD_APPSTART: version=3 | app=mccli
   [13 bytes]: 01032020202020206d63636c69
<- SELF_INFO: name=......... | type=client | public_key=... | tx_power=22 | freq_mhz=868.73 | bw_khz=62.50 | sf=7 | cr=7 | lat=.... | lon=....
   [72 bytes]: ....
<- LOG_DATA [92 bytes]: ....
<- LOG_DATA [92 bytes]: ...
<- LOG_DATA [93 bytes]: .....
<- LOG_DATA [93 bytes]: .....
<- LOG_DATA [93 bytes]: ....
<- LOG_DATA [93 bytes]: ....
<- LOG_DATA [94 bytes]: ......
INFO:meshcore_proxy.proxy:Client disconnected: ('172.20.0.2', 42644)

Thanks, i tried with SOCAT and that is stable and running with Remote Term.

> i can confirm, it's not working. i'm using ai-written python proxy and it's working okay. socat is working fine too. all on same host/port, so network connectivity is known good. > > cmdline: meshcore-proxy --serial /dev/ttyACM0 --port 44XX --debug --log-events-verbose output is redacted, i'm not sure if it's contains any sensitive data > > ``` > INFO:meshcore_proxy.proxy:Client connected: ('172.20.0.2', 42644) > -> CMD_APPSTART: version=3 | app=mccli > [13 bytes]: 01032020202020206d63636c69 > <- SELF_INFO: name=......... | type=client | public_key=... | tx_power=22 | freq_mhz=868.73 | bw_khz=62.50 | sf=7 | cr=7 | lat=.... | lon=.... > [72 bytes]: .... > <- LOG_DATA [92 bytes]: .... > <- LOG_DATA [92 bytes]: ... > <- LOG_DATA [93 bytes]: ..... > <- LOG_DATA [93 bytes]: ..... > <- LOG_DATA [93 bytes]: .... > <- LOG_DATA [93 bytes]: .... > <- LOG_DATA [94 bytes]: ...... > INFO:meshcore_proxy.proxy:Client disconnected: ('172.20.0.2', 42644) > ``` Thanks, i tried with SOCAT and that is stable and running with Remote Term. <!-- github-comment-id:4271107552 -->

adam commented 2026-10-05 01:59:43 +02:00

Author

Owner

Copy link

Copy source

Just something to be aware of; RemoteTerm doesn't technically have any problems running over a proxy, but it does take full control of the radio, offloading all channels and contacts unloading on only contacts that it decides should be on the radio. So, it can cause a lot of shift underneath another client that's not expecting to see changes in the radio, and the radio changing configuration underneath RemoteTerm can cause problems with messages going to the wrong.

Just something to be aware of; RemoteTerm doesn't technically have any problems running over a proxy, but it does take full control of the radio, offloading all channels and contacts unloading on only contacts that it decides should be on the radio. So, it can cause a lot of shift underneath another client that's not expecting to see changes in the radio, and the radio changing configuration underneath RemoteTerm can cause problems with messages going to the wrong. <!-- github-comment-id:4271139209 -->

adam commented 2026-10-05 01:59:43 +02:00

Author

Owner

Copy link

Copy source

proxy works with this docker build
https://github.com/rgregg/meshcore-proxy/pkgs/container/meshcore-proxy/760329377?tag=dev-13

proxy works with this docker build https://github.com/rgregg/meshcore-proxy/pkgs/container/meshcore-proxy/760329377?tag=dev-13 <!-- github-comment-id:4430975005 -->

adam commented 2026-10-05 01:59:44 +02:00

Author

Owner

Copy link

Copy source

Woot! Looks fixed on that thread too.

Woot! Looks fixed on that thread too. <!-- github-comment-id:4445982956 -->

adam commented 2026-10-05 01:59:45 +02:00

Author

Owner

Copy link

Copy source

proxy works with this docker build https://github.com/rgregg/meshcore-proxy/pkgs/container/meshcore-proxy/760329377?tag=dev-13

Can confirm works with building latest docker from source on meshcore-proxy.
RemoteTerm has been working perfect all along :-)

> proxy works with this docker build https://github.com/rgregg/meshcore-proxy/pkgs/container/meshcore-proxy/760329377?tag=dev-13 Can confirm works with building latest docker from source on meshcore-proxy. RemoteTerm has been working perfect all along :-) <!-- github-comment-id:4448725658 -->

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

dependabot/npm_and_yarn/frontend/npm_and_yarn-b3b4accef5

dependabot/uv/uv-10713fdc8d

alternate-repeater-detail-fetch

make-repeater-sortable

fix/cli-response-scoped-subscription

tracked-contact-telemetry

thin-docker

tcp-proxy

repeater-error-count

radio-config-export

channel-mute

extended-contact-fetch-timeout

web-push

ha

migration-updates

runtimes-and-sessions

aur-packaging

arch-publishing

self-reexec-on-windows

migrate-favorites

bugbash-v7

testbranch

move-to-fk-pragma

gnomeadrift/repeater_telemetry_history

use-nginx-docker

settings-scroll-fix

richer-install-script

fix-room-server-ordering

bot-safety

room_server

better-path-management

dm-ingest-unification

keep-track-of-channel-state

notifications

codex-refactor

multibyte-take-2

multibyte

fanout_bus

community-mqtt

loopback

actually-cool-ui-concepts

3.17.1

3.17.0

3.16.2

3.16.1

3.16.0

3.15.2

3.15.1

3.15.0

3.14.1

3.14.0

3.13.0

3.12.3

3.12.2

3.12.1

3.12.0

3.11.3

3.11.2

3.11.1

3.11.0

3.10.0

3.9.0

3.8.0

3.7.1

3.7.0

3.6.7

3.6.3

3.6.2

3.6.1

3.6.0

3.5.0

3.4.1

3.4.0

3.3.0

3.2.0

3.1.1

3.0.0

2.7.9

2.7.8

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Wojcieszonek)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#136