Lack of Https support is making this site very difficult to use

[John Lawton]

On my various machines, Edge on Windows, Chrome on OSX, (but not Firefox on Linux), I get the following results:

https://www.protoncompiler.com - works fine, no message, get security padlock.
https://protoncompiler.com - works but "Not secure" message and no padlock.

Maybe something to do with CNAME not covering the latter domain form?

What do others get using my links?

John

[kcsl]

Both your links work fine for me under Edge, Chrome and Firefox on Windows 10, and Safari on my iPhone.

Joe

[John Drew]

G'day John L
If I put https:// in front of either www.protoncompiler.com or omit the www it works in Firefox for me and Edge (W10). If I omit the 's' it goes to https:// so it is defaulting as it should to https. No combination on Firefox or Edge has given me an error message. I haven't loaded Chrome on this machine. So I think the problem has been resolved, thank you.
By the way, don't accidentally add an 's' to protoncompiler. A nasty Asian site has taken that URL.
John

PS Samsung Internet works fine on my phone also

[JonW]

Good work Gents.  I have no idea how to do this kind of stuff.

[charliecoutas]

Good work guys. Life in the digital world is getting so damned complicated. It's no wonder that banks (for example) suddenly stop being able to process things.

Charlie

[Stephen Moss]

On my various machines, Edge on Windows, Chrome on OSX, (but not Firefox on Linux), I get the following results:

https://www.protoncompiler.com - works fine, no message, get security padlock.
https://protoncompiler.com - works but "Not secure" message and no padlock.

Maybe something to do with CNAME not covering the latter domain form?

What do others get using my links?

John

Just tried both links and both resolve to protoncompiler.com in the address bar, and both are secure (Win 10 Chrome Browser), at least I can quote posts again (was showing loading banner but did nothing while unsecure).

However, in my pinned tab for the site (https://protoncompiler.com/index.php) is still showing a not secure, but complained less about it as I could log in without having the click the advanced button to then be able to "log in anyway".
I can only assume (not really sure if that is how that works) that it may be because a new security certificate was issued for the site rather than the previous one being extended and that for some reason the browser is still looking at the old certificate.