Netgear R8000 Remote Management Not Working

[slrcpa1999]

This router is at another house that we own and is about a 3 hour drive away.  The router goes down every couple of months or so due to various reasons.  I setup remote management following the directions below but adjusted the settings to everyone.  When I try to login to reboot the router, the connection times out and I can't login.  Any thoughts?

To turn on remote management:

1. Log in to the router, if you haven't already done so.
2. Click Advanced > Remote Management.
3. Select Turn Remote Management On.
4. Decide whether to give router access to one computer, or several computers in a range of IPs. (You probably shouldn't give access to everyone, unless you have a dial-up connection and a dynamic IP.)
5. If giving access to only one computer, select Only This Computer, and type the computer's IP.
6. If, instead, you want access to a range of IPs select IP Address Range and type the beginning and the end of the range in the From and To boxes. In this example, the starting IP is 68.205.2.56, and the ending IP is 68.205.2.65.
   
   
7. Leave Port Number at the 8080, unless behind a corporate firewall that blocks some ports. Ports that are not typically blocked are for HTTP and HTTPS outbound traffic, port numbers 80 and 443.
8. Click Apply.
9. Write down the IP shown in the Remote Management Address box. This is the address, followed by the port number, that gives remote access to the router. E.g., in this example http://68.203.2.57:8080.

   Accessing your router from the Internet, type your router's WAN IP into the browser, followed by a colon (:) and the
   port number. E.g, if your external IP is 134.177.0.123 and you use port 8080, enter http://134.177.0.123:8080.

[antinode]

> Netgear R8000 [...]

   Firmware version?  Connected to what?

> [...] When I try to login to reboot the router, the connection times
> out and I can't login. [...]

   "try to login" how, exactly?  Which IP address are you using?  If
you're worried about revealing secrets, then the top half of the
address, "a.b" out of "a.b.c.d", would satisfy most of my curiosity.
Or, plug that address into the form at: https://whois.arin.net/ , and
see if it is a public or private address.

> [...] The router goes down every couple of months or so due to various
> reasons. [...]

   That's pretty vague.

   If the router is so confused that it needs to be restarted, then it
might be over-optimistic to think that you'd be able to talk to it from
some remote location.