Unable to login to webUI of RT-AX86U on Chrome

[Qrucz]

Hi,
I'm not able to log in to the WebUI of my AX86U from Chrome on Win10 since I've updated the router to 386.7.2
Chrome says that webpage is unavailable (Connection refused)
Interestingly enough I can login if I use Edge on the same machine, or if I use Chrome on my Android tablet and phone.
I've upgraded to 388.1.0 now, but the issue remained

 

[Tech9]

No issues here, Chrome:

Flush browser's cache, reload with Ctrl + F5. You have a local issue.

 

[Qrucz]

No issues here, Chrome:

View attachment 45977

View attachment 45978

Flush browser's cache, reload with Ctrl + F5. You have a local issue.

It is still not working after flushing cache

 

[Tech9]

Use http://www.asusrouter.com instead. The old http://router.asus.com works too.

The default LAN IP for this router is 192.168.50.1 and I don't know if you have it changed or not.

 

[RMerlin]

The old http://router.asus.com works too.

This GPL didn't migrate to the new domain name yet, Asus only implemented it in a later version.

If the exact message is Connection Refused, then probably the IP is correct, however either the port is not correct (if using https, don't forget to also use the port you configured, typically 8443), the non-http access was disabled, or the web service is stopped/crashed (it should normally get restarted by the watchdog, but it does not always happen if it's just stuck rather than stopped).

 

[Qrucz]

This GPL didn't migrate to the new domain name yet, Asus only implemented it in a later version.

If the exact message is Connection Refused, then probably the IP is correct, however either the port is not correct (if using https, don't forget to also use the port you configured, typically 8443), the non-http access was disabled, or the web service is stopped/crashed (it should normally get restarted by the watchdog, but it does not always happen if it's just stuck rather than stopped).

You were right, thank you.
It works both with asusrouter.com and with http://192.168.1.1 IP was correct, but somehow Chrome tries to access it with https and then it denies. How can I check the https port? I tried 8443 but it was not working with that

 

[Tech9]

This GPL didn't migrate to the new domain name yet, Asus only implemented it in a later version.

The new domain http://www.asusrouter.com/ works on my older AC86U router on 386.5_2 firmware.

How can I check the https port?

You don't need https enabled for your LAN access to GUI. If you have WAN access to GUI enabled - disable that and use VPN instead.

 

[RMerlin]

The new domain http://www.asusrouter.com/ works on my older AC86U router on 386.5_2 firmware.

It might cause other browser issues because the certificate doesn't have that SAN yet - that was only added recently by Asus.

 

[Tech9]

Noticed it works on AC86U few days back when switching routers and typing "as" only in address bar. My intention was to visit your https://www.asuswrt-merlin.net/, but the browser send me to http://www.asusrouter.com/ instead and got the GUI login screen. It wasn't just browser's cache because I changed the router's LAN IP to something random 192.168.x.x and I still got the GUI login page on both http://www.asusrouter.com/ and http://router.asus.com/.

See this:

 

[RMerlin]

These are the hosts that are currently present in the hosts file (and would therefore at least work from a name resolution point of view):

192.168.10.1 router.asus.com
192.168.10.1 www.asusnetwork.net
192.168.10.1 www.asusrouter.com

With Asus' recent changes, they now support a much longer list of FQDNs, which I assume will be device-specific (or might be reserved for future use). These are the SANs that will next be used when generating a self-signed cert:

merlin@ubuntu-dev:~/asuswrt.386-50757-ac86/release/src/router/rom$ more rom/etc/openssl.cnf | grep DNS.
DNS.1 = router.asus.com
DNS.2 = www.asusrouter.com
DNS.3 = repeater.asus.com
DNS.4 = www.asusrepeater.com
DNS.5 = ap.asus.com
DNS.6 = www.asusap.com
DNS.7 = asusrouter.com
DNS.8 = asusrepeater.com
DNS.9 = asusap.com
DNS.10 = www.asusswitch.com
DNS.11 = asusswitch.com
DNS.12 = www.asusnetwork.net
DNS.13 = asusswitch.net
DNS.14 = asusrepeater.net
DNS.15 = asusap.net
DNS.16 = zenwifi.net
DNS.17 = expertwifi.net

 

[Tech9]

Interesting.

 

[RMerlin]

Interesting.

Yes, that one already works because it's been included in the router hosts file for years. It won't work properly on older stock firmware however because stock firmware automatically redirected you to router.asus.com, which would then run into the HSTS validation issue that were discussed.

It will mostly work on my firmware provided you don't try to access it over https and you don't have a pedantic browser (because that domain is not included in the certificate SANs yet).