Need Help For Migrating

[OrinTerry]

Hello everyone. I am running a small technology blog, which is in WordPress. The main problem with my blog is that it does not open on any Windows 7 computer normally. I know Windows 7 has lost official support from Microsoft but still, there are plenty of users who still use Windows 7. The blog site is already 'HTTPS' protected but after opening in any browser, it shows 'not protected' next to the URL box. So, if I migrate all the site data to 'ProcessWare', will I get the same problem here too? Any kind of feedback would be greatly appreciated.

[Gideon So]

Hi @OrinTerry,

I think it is the problem of Windows 7 rather than the CMS system. I am afraid that the problem may still persist after you migrate to ProcessWire.

Gideon

 

[Kiwi Chris]

This sounds like an SNI problem, although Windows 7 should support SNI.

https://www.kinamo.be/en/support/faq/which-browsers-support-server-name-indication-sni

The other possibility could be root certificates that aren't recognised by Windows 7, or TLS/SSL versions supported by the server.

A lot of servers have retired older versions of TLS because they're insecure, and by default Windows 7 doesn't support newer versions.

https://www.zdnet.com/article/nsa-urges-system-administrators-to-replace-obsolete-tls-protocols/

If this is the case, changing the CMS won't resolve the problem, as the problem is an issue between the server and Windows 7 not the CMS.

This might help you:

https://help.runbox.com/enabling-tls-1-2-on-windows-7/

If enabling TLS 1.2 on Windows 7 makes the website work with Windows 7, then you have the answer to what is causing the problem.

Unfortunately you can't be sure that anyone running Windows 7 has enabled TLS 1.2, and if the server has disabled older versions for security, it's unlikely to be able to get insecure versions of TLS enabled again, as it puts the server at risk.

It's over a year now since Windows 7 reached end of life, so anyone still using it on the internet is taking big risks with their security. 

 

[virtualgadjo]

hi,

just my two cents ?
whatever system you're on, have a look at your source code, if ever any image or content is in the source linked from an http:// (not https://) src, your browser with display an not protected error near the url
an outgoing link will not cause problem

have a nice day