Solved

192.168.0.1 login problem: Chrome/Edge Can’t provide secure connection; unsupported protocol etc.

  • 20 July 2022
  • 1 reply
  • 308 views

After going in circles looking for a solution to the “security” concerns of Chrome and Edge that result in not allowing a 192.168.0.1 login, I finally tried old Internet Explorer ("C:\Program Files\internet explorer\iexplore.exe") and Voila! 

Apparently, Chrome/Edge substitute https in place of http - it’s a “feature.”

(Microsoft may discontinue Internet Explorer in future but some other browsers also may work)

icon

Best answer by SURFboard Moderator 30 September 2022, 21:36

View original

This topic has been closed for comments

1 reply

Userlevel 5
Badge +41

Hello Bill Kreamer

 

Thanks for bringing this topic. 

 

Correct, some browsers will do that but not necessarily means there’s something wrong.