Joined: 10 Nov 2018 Posts: 154 Location: South Carolina
Posted: Fri Jul 12, 2019 14:47 Post subject:
I'm wondering if anyone else has noticed problems accessing the web GUI after a few days? Internet and wireless all work but even with a wired connection I sometimes can't connect to 192.168.1.1 It just hangs while trying on multiple browsers and devices. I can connect via telnet with putty.
I've googled and found reports like this off and on but never seen any reasons or actual fixes for it.
Interesting. Yeah, I did notice some hiccup of some kind on the GUI, but bushed it off as some one in a million oddity. Havn't had any further trouble. I also auto reboot the router at 4 in the morning, and that seems to clean up a hand full of "odd issues" I can't put my finger on.
With 40134, I have noticed it takes the GUI a little longer to load the page the first time I access it. Maybe 1-2 seconds. Then all other pages load fine.
In the syslog, there are the usual red HTTP errors every time the GUI is accessed. These errors have been going on for a year or so but are cosmetic. A bunch of them are written to the syslog like this:
Jul 13 05:38:14 router1 daemon.info httpd: httpd : Authentication fail
Jul 13 05:38:14 router1 daemon.err httpd: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Using build 40009 I'm seeing the GUI open instantly. I don't mind a few seconds but after a couple of days running 40134, I couldn't get the GUI to open at all till I rebooted the router. Even while internet worked and other pages loaded fine. I could access it via telnet though.
The browsers would just sit spinning trying to access 192.168.1.1. This was on multiple browsers and devices.
I didn't think to look at the system log but will stick to the 40009 build for now.