Issues connecting to admin page of RT-AC5300

[neanderthal]

Firmware 380.69, Chrome Version 65.0.3325.162 on Win 10 (issue reproducible on Android and iPad).

I have major problems connecting to the admin page; the login prompt appears, I log in and get a half-rendered page:

The Chrome dev console reveals a lot of files failed to load:

If I click on a link (Operation Mode, Firmware or SSID) I either get thrown back to the login prompt or ERR_CONNECTION_REFUSED.
Router is assigned a fixed ip at 192.168.1.1.
At first I assumed it was some sort of firewall/AV issue but I've disabled everything to no avail.
I then tried to connect using my (Android) smartphone which runs Opera and via Safari on my iPad and i get exactly the same behaviour.
As my admin access is next to non-existent I can't change the firmware (or any other settings) and can only think of carrying out a full reset, unless anyone can suggest a resolution?

 

[skeal]

Firmware 380.69, Chrome Version 65.0.3325.162 on Win 10 (issue reproducible on Android and iPad).

I have major problems connecting to the admin page; the login prompt appears, I log in and get a half-rendered page:
View attachment 12332

The Chrome dev console reveals a lot of files failed to load:
View attachment 12333

If I click on a link (Operation Mode, Firmware or SSID) I either get thrown back to the login prompt or ERR_CONNECTION_REFUSED.
Router is assigned a fixed ip at 192.168.1.1.
At first I assumed it was some sort of firewall/AV issue but I've disabled everything to no avail.
I then tried to connect using my (Android) smartphone which runs Opera and via Safari on my iPad and i get exactly the same behaviour.
As my admin access is next to non-existent I can't change the firmware (or any other settings) and can only think of carrying out a full reset, unless anyone can suggest a resolution?View attachment 12332 View attachment 12333

Try shift-f5 when logging in and when the first page fails to load correctly.

 

[john9527]

I know that's what you will get if you try and log in via https without installing the certificate authority (hitting Proceed anyway in Chrome). If that's the case, install the certificate when you get the invalid cert screen.

 

[neanderthal]

I know that's what you will get if you try and log in via https without installing the certificate authority (hitting Proceed anyway in Chrome). If that's the case, install the certificate when you get the invalid cert screen.

This is a normal (non-https) connection - and the issue is across multiple browsers and devices.

 

[neanderthal]

Try shift-f5 when logging in and when the first page fails to load correctly.

Thanks but I tried it before (and in response to your suggestion) but a forced reload makes no difference.

 

[Rumline]

I have an even worse problem: the admin web page refuses to draw at all on https://192.168.1.1:8443. RT-AC5300. Just upgraded to asuswrt-merlin 384.4 (Release). Performed a factory reset with JFFS format. Manually reconfigured everything. Created a self-signed certificate and imported it into Windows Trusted certs:
Issued to : 192.168.1.1
SAN : 192.168.1.1 router.asus.com RT-AC5300-54A0
Issued by : 192.168.1.1
Expires on : 2028/3/17

NMAP shows the device answering on the port.
nmap -p 8443 192.168.1.1
Starting Nmap 7.60 ( https://nmap.org ) at 2018-03-16 19:06 Mountain Daylight Time
Nmap scan report for 192.168.1.1
Host is up (0.00s latency).
PORT STATE SERVICE
8443/tcp open https-alt
MAC Address: D0:17:C2:3B:54:A0 (Asustek Computer)
Nmap done: 1 IP address (1 host up) scanned in 6.89 seconds

Firefox Quantum 59.0.1 (64-bit). Works fine with Microsoft Edge (64-bit) 41.16299.248.0 and Google Chrome 65.0.3325.162 (Official Build) (64-bit). Why does the httpd process not respond to Firefox on https 8443?

 

[john9527]

This is a normal (non-https) connection - and the issue is across multiple browsers and devices.

Check the address bar and make sure it says http and not https. Recent browser releases will automatically convert http requests to https. Drove me crazy for a while as once I connected via https, I could not longer connect via http. If this is the case, clear your browser cache.

 

[Rumline]

No dice. Web server is set to both protocols:

https://192.168.1.1:8443 just gives "The connection has timed out" or "The server at 192.168.1.1 is taking too long to respond." I can connect via http://192.168.1.1 (that's how I got the screenshot). While I can admin the device via unencrypted port 80, I would prefer not to. I would like to have all admin traffic encrypted In addition, https access over port 8443 used to work before the upgrade to version 384.4. I used to be on version 384.4_beta2 and it worked. I did try clearing the Firefox cache completely to no avail. I even tried moving the AICloud Disk port from 443 to 7443, then assigning the admin website from 8443 to 443. Doesn't work with Firefox.

My end user concern is two-fold:
1. It used to work on 384.4_beta2.
2. I would like all admin traffic/commands to be in an encrypted transport.

 

[kvic]

@neanderthal @Rumline

I may not be addressing your immediate issues. I'm offering you a solution that does solve your problem, and never have to face with invalid cert prompts and importing certs after every FW upgrade.

This solution is a free ride for pixelserv-tls users. If people haven't heard of it, then the fastest way to get start using it on this forum is through AB-Solution. Both combined is a superb DNS based adblock solution btw.

Once you're a pixelserv-tls user, then to address your invalid cert issue in FF is like eating a piece of cake by following my post:

https://www.snbforums.com/threads/firefox-https-connection.44787/page-2#post-389381

Also, worth pointing out is that immediately below my post, a forum member suggested another trick which seems to work for him (since I don't have the issue to begin with, I could not confirm if it works or not).

 

[Treadler]

I have an even worse problem: the admin web page refuses to draw at all on https://192.168.1.1:8443. RT-AC5300. Just upgraded to asuswrt-merlin 384.4 (Release). Performed a factory reset with JFFS format. Manually reconfigured everything. Created a self-signed certificate and imported it into Windows Trusted certs:
Issued to : 192.168.1.1
SAN : 192.168.1.1 router.asus.com RT-AC5300-54A0
Issued by : 192.168.1.1
Expires on : 2028/3/17

NMAP shows the device answering on the port.
nmap -p 8443 192.168.1.1
Starting Nmap 7.60 ( https://nmap.org ) at 2018-03-16 19:06 Mountain Daylight Time
Nmap scan report for 192.168.1.1
Host is up (0.00s latency).
PORT STATE SERVICE
8443/tcp open https-alt
MAC Address: D0:17:C2:3B:54:A0 (Asustek Computer)
Nmap done: 1 IP address (1 host up) scanned in 6.89 seconds

Firefox Quantum 59.0.1 (64-bit). Works fine with Microsoft Edge (64-bit) 41.16299.248.0 and Google Chrome 65.0.3325.162 (Official Build) (64-bit). Why does the httpd process not respond to Firefox on https 8443?

Try setting Firefox to ‘default’, then when prompted add an exception for the certificate & all should work.
(At least, it did for me.......)

 

[john9527]

Try going to the certificate management under your browser, and delete all the ASUSWRT-Merlin certs under certificate authorities. Then re-import the certificate.

 

[neanderthal]

Thanks for all the suggestions, but I was just want to point out that my issue is not ssl related, I am not connecting via https, and the issue is reproducible across different browsers from Chrome to Edge to Safari and Opera.

 

[Tagilso]

Getting the same half-rendered page error only with Chrome on Android after 384 update.

 

[Tagilso]

Getting the same half-rendered page error only with Chrome on Android after 384 update.

My issue happens on AC-68U, here is the screenshot from Chrome Android dev console.