[RESOLVED] Slooooow UI

[Adrien]

Hi
Is there a reason as to why the UI is so slow to load?
I've tried with safari chrome and firefox.
Firefox is somehow the most responsive.

Even after doing a reboot of the router, its almost impossible to use it and access anything.

Has someone seen this? Is there a way to find out whats going on?
i've sshed into the router and doing top does not show much. CPU is pretty much idle.

thanks
Adrien

 

[Adrien]

Well i think i just found out.
I was limiting myself to only use HTTPS and i disabled HTTP.

I decided to re-enable http mode and use and looks like it was the reason.

Can someone confirm that using the UI over https is slow to almost unusable.

thanks

 

[jrmwvu04]

Yes. It's slow with https. Not only do I know that for myself, there are a number of folks on this board who have claimed as much.

 

[Adrien]

cool.
thanks for the reply and trying it out
I was about to roll back to the original firmware until i decided to try.

I know its kinda of stupid to use https on my local network, but nowadays its better to be safe than sorry.

I guess i'll just use http until its resolved.

Adrien

 

[jrmwvu04]

It's fine to use http, just don't allow access from WAN.

 

[Adamm]

Somewhat of a solution to this issue is adding the cert to your root certificates as mentioned here;

I wanted to mention this few days ago. With Ac87U the Web UI was very fast with HTTP, but very slow with HTTPS protocol. It is really bad in Chrome, I would always hit refresh otherwise the Web UI section I clicked on would never load. Edge browser was a bit better.

After I upgraded from AC87U to AC88U I experienced the exactly same behaviour, the second I turned on HTTPS for the Web UI it started being very slow (the Web UI navigation).

I don't know why but after I added the router certificate to my trusted root certification authority the Web UI was working exactly the same fast as with HTTP protocol. Here is the tutorial how to add a certificate as an exception in Chrome: https://superuser.com/a/632060/172416

 

[Adrien]

thank you @Adamm I will take a look at it.

 

[Josh Schneider]

Somewhat of a solution to this issue is adding the cert to your root certificates as mentioned here;

Thanks for this advice. Seems to have solved the problem for me with 384.6

 

[DonnyJohnny]

i think the reason is due to multiple cert cache. You can delete all the cert under cert management of the browser that is tagged to Wan IP.

You will realise that if u use different browser, you will not have the slow effect.

 

[kvic]

For pixelserv-tls users, there is an easy way out to solve your SLOW GUI and all your HTTPS webgui certificate related issues.

Use pixelserv-tls to generate a certificate for your WebGUI for a good TEN years. Here is the HOWTO:

https://github.com/kvic-z/pixelserv...ixelserv-CA-to-issue-a-certificate-for-WebGUI

I was told a few guys are using this script on a regular basis. Looks like it's still little well kept secret.

 

[jksmurf]

Thanks for this advice. Seems to have solved the problem for me with 384.6

Does this advice still apply? My GUI, especially remote, is very slow.

 

[DJones]

Does this advice still apply? My GUI, especially remote, is very slow.

Unless you’re using an old version of Diversion pixelserv-tls isn’t used anymore unless it’s installed in something else.

However adamms advice might still stick.

 

[jksmurf]

Unless you’re using an old version of Diversion pixelserv-tls isn’t used anymore unless it’s installed in something else.

Nope nothing like that.

However adamms advice might still stick.

Thanks I might try so I don’t have to revert to http.

 

[jksmurf]

Unless you’re using an old version of Diversion pixelserv-tls isn’t used anymore unless it’s installed in something else.

However adamms advice might still stick.

Ok so I’ve exported (what I believe to be) the Let’s Encrypt certificate from the WebGui login page that shows up and installed it as a Trusted Certificate in Chrome Browsers on my desktops and in Safari on two iOS devices.

The http access remains considerably faster than https, which is nigh unusable.

Should I be using a different certificate ie not Let’s Encrypt?

 

[ColinTaylor]

Ok so I’ve exported (what I believe to be) the Let’s Encrypt certificate from the WebGui login page that shows up and installed it as a Trusted Certificate in Chrome Browsers on my desktops and in Safari on two iOS devices.

The http access remains considerably faster than https, which is nigh unusable.

Should I be using a different certificate ie not Let’s Encrypt?

Are you sure you're using a valid certificate and URL? What do you see in the browser?

 

[jksmurf]

Are you sure you're using a valid certificate and URL? What do you see in the browser?

View attachment 60152

I’m pretty confident yes. I don’t use https://www.asusrouter.com:8443 as that resolves to my local router, whereas 192.168.47.1 is my remote router (via a VPN).

But certainly when I changed between http and https on that 47.1 address I got the message about downloading the certificate and installing it to Trusted Certificates, which I have done (for both my routers), for use in Safari in my iPad. For my Chrome browsers on Windows I followed the method in Adamms linked reference.

But when I toggle between http and https access in the Admin the snappiness of the WebGUI is markedly different. Admittedly the remote router is only on a 300/100 connection but I tried both via Wireguard direct and Tailscale (direct not DERP) and I don’t think it’s the VPN that is slowing it down.

I note Colin that you said at some stage you just use http, is that due to speed or just a preference ?

 

[ColinTaylor]

I note Colin that you said at some stage you just use http, is that due to speed or just a preference ?

Just laziness really. I can type "192.168.1.1" rather than having to add the :8443 suffix. I have no security concerns when using plain HTTP. It also means that I can factory reset my router and not bother immediately having to regenerate and install the certificate on all the clients I might use (or put up with the slow GUI until I do so).

 

[DJones]

Just laziness really. I can type "192.168.1.1" rather than having to add the :8443 suffix. I have no security concerns when using plain HTTP. It also means that I can factory reset my router and not bother immediately having to regenerate and install the certificate on all the clients I might use (or put up with the slow GUI until I do so).

I just use a bookmark. I’m not accessing the web interface from many devices. But yeah for resetting that’s fair.