spektor56
Will not connect to Comma 3X
i can see in the log its scanning the correct IP range but the message box is blocking more of the log. Did you try 1.9.7 release with the discovery update? running a fork on 0.10.0 or later?
I'm seeing the exact same situation. WSL2 and Windows' built-in SSH clients work fine:
It seems to connect, but it keeps saying it couldn't find a device. I generated a key on OpenpilotToolkit itself by logging in into my Github account, and it got added just fine:
OpenpilotToolkit is not very clear about the key being used, but the Comma device is correctly setup to allow connections from the key added by it:
comma@comma-{deviceid}:/data/persist$ grep AuthorizedKeysFile /etc/ssh/sshd_config
AuthorizedKeysFile /data/params/d/GithubSshKeys
comma@comma-{deviceid}:/data/persist$ ssh-keygen -lf /data/params/d/GithubSshKeys -E sha256
256 SHA256:5zzEQzk2u08XJtOjGNwy8mVw3dQG/EGT8clIA43D0F4 no comment (ED25519)
256 SHA256:ug4I62ldamnXi9V+kkL5YhnveFyRn1lqvix+3ydzpQM no comment (ED25519)
256 SHA256:RFSlPmisFlA0J4fK0J7C1WIScD/JcYea501Yn9+X3To no comment (ED25519)
OpenpilotToolkit logs read a bit weird tho:
2025-10-07 12:21:40.097 -06:00 [INF] Connected to 192.168.50.63 on port 22
2025-10-07 12:21:50.943 -06:00 [ERR] Discovery Timed Out.
Interestingly, a bit later it says its connected:
2025-10-07 12:21:40.097 -06:00 [INF] Connected to 192.168.50.63 on port 22
2025-10-07 12:21:50.943 -06:00 [ERR] Discovery Timed Out.
2025-10-07 12:22:10.601 -06:00 [INF] Connected to Comma3 device at 192.168.50.63 on port 22
Seems it timesout before it recognizes the connection has been established?
Logs on the comma show that seems to be the case. Here are logs before running OpenpilotToolkit:
comma@comma-{deviceid}:/data/persist$ sudo netstat -tnpa | grep ssh
tcp 0 0 0.0.0.0:8022 0.0.0.0:* LISTEN 48840/sshd: /usr/sb
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 48840/sshd: /usr/sb
tcp 0 0 192.168.50.63:22 192.168.50.211:56698 ESTABLISHED 56983/sshd: comma [
tcp 0 0 192.168.50.63:22 192.168.50.211:55718 ESTABLISHED 57745/sshd: comma [
tcp6 0 0 :::8022 :::* LISTEN 48840/sshd: /usr/sb
tcp6 0 0 :::22 :::* LISTEN 48840/sshd: /usr/sb
... and then after, when OpenpilotToolkit says it couldn't connect:
comma@comma-{deviceid}:/data/persist$ sudo netstat -tnpa | grep ssh
tcp 0 0 0.0.0.0:8022 0.0.0.0:* LISTEN 48840/sshd: /usr/sb
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 48840/sshd: /usr/sb
tcp 0 0 192.168.50.63:22 192.168.50.211:56698 ESTABLISHED 56983/sshd: comma [
tcp 0 0 192.168.50.63:22 192.168.50.211:50310 ESTABLISHED 61462/sshd: comma [
tcp 0 0 192.168.50.63:22 192.168.50.211:55718 ESTABLISHED 57745/sshd: comma [
tcp6 0 0 :::8022 :::* LISTEN 48840/sshd: /usr/sb
tcp6 0 0 :::22 :::* LISTEN 48840/sshd: /usr/sb
ps tells a similar story:
comma@comma-{deviceid}:/data/persist$ ps -ef | grep sshd
root 48840 1 0 11:13 ? 00:00:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root 56983 48840 0 12:10 ? 00:00:00 sshd: comma [priv]
comma 56997 56983 0 12:10 ? 00:00:00 sshd: comma@pts/2
root 57745 48840 0 12:15 ? 00:00:00 sshd: comma [priv]
comma 57758 57745 0 12:15 ? 00:00:00 sshd: comma@pts/3
comma 61819 57759 0 12:43 pts/3 00:00:00 grep --color=auto sshd
comma@comma-{deviceid}:/data/persist$ ps -ef | grep sshd
root 48840 1 0 11:13 ? 00:00:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root 56983 48840 0 12:10 ? 00:00:00 sshd: comma [priv]
comma 56997 56983 0 12:10 ? 00:00:00 sshd: comma@pts/2
root 57745 48840 0 12:15 ? 00:00:00 sshd: comma [priv]
comma 57758 57745 0 12:15 ? 00:00:00 sshd: comma@pts/3
root 61462 48840 0 12:41 ? 00:00:00 sshd: comma [priv]
comma 61475 61462 0 12:41 ? 00:00:00 sshd: comma@notty
root 61524 48840 0 12:41 ? 00:00:00 sshd: comma [priv]
comma 61537 61524 0 12:41 ? 00:00:00 sshd: comma@notty
comma 61757 57759 0 12:42 pts/3 00:00:00 grep --color=auto sshd
