Not sure what proxy certificate means either but I can look into that to learn more.
I have set my site to ‘Full Strict’ but there seems to be no change, and no error as far as I can tell. breekatt.io still shows as ‘not secure’ however. Not sure if this made any difference, unless it takes time to propagate?
Not that I’d even know how to spell that, but isn’t the issue that the naked domain simply isn’t proxied, hence the settings won’t apply either? @breekatt, can you switch the naked domain from to ? That should do the trick.
If that is the tutorial I needed to follow in order to change to then I’m really at a loss because the cloud that I had under ‘proxy status’ was already set to orange. Starting to think it’s hopeless to get my URL to appear as secure haha? Maybe I could try to contact Cloudflare directly perhaps, not sure if they would reply.
Thanks for the reply and I really appreciate everyone trying to help me solve this!!
To be clear, there is nothing else to be done on my side of things? Not sure what 'Cloudflare would have to do this manually" means, exactly…? Perhaps if I contact them to ask about this, they can help me manually fix the issue? Haha! I’m trying to understand, forgive me.
Suppose it’s not a super huge issue as I can still use the other address configurations, I only wish it would work on the main domain (breekatt.io) so visitors know their connection to my site is secure.
No, you can’t do anything else. I believe the reason you cannot proxy the record for the root domain is because of The orange to orange problem, which essentially means that there are two Cloudflare configurations layered. This won’t work and it means that settings such as “Always Use HTTPS” and Page Rules will not work when you set them on your account.
Because you are using a Cloudflare service behind Cloudflare, their configuration takes priority over yours, so they would need to enable the HTTPS redirect.
I’ll escalate this thread with your domain breekatt.io and see what they can do and whether they can get it enabled for you.
I’m curious if it matters that I continue to edit and reupload my website at all, though? I make edits, deleting the old pin and repinning the new one and adding the new hash to my cloudflare DNS settings. I’m hoping this won’t affect that in any way? And that BreeKatt.io will continue to point to HTTPS regardless?
I know it takes time for the site to propagate and for changes to be made. For example, when looking at my site right now (after a recent edit/update) the URL shows http://breekatt.io.ipns.localhost:8080/
Also, the site isn’t loading properly but I think that might be a Nicepage problem (the software I use to build the site) so I’ve reached out to them because of that.
Ultimately, my question is - once everything has settled and propagated - if my site will point to HTTPS on breekatt.io regardless of any changes I make on my end?
I will have to give it a few days I think, to wait and see what happens with the URL and perhaps let you know. This is all such a learning curve and a process haha. Interesting to learn though.