WinBox "router does not support secure connection, please enable Legacy Mode": fix (WinBox 3 and 4)

WinBox shows "router does not support secure connection" when it can't do the modern login handshake with your MikroTik. In WinBox 3, turn on Tools > Legacy Mode. If that hangs, the real cause is usually an old RouterOS, NAT or a custom port, or a stuck router. Fixes for WinBox 3 and WinBox 4.

Share
WinBox error router does not support secure connection, please enable Legacy Mode

ERROR: router does not support secure connection, please enable Legacy Mode if you want to connect anyway means WinBox couldn't complete its secure login handshake with the MikroTik router. The quick fix in WinBox 3 is Tools > Legacy Mode: turn it on and connect again.

That works when the router runs old RouterOS (before 6.43). On a modern router, the same error usually points to something else: a connection through NAT or a port forward, a non-default WinBox port, a stale WinBox session, or a router that needs a reboot. Legacy Mode then just hangs at "Logging in". Both cases are below, plus what changes with WinBox 4, which has no Legacy Mode at all.

WinBox error router does not support secure connection

Fix 1: enable Legacy Mode in WinBox 3

  1. Open WinBox 3 (get the latest 3.x from the MikroTik download page).
  2. In the top menu, click Tools.
  3. Check Legacy Mode.
  4. Connect to the router again.
MikroTik WinBox Tools menu with Legacy Mode enabled

Legacy Mode switches WinBox to the old login method. Newer WinBox 3 builds use a stronger handshake that RouterOS supports from v6.43, and older routers don't understand it.

Logged in to a MikroTik router in WinBox

Once you're in, check the RouterOS version under System > Resources. If it's older than 6.43, upgrade RouterOS (and the RouterBOARD firmware under System > RouterBOARD > Upgrade). After that you can turn Legacy Mode off again. Old RouterOS has known security holes, so don't leave a router on it.

Fix 2: the router is modern and Legacy Mode hangs

If the router already runs RouterOS 6.43+ or 7.x, the secure login should work. When it doesn't, check these in order:

  • NAT, port forward or tunnel. Connecting through a port forward, an SSH tunnel or a NAT'ed path breaks the secure handshake for some setups. Connect directly to the router's LAN IP, or over a VPN that routes to it, instead of a forwarded port.
  • Custom WinBox port. If you changed the WinBox service port, enter it as IP:port (for example 192.168.88.1:8299) and make sure the firewall allows it. Check under IP > Services.
  • Firewall on the router. Allow the WinBox port (default TCP 8291) in the input chain from your management network.
  • Stale session data. Old saved sessions in WinBox can cause failed logins. Remove the router from the saved list, or start WinBox with a clean session (Session > New in WinBox 3), and connect again.
  • Router stuck. If WebFig doesn't respond either, the router itself is the problem. A reboot often clears it.

If you can still reach the router by MAC address in the Neighbors tab, use that to get in and fix the IP, firewall or service settings.

WinBox 4: there is no Legacy Mode

WinBox 4 is MikroTik's native app for Windows, macOS and Linux and replaces WinBox 3. According to the MikroTik WinBox manual, it uses ECSRP for key exchange and authentication and AES128-CBC-SHA for encryption. There's no Legacy Mode setting, so it can't fall back to the old login.

What that means in practice:

  • For old routers (RouterOS before 6.43), use WinBox 3 with Legacy Mode, or upgrade RouterOS first.
  • For new routers, WinBox 4 is becoming mandatory. On the MikroTik forum, users note that WinBox 3 is no longer supported from RouterOS 7.25 and that WinBox older than 4.3 won't connect.

So keep both installed if you manage a mix of old and new devices: WinBox 4 for current RouterOS, WinBox 3.43 for the old ones.

Other ways in when WinBox won't connect

  • WebFig: open http://router-ip in a browser.
  • SSH: ssh admin@router-ip. Through a bastion host, see how to use an SSH jump host.
  • MAC-Telnet or MAC WinBox from the same network segment, if IP access is broken.

Before you change anything big, export the config so you can roll back. I covered that in backing up a MikroTik configuration in plain text.

My take

Treat Legacy Mode as a way to get in once, not as a setting to keep. If a router needs it, that router is running RouterOS older than 6.43, and the real fix is an upgrade. If a modern router asks for it, Legacy Mode won't help: look at how you're connecting (NAT, port, firewall) or just reboot it.

FAQ

What does "router does not support secure connection, please enable Legacy Mode" mean?

WinBox couldn't complete the secure login handshake. Usually the router runs RouterOS older than 6.43, or the connection goes through NAT, a custom port or a firewall that breaks the handshake.

Where is Legacy Mode in WinBox?

In WinBox 3, open the Tools menu and check Legacy Mode. WinBox 4 has no Legacy Mode.

Legacy Mode is on but WinBox hangs at "Logging in". What now?

The router is probably modern and the problem is the connection. Connect to the LAN IP directly instead of a port forward, check the WinBox port under IP > Services and the input firewall, clear the saved session, or reboot the router.

Does WinBox 4 have Legacy Mode?

No. For routers on RouterOS older than 6.43, use WinBox 3 with Legacy Mode or upgrade RouterOS.

Is Legacy Mode safe?

It uses the old, weaker login method. Use it only to reach an old router and upgrade it, then switch it off.