ROS v7 Beta 5 - Web GUI?

RouterOS RouterOS beta
1

I just want to confirm some behavior on my RB760iGS for V7 Beta. I’m able to log into the Web GUI exactly one time after booting and it seems to work correctly. After I log out I’m no longer able to connect and the browser reports ERR_CONNECTION_REFUSED, unless I reboot the router, then I can log in again successfully for a single time. Is this expected behavior for the V7 Beta at this time?

Accessing the CLI via SSH still works perfectly fine, as usual. I really appreciate the MikroTik developers hard work on this version and I’m really looking forward to final release of this one :slight_smile:

2

I checked with CHR and it doesn’t happen there. Only when I click logout button, I’m returned to login page and it shows red “ERROR: Internal Server Error” under form. But it still works and I can login back right from there, or it I open the page again in same or different browser.

3

Did a little more digging on this (Wireshark) and found that my client is sending TCP SYN packets to the RB760iGS LAN IP TCP 443 properly and the router is only repeatedly replying with RST, ACK and is not completing three-way handshake. I can reboot the router and confirm that the first web GUI login works; if I log out it begins the RST, ACK response problem and will not complete three-way handshake to my client unless I reboot the router.

Sequence looks like this:

CLIENT TCP SYN → ROUTERBOARD TCP 443
ROUTERBOARD TCP 443 RST, ACK → CLIENT
CLIENT TCP SYN → ROUTERBOARD TCP 443
ROUTERBOARD TCP 443 RST, ACK → CLIENT
…ad infinitum

SSH access still works fine, as does WinBox. This problem only exists with web GUI.

4

Small update to this problem. I’ve found that I can get the Web GUI to start working again if I SSH into the router CLI and disable/enable the www-ssl service via:

/ip/service/disable www-ssl
/ip/service/enable www-ssl

This will let me log back into the router via TLS/SSL, and it works - until I log out again. It seems that logging out of the GUI is somehow crashing the http daemon on the router and that a disable/enable cycle restarts the daemon and makes it work until I log out again.

This does not happen when I login to the GUI using the normal non-encrypted (www service) port 80 connection. It only crashes when I log in via 443/TLS using a certificate that was created/self-signed by the router itself, and, when it does crash, it takes the entire web server down with it. I.E. I can’t log in over port 80 any longer either unless I manually disable the www-ssl service as noted above.

Hopefully this gives MikroTik enough information to figure out what’s going on since I have no way to view the daemon logs on the router myself..