Solved Cannot access my router's web admin page via 192.168.0.1

I have a lenovo Aii-in One i5 labptop with 16 GB RAM running fully up-to-date Windows 11 Pro
The pc is running Bitdefender
The pc is running Gogle Chrome
There is no VPN
The system gets its broadband via a Virgin Media Hub 3.0, running purely as a modem
I have a TP-Link AX23 router running off the Hub 3.0, providing wifi and ethernet connection to all my devices
I have a Raspberry Pi 5 attached to the router by ethernet, which is running pi-hole. This is a Linux program that blocks a large amount of adverts and other unwanted junk.The Pi is set up as the DNS server fo the netwok.

Until today everything seemed to work Ok with only occassional problems with wanterd sistes being blocked, something I can easily remmedy

Today I decided to do a review of all the settings made to the AX23 necessary to make the system work correctly. However when I try to log into the router admin page at 192.168.0.1, something I have successfully done many times recently, I get an error message

Local Management via http:is diabled. Try to access device via HTTP.

At the same time the url typed into Chrome (192.168.0.1) is changed to

https://192.158.0.1

with the https coloured red and struck through.

I do not remember recently making any change to either the Windows setting, Chrome settings or Pi settings that could have cause thi problem.

Any ideas?

Many thanks in advance

First start a Command Prompt as Admin
Type ipconfig /all and press Enter.
Confirm that the Default Gateway (your Routers) IP address is the same as you are typing.

Use the TPLInk Web Management page

In the address bar, type http://192.168.0.1 and press Enter.

Chrome and every other modern browser will throw up errors with self-signed certificates.

Could be a setting in Chrome. Try just 192.168.0.1 in Edge.

I just tried the adress of my FritzBox router (mine is 192.168.178.1, is an http adress too) in Edge, I normally use Firefox for that.
Does indeed function, Edge is warning that it is no secure connection, but does make the connection.

I did that as well in a VirtualBox Win11 environment where I did not change anything in the Edge settings: does function!

Fabler2 said:

Could be a setting in Chrome. Try just 192.168.0.1 in Edge.

Click to expand...

I agree. None of my browsers like "https://" when connecting to my router. Either "http://192.168.0.1" or 192.168.0.1 should work.

Thanks for all the helpful replies.

I'm sad to say thst I had also tried Chrome with the same result.

I also tried http://192.168.0.1 but this was not accepted and the again got httpS;?? struck through.

I have also swirche everything of nd then back on - pc, Hub3.0. AX23, Pi 5 with no improvement.

But..........I have been more succesful in a more roundabout way. I wasn't sure of the effect that Pi-Hole may have had with this problem so I went into the Pi-Hole admin page 192.168.0.50 (which was accepted wthout ant diffulty) and white listed 192.168.0.1 and amazingly(to me tht is!!!) the problem has dissappered.

The only niggling problem I now have is that for the last couple of weeks the url 192.168.0.1 was readily accepted. . Today sometghing changed without any known input from me.

Still. as long as it working OK I will settlr for that.

Thanks to you all.

One thing that I did find is stat Chrome uses, by default, something called Secure DNS. This apparently allows Chrome to access a DNS server of its own choosing thus avaoiding the adblocking setup by Pi-Hole. I had to turn off Secure DNS