Unable to login to GT-AX6000 WebGUI, but login via SSH is fine!

[gohlex]

Hi guys, not sure if anyone having the same issue as mine. My GT-AX6000 router (3.0.0.6.102_34791 firmware) having issue on login to WebGUI after the router running for sometime (maybe 20-30mins, can't exactly sure). The error is invalid username or password.

I'm pretty sure the password is correct as I can use the same password to login via SSH and the Asus App login just fine. I even verified the password is correct via the App's router information page.

I will have to reboot all my Aimesh nodes (AX6000 Main+AX3000P+AX3000) using the Asus App before i can login again. I tried factory reset and start from scratch but it still the same. (This seems to related to Aimesh? as i tried reboot only the main node AX6000 but to no avail. got to be all the nodes.)

FWIW, I can't update to 3.0.0.6.102_34793 also, which is similar to thread here. 

Hopefully any kind soul could shed some light on this. Thanks

[jzchen]

I suspect this has to with the Captcha setting, most of the time it does not show nor ask for it but if it expects it then it prevents login.

[gohlex]

@jzchen the Captcha is working. I can see it ask for Captcha only after first 2 failed login. 

[jzchen]

Have you tried a different web browser?  (Make sure it's not the same base/foundation, ie Edge and Chrome are Chromium based so try Firefox, or vice versa).

[gohlex]

Yup. tried Firefox too. still the same.

[Saltgrass]

I saw that message several times when I was switching from an HTTP logon to an HTTPS logon.  Have you made any changes in this area?

The last time I tried to use Captcha on my router (not an AX6000), I never got it to sing in.   It looked like it was asking for info from a picture I was not seeing.

I would not think the Mesh nodes were involved, but you could always turn them off for testing.

[Saltgrass]

One other thing you might check, if you were to be using the VPN in Edge, it may not allow access to the WEB GUI.

Of course, since your situation appears to have a time component, it may be something else.  A certain time period when the problem occurs, may indicate an overheating situation with the router.

The log is not normally understandable by users, but it you keep track of what time certain things happen, you may see something which could be involved.

[gohlex]

@Saltgrass  thanks for the suggestion. I've not made any changes in term of the http to https logon. By default it re-directed to https when i entered http. so the logon is always https.

my guess is not temperature related too as the SSH and Asus app can login just fine. and the power off AX6000 and power on again doesn't solve the login issue. i would need to system reboot from Asus app, which reboot all the nodes.

On the system log, i saw something related to PEB. Probably is hardware and might need RMA?
Jan 1 08:00:28 kernel: ubi0 warning: ubi_calculate_reserved: number of bad PEBs (263) is above the expected limit (40), not reserving any PEBs for bad PEB handling, will use available PEBs (if any)

Sep 6 18:40:40 kernel: ubi0: dumping 2048 bytes of data from PEB 112, offset 0
Sep 6 18:40:40 kernel: ubi0 error: __erase_worker: failed to erase PEB 112, error -5
Sep 6 18:40:40 kernel: ubi0 error: __erase_worker: no reserved/available physical eraseblocks
Sep 6 18:40:40 kernel: ubi0 warning: __erase_worker: switch to read-only mode

[gohlex]

i got these tainted errors too. not sure if anyone know what are these? seems like some filesystem/NAND issue?

Sep 7 16:29:24 kernel: ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 265:0, written 0 bytes

Sep 7 16:29:24 kernel: CPU: 1 PID: 118 Comm: ubi_bgt0d Tainted: P O 4.19.183 #1

Sep 7 16:29:24 kernel: Hardware name: GTAX6000_50991 (DT)

Sep 7 16:29:24 kernel: Call trace:

Sep 7 16:29:24 kernel: dump_backtrace+0x0/0x150

Sep 7 16:29:24 kernel: show_stack+0x14/0x20

Sep 7 16:29:24 kernel: dump_stack+0x94/0xc4

Sep 7 16:29:24 kernel: ubi_io_write+0x574/0x690

Sep 7 16:29:24 kernel: ubi_io_write_ec_hdr+0xc4/0x110

Sep 7 16:29:24 kernel: sync_erase.isra.0+0x11c/0x1f0

Sep 7 16:29:24 kernel: __erase_worker+0x34/0x460

Sep 7 16:29:24 kernel: erase_worker+0x18/0x80

Sep 7 16:29:24 kernel: do_work+0x98/0x120

Sep 7 16:29:24 kernel: ubi_thread+0x108/0x190

Sep 7 16:29:24 kernel: kthread+0x118/0x150

Sep 7 16:29:24 kernel: ret_from_fork+0x10/0x24

Sep 7 16:29:24 kernel: ubi0: dumping 2048 bytes of data from PEB 265, offset 0

Sep 7 16:29:24 kernel: ubi0 error: __erase_worker: failed to erase PEB 265, error -5

Sep 7 16:29:24 kernel: ubi0 error: __erase_worker: no reserved/available physical eraseblocks

Sep 7 16:29:24 kernel: ubi0 warning: __erase_worker: switch to read-only mode

Sep 7 16:29:24 kernel: CPU: 1 PID: 118 Comm: ubi_bgt0d Tainted: P O 4.19.183 #1

Sep 7 16:29:24 kernel: Hardware name: GTAX6000_50991 (DT)

Sep 7 16:29:24 kernel: Call trace:

Sep 7 16:29:24 kernel: dump_backtrace+0x0/0x150

Sep 7 16:29:24 kernel: show_stack+0x14/0x20

Sep 7 16:29:24 kernel: dump_stack+0x94/0xc4

Sep 7 16:29:24 kernel: __erase_worker+0x314/0x460

Sep 7 16:29:24 kernel: erase_worker+0x18/0x80

Sep 7 16:29:24 kernel: do_work+0x98/0x120

Sep 7 16:29:24 kernel: ubi_thread+0x108/0x190

Sep 7 16:29:24 kernel: kthread+0x118/0x150

Sep 7 16:29:24 kernel: ret_from_fork+0x10/0x24

Sep 7 16:29:24 kernel: ubi0 error: do_work: work failed with error code -5

Sep 7 16:29:24 kernel: ubi0 error: ubi_thread: ubi_bgt0d: work failed with error code -5

[Saltgrass]

I will look at your logs again tomorrow, but right now, I also show some of the error -5, so that seems to be normal.  The line I do not see on my log is the one below.  I do not know what it means, but the folks at ASUS may be able to pick it out if you give them an approximate time along with a copy of the log.

ubi0 error: ubi_thread: ubi_bgt0d: work failed with error code -5

As you probably realize, the logs can be quite extensive, so I like to clear the log and start a new one which would be much shorter than one several days long.

In the logs, when the system is rebooting, the date goes back to an earlier time.