Message: Suspicious page blocked for your protection when trying to access router info via 192.168.2.1

[dobes5kh]

Trying to access my router info and keep getting this message:

Suspicious page blocked for your protection

https://192.168.2.1/

Your connection to this web page is not safe due to an untrusted security certificate.
Phishing sites often use fake certificates that trigger this alert, and their goal is to obtain your sensitive information.

When I try on my phone:

"Unsecure connection.  Don't enter sensitive information such as passwords and credit cards on this site.  It could be stolen".

Why is this happening and what can I do?

Thanks

[WelshTerrier]

Good Day.

The link in you post in incorrect.

Your modem is secure, but it is not a secure web site. You are not entering the correct information. To access your modem, please enter: 192.168.2.1 into the web address field or use the link as shown in my reply below.

You can choose to select or copy the link as shown using any web browser: http://192.168.2.1/

Keep in mind, your modem is only accessible if you’re currently on your home network.

Here are some useful links to assist in answering any further questions you might have.

Accessing Bell Home Hub

Support for modems, connection and Wi-Fi network - Bell Internet

Thank you for posting your question.

Take care.

[dobes5kh]

Hello,

Thank you for your response.  The link I used originally is the same one you suggested.  I even clicked on the link in your response and I have received the same outcome.  I'm accessing on my home network as well.

This is the msg I received when I clicked on the link you provided: 

Your connection is not private

Attackers might be trying to steal your information from 192.168.2.1 (for example, passwords, messages, or credit cards). Learn more about this warning

net::ERR_CERT_AUTHORITY_INVALID

Back to safetyHide advanced

This server could not prove that it is 192.168.2.1; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.

Proceed to 192.168.2.1 (unsafe)

Is there a way to correct this and ensure safety?

Thanks!

[dks]

What a difference one letter makes. HTTP: not HTTPS: 

[dobes5kh]

I've tried it with both.....http and https....same result so no difference.

I'm not sure if the fact I have Bitdefender installed has any impact?  I have used this security for years though......

Even when prompted by the security popup and I choose to proceed, I'm still given multiple warnings.  

[Vanadiel]

It does not have a publicly signed security certificate because it's an internal IP address that uses a self-signed security certificate.

You could technically speaking manually add the security certificate to your Windows certificate store, but it's much easier to simply click proceed and ignore the certificate issue.

It's normal behavior and nothing to be concerned about.

[Vanadiel]

Forgot to add should you insist to install the certificate manually, here are the instructions for Google Chrome on how to do so. Other browsers use similar methods:

Login to modem first, with your user name and password.

Once logged in, follow the below instructions.

1. Save the certificate for the website to a file:
   1. Click the red triangle icon next to Not secure in your address bar.
   2. Click Certificate (Invalid).
   3. Select Details > Copy to File.
   4. An installation wizard displays.
   5. Click Next.
   6. Make sure the default DER encoded binary X.509 (.CER) option is selected.
   7. Click Next > Browse and save the certificate to a convenient location.
   8. Click Next > Finish > OK.
2. Navigate to the folder where you saved the certificate and double-click the file.
   The General tab displays.
3. Click Install Certificate.
   An installation wizard displays.
4. Click Next and select the Place all certificates in the following store radio button.
5. Click Browse > Trusted Root Certification Authorities.
6. Click OK > Next > Finish.
7. Follow the prompts to install the certificate.

[dobes5kh]

"adding the security certificate" is one of the options listed but it's unsettling to keep seeing these warnings.

Is everyone in agreement that there is nothing to be concerned about?

[Vanadiel · Accepted solution]

If you are using HTTPS it will pop-up that message because it's a self signed certificate rather than a public signed certificate.

You likely have adjusted, maybe through a bit defender update, your browser security level and it's insisting on a public signed certificate hence the error.

It's a very common issue with routers, not just with bell. See here. 

As long as you are sure you do not have a redirect that points 192.168.2.1 to a different IP you should be fine.

In other words, if it logs into your router when you proceed then it's working as intended.

[kidcoconut]

I see two different errors, depending on how I 'hit' the modem:

- if I browse to https://bell.ca/mymodem,  https is crossed out in red in the browser url, it redirects to 192.168.2.1 and the browser error message states that the site _does not have a certificate_ and warns that any username/pwd combo may be passed in the clear

- if I browse directly to https://192.168.2.1, https is struck out in red and an error states that the CN is invalid.  When I inspect the CN, it says 'self-signed cert' or such.  The browser similarly warns that any username/pwd combos could be intercepted

Quite concerning for a modem/gateway and single access point from WAN/LAN.

[kidcoconut]

It is very concerning when the browser says that the site does not have a certificate.

If the certificate is invalid and the username/pwd is being sent in the clear, even on a local network, then it is very concerning, esp given the number of devices we have sitting on our LAN these days.

[kidcoconut]

I am not in agreement.  I would not be concerned only if it was not the central access and gateway and control for all LAN and WAN connections. 

[Vanadiel · Accepted solution]

This is perfectly normal behavior, as 192.168.2.1 is an internal only IP address, better known as a private address block 192.168/16 and reserved for private use only.

As such, there's no public security certificate available for it and you cannot publicly access as it's a private block and internet routers will not route any traffic for it.

[dks]

You can easily prove to yourself that the IP is secure. Use any device not connected to your modem, such as a cell phone on any wireless network. Type in 192.168.2.1 in a browser search bar. The response in the browser will be "Connection timed out".  @Vanadiel is correct. There is no need for any concern. 

[User1637]

why is are the modem pages (192.168.2.1 into a browser) not secure? I get a warning when I access the page and a prompt to tell the owners to consider adding https.