v7.19 ssh login stucks with F1 for help

RouterOS General
1

Hi,

after upgrading to v7.19 I cannot ssh login as before on my RB3011UiAS even the router seems fully operational otherwise.

Login stucks at Press F1 for help and no input is accepted nor shown.

  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 7.19 (c) 1999-2025       https://www.mikrotik.com/


Press F1 for help

Any suggestions?

2

this doesn’t happen on hapac2 and RB5009 just fyi

3

Hey

bit low on details / context

changelog does mention some changes: https://mikrotik.com/download/changelogs

4

thanks a lot for answering

About the context

  • usually, from time to time, connect to the remote router via wireguard vpn
  • looking for log file, new versions available...
  • aware that a new version is available, so I could upgrade from 7.18.2 (I think) to 7.19, great, normal procedure for years, never checked the change log. :frowning:
  • /system/package/update/download
  • /system/package/update/install...
  • waiting for coming back for about two minutes, not switched off the wireguard client
  • no connection, vpn off and on again, no connection, returned after 10 minutes..., established wireguard tunnel
  • just started to check whether the devices behind the router could be connected, success.
  • ssh to the router, see above,
  • checked whether scp file download from router works (with a known filename), success.
  • no other actions performed up to now, ssh is the only once allowed by firewall (via wireguard), cannot access device in data center directly
  • no chance to see how healthy the router is

About the changelog: not quite sure which entry would give a hint regarding the observed behaviour

\

5

any other out-of-band methods available? serial?
have you tried rebooting again (via dc methods)?

looks like some troubleshooting / post-mortem will be needed, as 7.19 had quite some changes, including for ssh

6

ROUTER is alive again ! - friend of mine was able to reboot the router with via web ui, without wireguard.
Unfortunatly we did not implement rsyslog remote log, router log is memory based only, so no helpful entries.

Guess:
I think, that I logged in via ssh while the router was not fully functional/up. Observed odd behaviour also on some of my linux devices, when tried to ssh login in the middle of reboot, got something of a shell which looked weird.


Thanks all for helping, leave with the feeling that there are some secrets in the mt devices

Regards