I encountered a bug when trying login to webfig using ssl, when access the rounter with a DNS hostname (as opposed to IP).
I only found one previous reference to such error, but no follow-up or resolution: viewtopic.php?t=154444#p764586
--
details:
Using CRS125-24G-1S-2HnD with RouterOS v6.48.2(stable),
Using "Google Chrome" version 90.0.4430.72 on Debian Linux amd64.
When accessing webfig using HTTP and IP address (e.g. http://192.168.88.1) - works.
When accessing webfig using HTTPS and IP address (e.g. https://192.168.88.1) - works, and as expected, chrome displays a "PRIVACY ERROR" warning that the certificate does not match (NET::ERR_CERT_COMMON_NAME_INVALID ).
But,
when accessing webfig using HTTPS and hostname (e.g. https://router.mydomain.com , pointing to the same IP as above) - login fails with a generic red error message "ERROR: not found".
Looking at the google-chrome dev console, the following error appears after clicking the "login" button:
-------
Code: Select all
master-min-79a26da00efe.js:798 GET https://router.mydomain.com/webfig/roteros-5e5cc36ce70b.jg 404 (Not Found)
request @ master-min-79a26da00efe.js:798
loadGUM @ master-min-79a26da00efe.js:1267
(anonymous) @ master-min-79a26da00efe.js:1271
req.onreadystatechange @ master-min-79a26da00efe.js:796
XMLHttpRequest.send (async)
request @ master-min-79a26da00efe.js:798
initWebfig @ master-min-79a26da00efe.js:1268
load (async)
(anonymous) @ master-min-79a26da00efe.js:1290
As noted in the other forum message (linked above), trying the same ( https://router.mydomain.com ) DOES WORK from firefox.
So this looks like some strange edge-case of incompatibilities.
Happy to try more things if you have suggestions.
Regards,
- gordon