Router requiring a security exception in the browser to proceed

Verizon is using an expired or outdated certificate. That is why your browser is throwing up a warning. Verizon is the one that needs to fix this issue.

ram1220 said:

Verizon is using an expired or outdated certificate. That is why your browser is throwing up a warning. Verizon is the one that needs to fix this issue.

That's what I suspected. Their certificate expired and they are clueless.

Callender said:

FYI:

Certificate Error, Router home page hacked? (192.168.1.1) - Page 2 - Verizon Fios Community

Solved: Logging into Router Using HTTPS - Verizon Fios Community

Try typing 192.168.1.1 into your browser's address bar (use a browser that doesn't force https)

Except as I said I've been using this browser all along without this happening until last week. It happens on Firefox and Chrome. I have the https everywhere addon but even with it disabled it happens. And it happens even when I type in 192.168.1.1.

As mentioned above, it's very likely their certificate expired, so Firefox and Chrome are doing exactly what they should be doing - telling me the certificate is expired.

The same thing just happened to me. 192.168.1.1 sends me to a web page that redirects me to myfiosgateway.com. When I go there I get the security warning. Not sure why a connection to a local IP address is sending me across the Internet to allow a secure certificate. This happens to me in Windows 7, Windows 10, Android and five different flavors of Linux on both AMD64 and ARM processors, in both Firefox and Chrome, and on systems with and without antivirus software installed, so I don't think the problem is on my end.

I also have a live IP address that doesn't seem to be owned by any of my local devices. When I traceroute it only takes one hop, but the delay is between two and five seconds. Ping is also way longer than any of my local devices. I want to disconnect it, which is how I found out about the login problem, so I can't get into my router control panel to make it drop the address or even to see what is connected there. I power cycled the router and the rogue address reconnected.

So I'm starting to get suspicious about gremlins wandering around my network. Verizon is either dumb as a brick or assumes I am, so it's hard to get past the "reset the router" instruction. Any advice?

Caledon Ken said:

Call Verizon and have them change your wireless password(s).

See if they have a more recent modem router that can be swapped in.

I don't see the point in this. It seems very likely that they have not updated their security certificate and that's why we're seeing this.

I would think that there should be some coverage of this though on some tech news site or something.

Well then wasn't it also self-signed last month, 6 months ago, last year, 2 years ago, etc.? What changed?

Because as I said, I haven't had this issue until a few weeks ago. Before then, I would just go to 192.168.1.1 or myfiosgateway.com and log into the router. As of a few weeks ago I have to make that security exception in my browser.