Valid Cert, but 'connection not secure' warning persisting

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: na

It produced this output: na

My web server is (include version): unknown

The operating system my web server runs on is (include version): unknown

My hosting provider, if applicable, is: Groovepages

I can login to a root shell on my machine (yes or no, or I don't know): no

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): na

my root domain is:
I built a new page in Groovepages (part of
this new page is hosted on
I followed the instructions to set up cloudflare DNS and pointed cname at 'groove'

Cloudflare set up ssl on *

Ths SSL is valid but shows insecure in browser.

I can't determine what is causing this issue.
Thanks in advance for your help :slight_smile:


Hi @grahamdoessel, and welcome to the LE community forum :slight_smile:

The certificate is managed by CloudFlare.
The content is managed by... you.
It is likely some mixed [http+https] content on the page that is giving you that warning.
If you could show the warning message, maybe we could better direct you.
In any case, at the moment, it doesn't look like anything related to this forum.


That's not what I'm seeing using Firefox:

Edit: doesn't show any (major) problems:
Test Results: - Why No Padlock?

Neither does
SSL Server Test: (Powered by Qualys SSL Labs)

Both note that you have TLS1 enabled, which isn't great, but shouldn't be giving you browser warnings. What browser are you using when you see these errors, and what exactly do they say?


Thanks all, it looks like it got fixed elsewhere
Close and or delete this thread :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.