After all that, your RemoteWinBox SSTP connection should establish! If you really, really want to stay on RouterOS v7.6… We’ve seen connect-to, username and password get corrupted in the SSTP client config during reboots on RouterOS v7.6. Next step is to drag and drop, or upload that file to your router and run the command /system package downgradeĪfter that, log back into the router, and run the command /system routerboard upgrade followed by /system reboot in order to get your boot firmware to match the package version.Īfter that, if your connection is not up, remove the RemoteWinBox SSTP client, and copy paste that part of your router’s RemoteWinBox config. If you’re not sure about your router’s CPU architecture, run the command /system resource print and look for the property called cpu. In my case, I’m using a MikroTik hAP ac^2, and it has an ARM CPU, so I will download version 7.5 for ARM routers. To do that, you have to determine what CPU architecture your routerboard is running, and find the appropriate package at There are two ways to solve this problem. If you take a look at the packages and boot firmware, you can see that it’s at version 7.6: The Solution While we can’t write our custom RouterOS patches, we can provide some workarounds!Īs you can see, the RemoteWinBox configuration is on the router, the router can definitely resolve the address, that my router resides on, yet the SSTP connection fails due to not being able to resolve the name of. It seems like the latest MikroTik update broke something related to SSTP Client interface.

After spending some time investigating this issue in our lab, we came to a conclusion that the problem happens specifically with routers that are on RouterOS 7.6. Almost all of them were related to routers not establishing an SSTP connection to a RemoteWinBox server. In the past week or so, we have received higher than usual number of support emails.

Router os 7