New Firmware for GT-AX6000?

[Saltgrass]

It looks like this router finally got a firmware update.

34860  8/27/2025

@YK_Kwok  I will check for the Secure Web GUI certificate when I get the GT-AX6000 back up and running.

[Saltgrass]

Been trying today to get the https:// to work but it seems even worse than it was before.  I can get it to log in using https: but it still shows "Not Secure" and fails after only one reboot.

It seems the certificate options did change, so perhaps I am doing it incorrectly since none of the guides reference this configuration.

[jzchen]

Which browser are you using?  Are you adding :8443 (port number)?  I noticed for Edge browser the PC needs to be rebooted before it recognizes the certificate...

EDIT:  I never tried exporting the server certificate.  But it should be the Root Certificate that you install in the Trusted folder...

[Saltgrass]

@jzchen I am doing it the correct way.  When I went back to the 98 Pro, it had lost the secure login option, so I just used the same process, and it is working fine again.  Since I use the same browser (Edge) for both routers, that would not seem to be an issue.

There is just something fundamentally wrong with the GT-AX6000.  This situation was reported, to ASUS, by at least two folks in this forum and after all this time, they chose not to fix it.  The router seems to work fine otherwise.

The process should be, update the server certificate.  Then update the root certificate, export and install that certificate on the computer, as you suggest.

[jzchen · Accepted solution]

I'm sorry to read that this is still unresolved.  The GT-AXE16000 is the closest thing I have.  After hard resetting, I followed the instructions by:

1. Accessing the secure login page at https://192.168.50.1:8443 or as noted https://asusrouter.com:8443

Go to -> Advanced and -> "Go on to the webpage (not recommended)"

Log in

Under Advanced Settings -> Administration -> System (tab)

Scroll down to Local Access Config

Verify Authentication Method is either BOTH or HTTPS

(Please don't kill the messenger, as the instructions seem to have changed)!

-> Export Root Certificate

Install that.

Reboot your PC or open a different web browser.  (In order for Edge to work PC reboot has been needed for me.  Google Chrome and Firefox not necessary.  I guess it could be the open Edge session preventing the cert install)...

IF you use WAN access to the router config you can not have both certificates.

[Saltgrass]

@jzchen I tried again this morning with the emphasis on restarting Edge and maybe even the computer.

It was working for maybe two router reboots but failed again back to not accessible page.  This is the same behavior as from before the latest firmware update.

I see the window below when I install the Root certificate, but I cannot remember if that also happens on the BE98 Pro.

I will mark your response as an answer, just so other folks can try the process.

  

[Saltgrass]

I also got this from the log.  The only change is my user name.  The Dec 31 date indicates this is during the reboot process.  I will now go back to the BE98 Pro so no more testing.  I have logs, in case anyone would like to see them.

GT-AX6000: start https:8443
Dec 31 18:00:40 GT-AX6000: start httpd:80
Dec 31 18:00:40 httpd: reload cert and clean all files
Dec 31 18:00:40 httpd: Restore saved SSL certificate...8443
Dec 31 18:00:40 disk monitor: be idle
Dec 31 18:00:40 httpd: Generating SSL certificate...8443
Dec 31 18:00:40 hour monitor: daemon is starting
Dec 31 18:00:40 hour monitor: daemon terminates
Dec 31 18:00:40 Mastiff: init
Dec 31 18:00:41 avahi-daemon[2670]: Alias name "GT-AX6000" successfully established.
Dec 31 18:00:41 Myself: Root certificate updated, auto-generated.

[jzchen]

Just for future reference.  I believe all this can be tested with a double NAT, connected to a LAN port on the GT-BE98 Pro...

I forwarded your concern to a friend at ASUS.  Told him I was tempted to buy one.  Newegg has a good price and free web/animal cam offer...

[Saltgrass]

Don't do what I did.  The technical folks obviously do not believe or can do nothing to fix it.  They had my logs from 8 months ago which is all I can do.   It may be another 6 months before another update is released.

It is a nice little router and can run my entire system all by itself.  The production year shows as 2024.

[jzchen]

It seems there was a misunderstanding of what the concern was.  I've tried to clarify that the certificate goes bad.  If I understood correctly they thought it was the default switch from BOTH to HTTPS, which I think it has been BOTH and still is BOTH?...