Took a minute to get my login screen over https

[LimJK]

Hi,
I have a strange issue trying to login to my router. It took me about a minute before I get the login screen.
Specifically, when accessing router using https it takes about a minute to get login screen:

• https://router.asus.com:8443
• https://192.168.128.1:8443

However, if accessing over http it is split second:

• http://router.asus.com
• http://192.168.128.1

I think this problem appears to start occurring on my MacBookPro with the latest macOS Catalina 10.15.4 with Safari during this 384_beta2 cycle. I do not have issue using accessing using Safari on iOS 13.4.

I have done Complete Factory Reset on RT-AX88U, removed all scripts … see the same problem, now I just have reinstall all the scripts in my signature from scratch.

Any advice would be greatly appreciated. Thanks.

 

[Adamm]

Are you using a self signed HTTPS certificate? If so you will need to "import" it to your device.

 

[LimJK]

Are you using a self signed HTTPS certificate? If so you will need to "import" it to your device.

Adamm,
Thanks for your reply. I don’t know how to make self signed HTTPS certificate
I used Asus DDNS with Let’s Encrypt, it appears to be set up correct. How do I check that I have a self signed certificate? Sorry for such basic question. Thanks.

 

[juched]

Sometimes it gets slow for me too. I use this command to make it fast again.

 service restart_httpd

Can you try that and see if it helps?

 

[LimJK]

Sometimes it gets slow for me too. I use this command to make it fast again.

 service restart_httpd

Can you try that and see if it helps?

Juched,
Thanks for your reply ... I tried over SSH

• service restart_httpd

Unfortunately it does not help for my case

 

[LimJK]

Hi,
Update:

• If I click on the 2 https links in my original post ... it takes me to the login screen immediately.
• However if I copy the link and paste on the URL address bar ... I got the same problem
• As mentioned earlier if I use Safari on iOS 13.4 ... it works too

 

[Maverickcdn]

Are you accessing it locally on your own network (not through the internet remotely??)

If you dont need remote router access over the internet, disable WAN access on the admin page, change it to HTTP only and be done (this is a strong recommendation). There is no need for local HTTPS connections on your own network you control and maintain.

 

[bluzfanmr1]

@LimJK I too am experiencing this issue. Never had the issue on my old MacBook but last week I got a new 2019 MacBook Air and that's when it started. I tried troubleshooting but gave up and went back to http since I know there is not much need for the https on my own network.

 

[bluzfanmr1]

Also, once it would log in via https, navigation was terrible and pages would hang for a long time or just crap out. It also started pegging the router cpu's and therefore killing the network. Took me a half day to figure out what was going on and after switching to http only, all is well.

 

[dave14305]

I've been having this issue since upgrading to iOS/iPadOS 13.4 and using https on John's fork. It's mostly hanging for me on the System Log page. But it works fine in Private Browsing mode or any other browser on iOS. http is not affected at all. I've cleared Safari data, wiped the phone, wiped the router, tried a self-signed cert, changed domain names, and eventually downgrading the iPad to 13.3.1 fixes everything. Not sure where to go.

Edit: I use a Pixelserv CA signed certificate for my router GUI.

 

[eclp]

Same for me. With iPadOS 13.4 the login page loads only after several refresh attempts. But only with Safari, not with other browsers.

 

[dave14305]

Same for me. With iPadOS 13.4 the login page loads only after several refresh attempts. But only with Safari, not with other browsers.

Thank you, I've been waiting for someone else to prove I'm not insane!

 

[john9527]

I've been having this issue since upgrading to iOS/iPadOS 13.4 and using https on John's fork. It's mostly hanging for me on the System Log page. But it works fine in Private Browsing mode or any other browser on iOS. http is not affected at all. I've cleared Safari data, wiped the phone, wiped the router, tried a self-signed cert, changed domain names, and eventually downgrading the iPad to 13.3.1 fixes everything. Not sure where to go.

Edit: I use a Pixelserv CA signed certificate for my router GUI.

Just a bit of additional data....
On my fork, in addition to having a watchdog check that the httpd server process is running, it also tries to do a small transfer of a file header to make sure it's really alive. Whatever happens with Safari, the file transfer watchdog times out and restarts the httpd server thinking it's dead.

 

[LimJK]

@LimJK I too am experiencing this issue. Never had the issue on my old MacBook but last week I got a new 2019 MacBook Air and that's when it started. I tried troubleshooting but gave up and went back to http since I know there is not much need for the https on my own network.

Also, once it would log in via https, navigation was terrible and pages would hang for a long time or just crap out. It also started pegging the router cpu's and therefore killing the network. Took me a half day to figure out what was going on and after switching to http only, all is well.

blusfanmr1,
Thank you for confirming that I am not the only one having this issue. Looks like it is the latest update of macOS Catalina 10.15.4 that is giving us the problem, the workaround of using http instead of https works fine for me

 

[LimJK]

Are you accessing it locally on your own network (not through the internet remotely??)

If you dont need remote router access over the internet, disable WAN access on the admin page, change it to HTTP only and be done (this is a strong recommendation). There is no need for local HTTPS connections on your own network you control and maintain.

Maverickcdn,
Thanks for your reply. I normally access my Router configuration page locally within my own home network. However, if I have a need to access it remotely, I only used OpenVPN. Yes I aways DISABLE WAN access on the admin page.

 

[jrmwvu04]

blusfanmr1,
Thank you for confirming that I am not the only one having this issue. Looks like it is the latest update of macOS Catalina 10.15.4 that is giving us the problem, the workaround of using http instead of https works fine for me

I have been watching this unfold and I’m confused by what value is added by using https. Why bother with all the problems this adds?

 

[dave14305]

I have been watching this unfold and I’m confused by what value is added by using https. Why bother with all the problems this adds?

For me, I do it because I can and I’ve learned a lot about certs in the process. Eventually, browsers will shame all sites using plain http with warnings and scary colors.

 

[jrmwvu04]

For me, I do it because I can and I’ve learned a lot about certs in the process. Eventually, browsers will shame all sites using plain http with warnings and scary colors.

Ok, I can accept that. I tried it out myself many, many moons ago and did not stick with it because it was slow and problematic. Carry on. Perhaps one of these days I’ll have to do it again and enjoy the fruits of your current labors.

 

[LimJK]

I've been having this issue since upgrading to iOS/iPadOS 13.4 and using https on John's fork. It's mostly hanging for me on the System Log page. But it works fine in Private Browsing mode or any other browser on iOS. http is not affected at all. I've cleared Safari data, wiped the phone, wiped the router, tried a self-signed cert, changed domain names, and eventually downgrading the iPad to 13.3.1 fixes everything. Not sure where to go.

Edit: I use a Pixelserv CA signed certificate for my router GUI.

Dave14305,
Strange my iPhone XsMax with iOS 13.4 appears to be ok with https://router.asus.com:8443 anyway for now I am just going to use http://router.asus.com in a secured environment.
Observation: something happened to new Apple macOS 10.15.4 and iOS 13.4 that introduces this https issue / feature.

 

[Maverickcdn]

Maverickcdn,
Thanks for your reply.

No worries, back in the day I ran self singed certificates and used HTTPS but Ive found over the last few years the Asus/Merlin firmware using HTTPS is slower on most browsers compared to HTTP so Ive just always run with that lately.

Like I mentioned, browsing on a local network with no unknown/shady clients and HTTP will do, but yes one day sooner than later browsers will be warning about all non-HTTPS connections like @dave14305 mentioned