$ balena ssh 79a1dd9
Connecting to: 79a1dd9
BalenaRequestError: Request error: tunneling socket could not be established, cause=connect ECONNREFUSED 172.18.0.6:3128
If you need help, don’t hesitate in contacting us at:
This issue appears to be unrelated to ssh domain name.
I looks like it is more likely something to do with network configuration on either host instance or remote device.
I believe 172.18.0.6 is the IP of address of your remote device running Balena host OS? The first thing I would do is start using some network tools like telnet to check that your Balena instance can reach the device at that IP and then check if there is anything listening on that port.
I’m getting the same problem. I also get the same thing for the device reboot and device shutdown commands. The IP address shown in my case is 172.18.0.7. This is not the device IP, but the IP of the balena/open-balena-registry Docker container as per the below:
# docker exec openbalena_registry_1_7b865c92e558 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
254: eth0@if255: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:12:00:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.18.0.7/16 brd 172.18.255.255 scope global eth0
valid_lft forever preferred_lft forever
Do note that local SSH works, remote isn’t and it’s what we’re working on. That means if you need to SSH into devices on your local network you can do so with balena ssh LOCAL_DEVICE_IP.
Do note that local SSH works, remote isn’t and it’s what we’re working on. That means if you need to SSH into devices on your local network you can do so with balena ssh LOCAL_DEVICE_IP.
