Issues with ASUS GT-AX11000's firmware updates.
Issues with ASUS GT-AX11000's firmware updates.
Hello, I hope you're here to discuss this. After trying to update the firmware on my GT-AX11000, the router failed to connect to the ASUS server for the update. I managed to download the newest firmware and installed it manually via the router's web interface. However, when I reopened the web GUI, I received error messages similar to those shown in the screenshots. I confirmed with ASUS on my phone that the firmware I downloaded was current and verified it came from their official site. Could this situation occur? What might be causing it? Am I now using the correct or secure web interface, and is everything safe from a security standpoint? Any advice would be really helpful. Thanks!
It looks like the firmware update completed successfully. A freshly reflashed device shouldn’t retain any data, so the issue likely stems from the original default password instead of a custom one. The certificate handling is odd but makes sense. Unless you suspect a man-in-the-middle attack, that’s unlikely. You should be able to reach ASUS support if needed.
It's completely normal. You'll encounter certificate warnings while accessing sites via HTTPS, just as you did before. Previously, using unencrypted HTTP prompted your router to switch to HTTPS for security.
Thank you for your message. I also reached out to ASUS support again, but they couldn't provide a clear explanation or solution. They suggested I send screenshots via email, which I did, but haven't received any updates yet. Appreciate your assistance.
They used HTTP to reach the router’s web interface, but this method isn’t secure because it lacks encryption and leaves you vulnerable to various attacks. It works well for home networks where the attacker is on the same local network, though it’s still not the best option. Asus suggests switching to HTTPS, which uses encryption and is more reliable. However, HTTPS depends on certificates that often require additional services and can be costly to obtain. For instance, when visiting the site displays its certificate to your browser. Your browser checks it, but if your router doesn’t meet all the necessary conditions—due to budget or technical constraints—it won’t recognize the certificate properly. Chrome flags this as insecure because it can’t verify the router’s authenticity without a trusted certificate authority (CA). This creates a trust issue: your browser sees a fake certificate, triggering a warning. The analogy helps—imagine someone presenting you with a forged ID card that looks legitimate but isn’t issued by any official body. Without proof of legitimacy, you’re left uncertain about who you’re interacting with.