I am sorry for the silly questions lately.
The following used to work for me to SSH into production devices (based on this topic):
- Use balena tunnel to forward the ‘ssh port’:
balena tunnel <uuid> -p 22222:22222
Fetching device by UUID fc0 (string)
[Info] Opening a tunnel to fc09dd5bcbcf6e81cda084c5e6f98ff0…
[Info] - tunnelling localhost:22222 to fc09dd5bcbcf6e81cda084c5e6f98ff0:22222
[Info] Waiting for connections…
- Use putty (or linux SSH) to the forwarded port using
127.0.0.1:60196 => 127.0.0.1:22222 ===> 10.240.0.11:22222
So the forwarding seems to work. I also ‘reach’ the device but there is something wrong with my public-key.
Putty shows this error:
Using WSL I get some more information:
I don’t really understand the problem. Before I could connect to my devices just fine. I even removed my devices and flashed them again. They are listed in my
balena devices command. I can ping the devices inside my network and get responses. Also; ssh’ing to my development-devices does work. But I guess that’s because the security is lacking in that imagefor development purposes. You can connect as root without a password.
Maybe it is worth mentioning (as I think it is correlated): deploying an app to my devices using
balena deploy <name> --logs --source . --emulated works. I see the images are being pushed to the registry and get the unicorn message etc. But those devices don’t actually start the application. My guess is that the application is not pushed correctly to those devices maybe due to the same error? My OpenBalena probably gets the same publickey error while pushing to those devices. I don’t know how to verify that though.
Hardware: RaspberryPi 4
Balena CLI: 11.36.0 (both linux and windows)