What's new

Unable to login to webUI of RT-AX86U on Chrome

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Qrucz

Occasional Visitor
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
 
No issues here, Chrome:

1670175138072.png


1670175162918.png


Flush browser's cache, reload with Ctrl + F5. You have a local issue.
 
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).
 
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
 
Last edited:
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):

Code:
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:

Code:
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
 
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).
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top