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

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.