Archer C1200 FW Upgrade Bug
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer C1200 FW Upgrade Bug
Model :
Hardware Version :
Firmware Version :
ISP :
After upgrading firmware on brand new Archer C1200 V3.0 to version 3.0.3 Build 20180104 Rel.52829 (US), Logging into web interface results in "No such file or directory" on page "192.168.0.1/webpages/index.html". After doing a factory reset using the pin button on router, it asks you to set up new password, accepts the change, but then immediately redirects to the same "No such file or directory" on the same URL. Reloading "192.168.0.1" allows you to log in using the same password you just set, but then also immediately redirects to "No such file or directory" on the same URL.
If I take the "index.html" off the end of the URL, it loads up the page as it should be. It appears this firmware update changed the page names, but failed to update all the relevant redirects to the new filenames. I can get by with this workaround, but suspect this could be detrimental to other users. Hopefully this gives other users helpful info - and devs a good place to look for fixing the issue.
Hardware Version :
Firmware Version :
ISP :
After upgrading firmware on brand new Archer C1200 V3.0 to version 3.0.3 Build 20180104 Rel.52829 (US), Logging into web interface results in "No such file or directory" on page "192.168.0.1/webpages/index.html". After doing a factory reset using the pin button on router, it asks you to set up new password, accepts the change, but then immediately redirects to the same "No such file or directory" on the same URL. Reloading "192.168.0.1" allows you to log in using the same password you just set, but then also immediately redirects to "No such file or directory" on the same URL.
If I take the "index.html" off the end of the URL, it loads up the page as it should be. It appears this firmware update changed the page names, but failed to update all the relevant redirects to the new filenames. I can get by with this workaround, but suspect this could be detrimental to other users. Hopefully this gives other users helpful info - and devs a good place to look for fixing the issue.
