The cPanel for the website I'm working on has a SSL/TLS feature in the security section

If you go to my website, you will see that it is not secure. There is no HTTPS.

I have this issue with WooCommerce: " Stripe is enabled, but a SSL certificate is not detected. Your checkout may not be secure! Please ensure your server has a valid SSL certificate"

Perhaps it has something to do with my client (the owner of the domain) having moved the domain from GoDaddy to this other guy that hosting on the GoDaddy server??

You don't have a redirect. But this is another problem.

Your https

https://nextlevelcbd.net/

works. Has some mixed content warnings you should fix. FireFox or Chrome, Ctrl + Shift + I, then you see the console. There are some http links, you should change to https.

PS: If your cPanel doesn't support Letsencrypt (missing option under Certificates), it's painful.

But there is a cPanel-certificate with 6 names:

nextlevelcbd.net, 
cpanel.nextlevelcbd.net, 
mail.nextlevelcbd.net, 
webdisk.nextlevelcbd.net, 
webmail.nextlevelcbd.net, 
www.nextlevelcbd.net

Certificates on Server

Domains Issuer Expiration (UTC) Key Size Description Actions
nextlevelcbd.net

mail.nextlevelcbd.net
www.nextlevelcbd.net|- Self Signed -|11/8/19|2048|Cert for “nextlevelcbd.net”| Edit Delete Install|
|nextlevelcbd.net
cpanel.nextlevelcbd.net
mail.nextlevelcbd.net
webdisk.nextlevelcbd.net
webmail.nextlevelcbd.net
www.nextlevelcbd.net|cPanel, Inc.|2/7/19|2048|Cert for “nextlevelcbd.net” 1541696226.0| Edit Delete Install|

How did you get that??

I use my own online tool:

There are a lot of problems in this forum. So it’s easy to check a lot of things in one step.

I noticed some issues when I used the Facebook debugger. What you said sounds like the same sort of thing. I added some metadata tags to the header.php file for the theme it uses. Some of it is out of order, perhaps.

I had to add this to the functions.php file:
add_filter( ‘jetpack_enable_opengraph’, ‘__return_false’, 99 );

Could that be what is preventing the SSL certificate from working? It did not have HTTPS before I added the tags.

That’s great… I am no coder or “guru” and am just trying to learn how to get an SSL certificate for this website that works with the eCommerce features.

Is there something that will fix those issues automatically? I have no idea of how to do it.

Sorry about all these questions. It looks like this indicates the problems but I need to learn how to fix it. Is there a place where it will tell me how??

Comments

A name “nextlevelcbd.net” is domain, public suffix is “net”
A good: one preferred version: non-www is preferred
B https://nextlevelcbd.net/ 132.148.155.20 200 Missing HSTS-Header
B https://www.nextlevelcbd.net/ 132.148.155.20 301 Missing HSTS-Header
C Error - more then one version with Http-Status 200
D http://www.nextlevelcbd.net/ 132.148.155.20 301 http://nextlevelcbd.net/ wrong redirect one version http to other version http - first redirect to https without new dns query
D http://www.nextlevelcbd.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 132.148.155.20 301 http://nextlevelcbd.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de wrong redirect one version http to other version http - first redirect to https without new dns query
H fatal error: http result with http-status 200, no encryption
O Old connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384
http://nextlevelcbd.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 132.148.155.20 404 1.740 seconds Warning: 404 needs more then one second
A Duration: 16837 milliseconds, 16.837 seconds

My other question is… If I find out how to add the metadata tag in the correct order, will it fix the problem? Are tags in the header like this the cause of the SSL issue??:

<title>Next Level CBD Cream</title>

<!-- Schema.org markup for Google+ -->
<meta itemprop="name" content="Next Level CBD, LLC">
<meta itemprop="description" content="Next Level CBD, LLC distributes a special pain relief cream made with CBD oil. We will seek, train and assist 1000 individual distributors to sell 25 thousand units of product monthly.">
<meta itemprop="image" content="https://www.nextlevelcbd.net/nextlevelcbd-logo-facebook.png">

<!-- Twitter Card data -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@robertheston">
<meta name="twitter:title" content="Next Level CBD Cream">
<meta name="twitter:description" content="Next Level CBD, LLC distributes a special pain relief cream made with CBD oil.">
<meta name="twitter:creator" content="@robertheston">
<!-- Twitter summary card with large image must be at least 280x150px -->
<meta name="twitter:image:src" content="https://www.nextlevelcbd.net/nextlevelcbd-logo-facebook.png">
<!-- Open Graph data -->
<meta property="og:image" content="https://www.nextlevelcbd.net/nextlevelcbd-logo-facebook.png" />
<meta property="og:title" content="Next Level CBD Cream" />
<meta name="og:site_name" content="nextlevelcbd.net"/>
<meta property="og:image" content="https://www.nextlevelcbd.net/nextlevelcbd-logo-facebook.png" />
<meta property="og:description" content="Next Level CBD, LLC distributes a special pain relief cream made with CBD oil. We will seek, train and assist 1000 individual distributors to sell 25 thousand units of product monthly." />
<meta property="article:tag" content="cbd oil, topical pain relief, cbd cream, purchase, distributor opportunity, training, cbd for pain, cannabidiol, cannabis" />
<meta name="og:locality" content="Cary"/>
<meta name="og:region" content="NC"/>
<meta name="og:country-name" content="USA"/>
<meta name="og:email" content="greg@nextlevelcbd.net"/>
<meta name="og:latitude" content="35.767290"/>
<meta name="og:longitude" content="-78.834100"/>

Meta tags in your website are not relevant to your ssl-questions.

First a browser starts a SSL-connection, then it’s something like “http over SSL”.

That's a question of your system configuration. There are millions of different systems and config options.

You should add a redirect

http://nextlevelcbd.net/ -> https://nextlevelcbd.net/

So every user who starts with the http version: The result ist https://nextlevelcbd.net/.

From what little I know… and that’s not much… it appears that he (the owner, Greg) cannot use the SSL certificate because he moved his website to another host, albeit the same server, perhaps, so the certificate was acquired when he had the account with GoDaddy. There still seems to be some way to get to it, but it requires, perhaps, the “redirects” you referred to… something I do not know how to manipulate.

The only logical solution from my point of view is to download his site to my local (xampp) server then upload it to a new account at a host that has “Let’s Encrypt.” Just forget about what he is using now and make a fresh start. I do know how to transfer the site back and forth with xampp and ftp and move the database and use queries that will fix the directory paths for whatever location the site resides…and also fix the wp_config.php file.

That way there should be no confusion. Later, I should go learn the correct way to place the metadata tags.

Do you know if GoDaddy has the Let’s Encrypt feature in the security section of their cPanel??

Thank you for your replies!! I just graduated with a degree in Web Technologies, but we did not explore issues like this. It’s a little confusing.

I don't have a clear picture of this but I've said before that

However, this might vary depending on your hosting plan with GoDaddy and I don't have a recent official confirmation of this position. It seemed clearly true as of a year or two ago.

Also,

Maybe your courses were focused on front-end topics like HTML, Javascript, and CSS. The web platform, web hosting, and the Internet infrastructure include a lot of other technologies.

It seems that the technology landscape has gotten complex enough that a lot of people who work with the web have divided themselves into front-end developers and back-end developers, and the back-end developers may be further separated from system administrators or devops engineers.

But I think some curricula are short-changing people by not giving them a useful big picture view of all of these technologies, where they come from, and how they work together.

That being said, what Let's Encrypt aspires to is integration with hosting providers and in server software so that almost all configurations can get, install, and renew certificates automatically, without significant human intervention. When you don't have that experience, it means that we don't yet have the levels of integration that we want. :slight_smile:

1 Like

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