SSH standalone access Issue

Product support
1

Hi,

I am having an issue, was trying to add standalone SSH access capabilities to my device. Provisioned the ssh keys on the config,json file and can confirm that my ssh key is available on the host OS on the .ssh/authorised_keys and the .ssh/authorised_keys_local files.

Has you can confirm by the image below.

image
image1558×580 142 KB

Nonetheless my SSH standalone access is not working, both:.

ssh -p 22222 root@3.xxx.xxx.60

and

balena device ssh 3.xxx.xxx.60

The keys i have on the device are the same I have on the platform so I am able to use the usual:

balena device SSH <device_UUID>

I have rebooted and done other troubleshooting, but not sure what’s wrong.
Can you give me a hand, I can open the machine for support access.

Best

2

Hi Again,

I activated support access just in case you would like to llok around before giving me an answer.

image
image478×122 4.25 KB

Thanks

3

Hi @suporte what version of balenaOS and device type are you trying this on? Additionally, could you perhaps share a copy of what your edited config.json file looks like, making sure to redact private info like device API key, etc.

4

Hi Shaun,

Looking further into the issue seems like the problem might be the CGNAT on our 4G provider, which doesn’t allow us to reach the device through SSH.

We are studying other ways to obtain SSH access of the container.

Thanks for the quick intervention.
and Sorry for the inconvenience.

Best!

5

No problem at all. I hope you find a way forward!