@Clive_A 

Further to my previous post, my browser is reporting that the Certificate is invalid.

I have exported the Certificate details, and Win 10 states that the Certificate is "Not trusted", see following screenshot;-

I have installed the Certificate on my Win 10 machine but, as expected, that made no difference as my machine is not a Trusted Authority

Cheers

mhoam

  @Clive_A 

Apologies for my lack of knowledge, this is not an area in which I have any experience.

I followed the instructions at the following Microsoft site to install the certificate:-

 https://techcommunity.microsoft.com/t5/windows-server-essentials-and/installing-a-self-signed-certificate-as-a-trusted-root-ca-in/ba-p/396105 

and then restarted my Win 10 PC.

I now get the following error "NET::ERR_CERT_COMMON_NAME_INVALID" as shown in the attached screenshot. The additional info suggests that the "name" does not match the certificate. Ad I'm accessing the Router via an IP address, I'm not sure what "name" is being referred to.

Of course, I understand that my network is not exposed in any way by this problem and I can proceed to the Router's admin page by ignoring the error. However, I would like to understand what, if anything, I have done incorrectly or if the Certificate provided by TP-Link is somehow mis-configured

Thanks for your assistance

mhoam

@Clive_A 

I suspect a blog post I have found may be relevant, for some reason the Forum does not accept the URL so please search for the following:-

"Browser not trusting self-signed certificate even after importing into the Trusted root certificate folder" 

at a the site located at "blog dot shafeeque dot in"

This site states that Certificates without a matching "Subject Alternate Name" are no longer trusted in Windows 11, and I suspect also the latest Windows 10 and Chrome.

As TP-Link cannot know the domain name and/or address of all their installed routers, I struggle to see how https can be used.

regards

mhoam