NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear R7000 admin web interface failed to start after updating to latest 1.9 firmware
I updated to the latest 1.9 firmware and when I did the admin web interface is no longer available. The wireless network itself came back up and can connect to the internet fine. I am up and running but would really like to have the admin web interface back.
I have no idea which firmware version I updated to since I can't get on the admin web interface to see the version. I clicked on the banner that said "router firmware upgrade available" and it did its thing like it has dozens of times before. It was a 1.9.x_XX_XX_XX version though.
Doing some basic network troubleshooting port 80 simply isn't available.
curl -v http://192.168.1.1 * Trying 192.168.1.1... * TCP_NODELAY set * Connection failed * connect to 192.168.1.1 port 80 failed: Connection refused * Failed to connect to 192.168.1.1 port 80: Connection refused * Closing connection 0 curl: (7) Failed to connect to 192.168.1.1 port 80: Connection refused
I also port scanned 192.168.1.1 (ports 1-65535) with Angry IP Scanner and the only ports it reports being open are:
631, 1990, 5000, 7272, 20005
I have tried restarting my router of course. The interface still isn't available.
Is there someway to get the interface back? I supposed I could try rolling back my firmware to the previous version using tftp to update. That seems like it could be possible to brick it though so want to leave that as a last resort.
Is it possible the IP of the admin interface changed? I didn't see anything in the release notes about the admin interface changing IPs.
11 Replies
> I have no idea which firmware version I updated to [...]
I doubt that it matters much. Whichever version it was, it's hosed
now.> * Failed to connect to 192.168.1.1 port 80: Connection refused
Normally, "Connection refused" means that contact was made with the
target address, but nothing there was listening at the target port. In
this case, the management web server appears not to be running. The
usual explanation for that would be that the firmware is seriously
corrupt.> [...] I supposed I could try rolling back my firmware to the previous
> version using tftp to update. That seems like it could be possible to
> brick it though so want to leave that as a last resort.That's what I'd try; it's pretty close to useless as-is.
> Is it possible the IP of the admin interface changed? [...]
Conceivable, but "Connection refused" suggests otherwise. If you
tried your test at a known-useless address (say, "192.168.1.57"), then
I'd expect some different error message. _Somethings_ seem to be
listening at the default address, just not its httpd (port 80).> [...] It was a 1.9.x_XX_XX_XX version [...]
If I had to choose a 1.9.xxx, it'd be V1.0.9.42_10.2.44, and then I'd
work my way up from there. Probably to the latest
(V1.0.11.116_10.2.100?), and not necessarily gradually.The next challenge would be getting the thing to be receptive to a
TFTP load when it's only stupid, not mostly dead. If its Power LED were
flashing, then you might expect it to take a TFTP load without special
effort. This way, you might need to play with the Reset button (to get
it into the mood), and/or with the timing of the TFTP-PUT command (tocatch it when it is).
mjparme wrote:
I updated to the latest 1.9 firmware and when I did the admin web interface is no longer available. The wireless network itself came back up and can connect to the internet fine. I am up and running ...
This suggests that your R7000 is working as expected on the router front. So it might be worth a bit of investigation before diving into TFTP, not the easiest move to make.
The thing tries to help by warning you of seriously broken firmware, The power LED changes from the normal white colour. What do you see?
I see no hint in your message that you have tried the factory reset.
How do I perform a factory reset on my NETGEAR router? | Answer | NETGEAR Support
There's a more through "recovery reset" that sometimes works, although not usually when the firmware itself reports problems.
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
This might get you back to where you can reflash the firmware with the normal process.
mjparme wrote:
Is it possible the IP of the admin interface changed? I didn't see anything in the release notes about the admin interface changing IPs.
That can happen when the router boots and finds that it is trying to connect to something, usually a modem, that is already using the preferred default IP address.
> [...] seriously broken firmware, [...]
Define "seriously broken". "No httpd" sounds pretty serious to me.
> That can happen [...]
And when it does, would you expect the router (or something else) to
be listening at those ports at the default address? And, presumably, be
working at that address as a router, DNS server, and so on?But sure, try a settings reset. I could be overly pessimistic.
michaelkenward wrote:
I see no hint in your message that you have tried the factory reset.
I considered a factory reset but if the admin interface doesn't come back after a factory reset then I am stuck with a brick since I will not be able to get in and set everything up. At this point the router is working as far as being able to connect devices to it and get on the internet with it. I don't want to make my problem worse.
As far as power LED it is a solid white.
I have no other devices on my network that provide an admin interface on 192.168.1.1. I use a WISP so I don't have a cable modem. The device my antenna on my roof connects to doesn't offer a web interface as far as I know. It is just a PoE device that powers the antenna.
Based on the open ports on 192.168.1.1 it seems like it is probably the router. Port 53 (DNS) is definitely something I would expect to see open on a router. Port 631 (Internet Printing Protocol) seems like something this router would have as well. The other 4 ports are curious though.>nmap -p- 192.168.1.1 Starting Nmap 7.91 ( https://nmap.org ) at 2021-02-22 08:49 CST Nmap scan report for 192.168.1.1 Host is up (0.0036s latency). Not shown: 65529 closed ports PORT STATE SERVICE 53/tcp open domain 631/tcp open ipp 1990/tcp open stun-p1 5000/tcp open upnp 7272/tcp open watchme-7272 20005/tcp open btx
I have actually had this router up on firmware 1.0.9 and 1.0.11 before. They were both so buggy I rolled back to 1.0.8. But I know there are security concerns with 1.0.8 so I decided to give 1.0.9 a go again. And now this. Every firmware past 1.0.8 for this router has been horribly buggy and I have actually ordered another non-netgear router because I am tired of the buggy firmware. I just have to nurse this one along for a week until it arrives.To confirm that the router is on 192.168.1.1, because you have access to the wifi, you could track down the IP address of that. See if that lets you in.
I'm surprised you have had so much trouble with firmware on the R7000. It is one of Netgear's biggest sellers. Yes, people have issues with it, but not enough huge numbers to suggest it is terminally useless.
