Are there any known issues with using a local HTTPS setup over Sky wifi with the SR203 router?

[CISCRH]

I recently upgraded to a Sky FTTP package. Until a few days ago I thought the package with the Sky SR203 hub  was working. For the last 20 years I've been using an Apache server installed on my main Windows PC (aka Nemo) to deliver access to databases to laptops. I secure them over the wifi using HTTPS. My main PC was renewed in 2019 & has been hosting my databases without issues until this week. Mostly I access the databases directly on my main PC (aka Nemo) but when I accessed them from two laptops they were reporting error messages concerning HTTPS. I have not made any changes to the set up so I think the change probably happened when upgrading to broadband/SR203.

I am not having with HTTPS sites on the Internet or when accessing the databases using a browser on Nemo. The problems occur when using Chrome, Brave or Edge.

As part of my investigations I have recommissioned an old BT Mini Whole Home mesh system, plugged into the new router, but the HTTPS errors persist when using the mesh network for both Nemo & the laptops.

[TimmyBGood]

@CISCRH 

Is that real SSL with a CA-issued certificate, or self-signed?

[TimmyBGood]

@CISCRH 

And what are be browser error messages?

[CISCRH]

It's real SSL with a self-signed certificate. The  databases (there were several of them) were originally developed for use in a work environment, SSL was a required feature using certificates provided by my network colleagues. My home databases use the same code but didn not require SSL to be active until I got Wifi broadband in about 2007.

The current set up was installed on my main PC in 2019. This problem is only days or possibly weeks old.

Nemo continues to work in SSL mode but the laptops are now reporting SSL certificate errors. As you can see from the screendump the certificates were created in 2019 & were installed on the new laptop Chrome browser in 2023. The Nemo desktop PC screendump shows no errors.