SSH to opnsense fails after upgrade to 26.7.2_2

Started by revr3nd, August 19, 2026, 03:50:15 PM

Previous topic - Next topic
Quote from: franco on August 19, 2026, 07:35:10 PMWell, given the release log only this sticks out:

* ssh(1), sshd(8): make the transport protocol stricter by
  disconnecting if the peer sends non-KEX messages during a post-
  authentication key re-exchange...

It's not even passing initial authentication, though - so doesn't get anywhere near key re-exchange...(?)


Quote from: dseven on August 19, 2026, 07:50:38 PMRegardless of key type, if password authentication is enabled, there should be a password prompt if the publickey method fails, so there's something else not right here.

OP, when this worked prior to the upgrade, were you prompted for a password, or did you get straight in with the key?

Check System -> Log Files -> Audit for clues (maybe change level to "Informational")

Only items in the audit logs are just starting and stopping of the process. Does not appear to generate any logs of connection attempts


2026-08-19T10:37:57-07:00InformationalsshdServer listening on 127.0.0.1 port 22.
2026-08-19T10:37:57-07:00InformationalsshdServer listening on fe80::1%lo0 port 22.
2026-08-19T10:37:57-07:00InformationalsshdServer listening on fe80::227c:14ff:fef4:381d%vlan0.10 port 22.
2026-08-19T10:37:57-07:00InformationalsshdServer listening on 192.168.11.1 port 22.
2026-08-19T10:37:57-07:00InformationalsshdServer listening on fe80::227c:14ff:fef4:381d%vlan0.11 port 22.
2026-08-19T10:37:57-07:00InformationalsshdServer listening on fd00:0:0:11::1 port 22.
2026-08-19T10:37:56-07:00InformationalsshdReceived signal 15; terminating.




Regarding rollback of the process itself, I will need to go on site to console into the device. This will take some time :/

Are you sure you're actually ssh'ing to the opnsense box? Maybe you have destination NAT for port 22 or something???