- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Updated from 1.3.1.26 to 1.3.1.44 .. I did not reset / reboot .. just ran the update which said it should take 2 minutes .. 10 minutes later after the firmware update icon was still spinning I figure I would try refresh the page and found the admin UI is now inaccessible. I can still get around on on the web, but the internal webserver of the router seems to be hung. I'm not sure its safe to reboot it and I dont want to brick it. What should I do?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> [...] I can still get around on on the web, but the internal webserver
> of the router seems to be hung. [...]
I'd cycle the power, and see what happens.
> [...] I'm not sure its safe to reboot it and I dont want to brick it.
What real choice do you have?
https://community.netgear.com/t5/x/x/m-p/1577779
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> [...] I can still get around on on the web, but the internal webserver
> of the router seems to be hung. [...]
I'd cycle the power, and see what happens.
> [...] I'm not sure its safe to reboot it and I dont want to brick it.
What real choice do you have?
https://community.netgear.com/t5/x/x/m-p/1577779
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
What does the power LED look like?
There is a manual for the R7000P somewhere at the end of this link:
>>> R7000P | Product | Support | NETGEAR <<<
Check the section Troubleshoot With the LEDs.
Just another user with a set of boilerplate macros.
My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
Can you really show me where in the manual this situation is covered? Because its not. RTFM answers are literally the worst.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
Hiya antinode. Ya .. that's basically what I was thinking ... there's no other choice ... so I took a deep breath .. and rebooted it ...
Thankfully, the worst thing that happened is that I had to reset the master password, but everything else worked just fine.
I swear .. one day I'll build another iptables FW for my network. This shot-in-the-dark nonsense is too un-nerving.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
@idazco wrote:
Can you really show me where in the manual this situation is covered? Because its not. RTFM answers are literally the worst.
No one said RTFM. I said look at the bit in the manual about the LEDs. More accurately, I asked "What does the power LED look like?"
One way to diagnose your "hung" device was to look at the state of the LEDs. Saying that it was "hung" is not enough information to go by. Or, to use your term it is "literally the worst" bit of information that you could have provided.
For future reference, the manual explains what the LEDs should look like in normal operation, and gives tips on troubleshooting when they don't look right.
For example, had you come back saying that the power LED was flashing orange, that would have been useful diagnostic data.
Just another user with a set of boilerplate macros.
My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
@michaelkenward .. OK, you are right .. lets look at this ..
.. the LEDs were as one would have expected .. and according the manual .. "Solid white. The router is ready." .. and indeed it was behaving "ready" by in fact operating normally otherwise, and letting me "still get around on on the web"
Other than this .. the only thing out of place was the the internal web server (not the device in general, or the firware upgrade) was hung. I've seen nothing in the manual for LEDs indicating the status of the internal web server. I comprehend that, according to the manual if the power LED was "Blinking amber." it means "The firmware is upgrading" ... but since it was not I concluded that the firmware upgrade process was not hung.
Therefore as I said, only .. and specifically .. the internal web server was hung.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
@idazco wrote:
Therefore as I said, only .. and specifically .. the internal web server was hung.
What is this "internal web server"?
The last time I looked at my R7000P it didn't have one of those.
Just another user with a set of boilerplate macros.
My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can't access router's admin UI afterupdating from 1.3.1.26 to 1.3.1.44
> What is this "internal web server"?
Presumably, the router's management web server.
> The last time I looked at my R7000P it didn't have one of those.
I'd bet that it does, except when using a peculiarly eccentric
definition of "web server".
Back in the real world...
Sadly, you are dealing with a fellow who seems to believe (adamantly)
that a web site or a web server is only a web site or a web server if
it's _not_ in your router. For example:
https://community.netgear.com/t5/x/x/m-p/1615918
https://community.netgear.com/t5/x/x/m-p/1466400
https://community.netgear.com/t5/x/x/m-p/1373383
[and so on, and on, and on, ...]
As you can see, attempts at rational persuasion have, so far, been
unsuccessful.