OS: 2.58.6+rev1
Supervisor: v11.14.0
open-balena-vpn: v9.16.1
open-balena-api: v0.109.2
open-balena-registry:v2.13.11
open-balena-db: v4.1.0
open-balena-s3:v2.9.9
I am having some trouble getting into my production devices using balena tunnel.
- I created a tunnel using:
balena tunnel <uuid> -p 22222:22222
It opens a tunnel correctly:
[Info] Opening a tunnel to ae2f4a8fbbf060e6d4f48589edc0cebe...
[Info] - tunnelling localhost:22222 to ae2f4a8fbbf060e6d4f48589edc0cebe:22222
[Info] Waiting for connections...
- Tried connecting to the tunnel using:
ssh -p 22222 -i id_rsa root@localhost
but it results in:
[Error] 127.0.0.1:51478 => 127.0.0.1:22222 ===> 100.64.0.3:22222 :: Unable to connect: 503 Service Unavailable
I checked if port 3128 is forwarded on the open-balena-server. It is. There is also nothing wrong with the id_rsa (key) because ssh’ing straight to the production device using ssh -p 22222 -i id_rsa root@<my-local-ip-to-device>
does indeed work. The IP: 100.64.0.3 is unknown to me though as my open-balena-server has a different IP. Is that the problem?
This method used to work before I moved my vm from firebase to azure and before I updated to latest hostOS versions. I suspect there is some configuration missing in the open-balena-server. No alarming logs on docker logs
on the open-balena-vpn-container though. Also no logs on the supervisor on the device itself.
Anything obivious I am missing here?