Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[johnpd]

HTTPS server is enabled on my 880L but when I try to access the router using HTTPS instead of HTTP, Firefox will not allow access. If I use just HTTP, I get a small message from Firefox but I can ignore it and log in as usual. When trying HTTPS, the message I get is:

"The owner of 192.168.0.1 has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website."

This indicates the the certificate associated with the website cannot be verified. Can I not use HTTPS to access a router as there appears to be no certificate associated with it?

JohnD

[FurryNutz]

What version of FF are you using?

FF x32 or x64? Do other browsers exhibit same problem?

Sent you a PM...

[FurryNutz]

Do you have a port setting enabled with the HTTPS?

HTTPS is mainly for more secure access from a remote location, like me trying to get in or you trying to access the router from work. Looks something like this:
https://##.##.###.###:#### where ##.##.###.### is the WAN IP address that the router gets from the ISP service/modem and the :#### is the port selection you use with the remote access IP address. 8080, or 8081 etc...

[johnpd]

I am using FF 54.0.1 32bit. I also tried IE and Edge. They also say the site is not secure and will not allow access. I have not done anything with ports.

JohnD

[johnpd]

IE error message:

Your PC doesn’t trust this website’s security certificate.
The hostname in the website’s security certificate differs from the website you are trying to visit.
Error Code: DLG_FLAGS_INVALID_CA
DLG_FLAGS_SEC_CERT_CN_INVALID

JohnD

[FurryNutz]

Are you trying to log into the local 192.168.0.1 address using HTTS or HTTP://192.168.0.1? Local side access to the UI doesn't need HTTPS.

If your at work and have remote access enable, then HTTPS://WAN IP address:port#### would be needed and used.

[johnpd]

OK, the problem is that Firefox added warning messages indicating when a site does not use "https" for access. The message can block user or password fields. I have been able to work around it so I will stick with the plain old "http".

Thanks Furry,

  JohnD

[FurryNutz]

Ok, Ya, for local side access, HTTP is recommended and the norm. From the WAN side, HTTPS should work though.

Enjoy.