with the release party yesterday (great stuff!) I wanted to try ApolloX.
After installing the extension I was able to connect but got strange error messages. I then reinstalled Torizon on the module and now I can no longer connect. The error message doesn’t say much:
[04-20 10:56:31.137] Trying to connect to 192.168.37.124
[04-20 10:56:41.089] ERROR :: Error trying to connect to apalis-imx8-06494488.local : undefined
If I enter the wrong username or password, I get a different error message.
Connecting to the device with the + symbol and entering IP address doesn’t work either.
But inside WSL I can connect via ssh:
user@Lenovo:~$ ssh torizon@apalis-imx8-06494488.local
torizon@apalis-imx8-0xxxxx8.local's password:
Last login: Sat Mar 18 18:01:38 2023 from 192.168.37.188
torizon@apalis-imx8-0xxxx8:~$
I’ve got the warning about changed host/fingerprint the first time I connected as expected.
I assume it has something to do with the fingerprint/changed host?
After installing the extension I was able to connect but got strange error messages.
Can you describe what exactly were those error messages?
I just talked with the extension team and if you reinstalled TorizonCore on the SoM you have to remove the device in the extension then connect it again.
Just go to your device in the Connected Devices menu then select Remove Device, then try to connect it as you did for the first time.
you can try “CTRL SHIFT P” in VS Code and enter “Logs” which should bring up “Developer: Show Logs”. Select this entry and then select either Extension Host or Extension Host (Remote) - it depends on where the ApolloX extension is installed. This should bring up a more detailed log regarding extensions.
Did you change the default password (being torizon) after you reinstalled TorizonCore? I was able to reproduce your issue after reinstalling TorizonCore on a SoM then trying to connect to it with the default password.
Usually when logging in for the first time as user torizon on a new TorizonCore installation the user is immediately prompted to change the password. This may not be very well handled by V2.0 of the extension, which in turn could be the cause of the problem.
If you haven’t changed the default password on the module, try doing that through serial/SSH then see if you can connect the device on the extension. I’ll report this behavior to the extension team.
As a side note, we recently discovered that the same error also happens on the IDE extension V2 if the user password has a combination of certain special characters like $, #, &, etc.
The extension team is aware of the problem and a solution is being discussed. In the meantime, using a password without the special characters is a possible workaround.
)