This page is not secure (broken HTTPS).

This page is not secure (broken HTTPS).

This page is not secure (broken HTTPS).
This page is not secure (broken HTTPS).
2024-07-05 21:34:02
Model: OC200  
Hardware Version: V1
Firmware Version: 5.13.30.20

Anyone same problem with me what did you do to fixed?

 

Trying to connect on portal of the wifivoucher on chrom and edge broawser always error massage popout sometime if you click the continue botton it will proceed to the portal loging details for code. but most of the time it will now proceed even though you turn off and on the wifi click the proceed ot continue botton.

 

this the error massage on the devtool of an browser I get.

 

This page is not secure (broken HTTPS).

Certificate - missing

This site is missing a valid, trusted certificate (net::ERR_CERT_AUTHORITY_INVALID).

View certificate

Connection - secure connection settings

The connection to this site is encrypted and authenticated using TLS 1.3, P-256, and AES_128_GCM.

Resources - all served securely

 

though I check the cert are still valid.

 

TP-Link

Issued By

Common Name (CN)

localhost

Organization (O)

TP-Link

Organizational Unit (OU)

TP-Link

Validity Period

Issued On

Thursday, June 20, 2024 at 12:28:25 PM

Expires On

Wednesday, September 23, 2026 at 12:28:25 PM

SHA-256 Fingerprints

 

 

  0      
  0      
#1
Options
1 Reply
Re:This page is not secure (broken HTTPS).
2024-07-08 06:39:53

Hi  @Mr_Sky 

 

The HTTPS web interface of your TP-Link device is sometimes flagged as insecure by some web browsers, the reason is that TP-Link's certificate is self-signed (e.g., tplinkeap.net). Most browsers do not accept this type of certificate because tplinkeap.net is not an authoritative CA. However, even if TP-Link's self-signed certificate is not trusted, the connection between a web browser and the tplinkeap.net server is still secure.
The purpose of a certificate is solely to allow a client to verify an unknown server. It has nothing to do with the encrypted connection. The data transmitted between the browser (client) and tplinkeap.net (server) remains safe and encrypted. No one else could decrypt this data except the client and the server because tplinkeap.net uses TLS v1.2 as a secure connection builder, and TLS v1.2 is a widely recognized secure connection protocol. So there is no need to be overly concerned about the insecure warning.

  0  
  0  
#2
Options