We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

Can't connect neither by serial nor ssh (exp dock)

  • HI guys

    I have been trying to connect my Omega2+ via ssh or serial but I'm unable to do that.
    4_1485694073463_Screen Shot 2017-01-29 at 6.12.11 PM.png 3_1485694073463_Screen Shot 2017-01-29 at 6.12.13 PM.png 2_1485694073463_Screen Shot 2017-01-29 at 6.12.36 PM.png 1_1485694073462_Screen Shot 2017-01-29 at 6.12.50 PM.png 0_1485694073448_Screen Shot 2017-01-29 at 6.13.10 PM.png

    I have included some screenshots you can have a look at them and suggest me what to do

  • It looks like that you are not in the same IP Range with your wifi.
    You have to check with ipconfig that your computer also has a IP Address with 192.168.3.x or activating also wifi on the omega to get an ip address with 192.168.1.x on the omega ... now you are in two different networks and your computer not allows you to connect.

  • Your title mentions serial, but you don't seem to have actually tried that, but only the web interface and ssh.

    The SSH identity warning may in fact be normal, or at least it is frequently encountered with systems that may re-invent their identity when reset, or if you have multiple systems that default to the same address.

  • This happens also when once connecting with Omega-8C69 and the other time with the IP. But his problem seams to be the ip range. The client is in a different range as the Omega. With other words two AP networks (refused to connect).

    @Chris-Stratton , did you see all the picture he posted?

  • Remove the old key in the .ssh/known_hosts file for, that will allow you to ssh without error.

  • @Luciano-S. said in [Can't connect neither by serial nor ssh (exp dock)]

    @Chris-Stratton , did you see all the picture he posted?

    That was exactly my point. None of them show an attempt at using a serial connection.

    In terms of being in the wrong subnet, the ssh warning would not have resulted without connecting to something at a running an SSH service, and while that could be a router, the comparably custom address makes it more likely that it actually was the Omega2.

Looks like your connection to Community was lost, please wait while we try to reconnect.