Hello, yesterday i encountered the dreaded "haserl cgi error" that so many other people are running into. As some netduma tech have suggested in other posts, i was able to access the router at 192.168.1.1/adv_index.htm. The interesting thing is that when i used the "reboot" command (from top right 3 dots>reboot) the router lost all settings, reverted to unusual "Netgear" and "netgear-5g" open networks, and the password was reset to "password" and not the unique netgear default password printed on the router sticker. 1, im not sure where it would be pulling that password from. and, 2. that is a MASSIVE security breach. Can someone explain why a netgear firmware, or DUMAos software would have "password" and open networks as a default config?
Also concerning, the router would not allow me to change the default admin password after it reset itself. I could specify a password and attempt to set it. But i was met with a "400 Bad Request This server does not support the operation requested by your client." message when i clicked "Apply". The only way I was able to recover the router was to force a fatory reset from the Admin>Backup>Revert to Factory Settings>Erase" option. And I had to do it twice. Because the first time it didt trigger a reboot or reset. Ive had to factory reset this router maybe 20 times now. With my configs being lost, and the security risks this expensive flagship router on its own, Im afraid i might have to either downgrade to a less feature packed, more reliable router, or move away from netgear/DUMAOS based routers altogether. And yes, before anyone asks or suggests, im on firmware XR1000 1.0.0.74_1.0.63. Im pretty disgusted that this "haserl cgi" error has been persisting for approximately 3 or 4 years. And im very disgusted with how the router is configuring itself with open networks and default passwords like "password". IM not even sure where it would be getting those credentials. I would assume Netgear and Netduma employees would know better. But here we are.
Id ask what a long term solution is. But, it seems like factory resetting and/or TFTFing the most current firmware is the most common suggestion for this. So is there an ETA on a solution that actually fixes the error? Or should i start shopping for a device that doesnt lose its config or expose my network to cyber security threats with no warning and without my knowledge?? If the engineering team needs help. By all means, just ask. i can do a few packet captures. But im not advaced enough to JTAG the device.