I don't even understand how to do this

My domain is: www.akashikonline.com which is hosted at www.apocalypsewriters.com
Hosted by godaddy.com

I’ve read and my eyes bleed and I’m sick of trying to get it. I don’t undestand the pages much less where to go and how.

I got a certificate for Akashikonline.
I don’t know where to put it, how to do the weird “check and get verified or else” stuff, and quite frankly at this stage i"m just going to choose to be unsecure until I magically have someone to do it for me. I guess.

I have a lot of words for this SSL business. They’re not nice words.

Hi @Spearcarrier

do you really have a certificate? Certificates are listet in Certificate Transparency logs - I can't find a certificate with that domain name ( https://check-your-website.server-daten.de/?q=akashikonline.com ).

Crt.sh is currently buggy, but Certspotter has new certificates. A manual check of the Google search - the same result, no certificate found.

Or is it only the validation file?

There is a template.

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. crt.sh | example.com), 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:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

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

So here’s the deal. My OP filled out as much of that template as I knew the answers to…

Thank you anyway for you reply. I’ve decided to shoot the situation a bird. I don’t understand it, I’ve got WAY too much going on around me to try to understand it, and my website now sports a nice notice saying to use something besides chrome. I’m so frustrated about it right now I have nothing but curse words on the matter.

Bottom line, if your site is hosted by a web hosting provider, the provider should be obtaining, installing, renewing, etc. the certificate for you. If yours won’t do that (and I don’t think godaddy will–indeed, as I understand it, they go out of their way to make it hard (if not impossible) for you), there are hundreds of others who will, and you should seriously consider voting with your wallet and moving to one of them.

Now, if you’re actually running your own server, then all that stuff is your responsibility. The concepts aren’t especially difficult, and Let’s Encrypt does aim to make the task easier, but there’s a certain degree of knowledge you should have if you’re running your own server on the Internet.

1 Like

Yeah I figured it was Godaddy’s fault. But as far as voting with my wallet, I’m stuck on a lot of counts. To move would be to move more than just 1 website and domain, and where I’ve looked into transferring didn’t understand that either. Add to that the cost of moving. The other half just lost another job offer today - there’s nothing in the coffers to vote WITH.

Whch is another problem. Godaddy wants at least $100 a year. SO many places have these overpriced certificates as if everyone just has money swimming around, you know, simply because they’re on the 'net. I thought Letsencrypt was a solution - but I guess that’s only if you can code. Which I cannot. And if I could code I’d probably do one of the options I found where you can make your own certificate from scratch. =^-^=

The most I’ve been able to do is move my publisher store to a new home, which also doesn’t have an SSL certificate. And again. I don’t understand any of this and have given up trying.

If you use an uncooperative web host, much of the certificate-related advice that you find online may not apply to your situation or may apply only with difficulty. We’re in the midst of making some changes to the Certbot web site that should make this clearer up front.

I’m sorry about this situation, but there’s really literally no way that we can get our certificates onto web hosting environments whose operators don’t want us to, or make it easy where the web hosting operators don’t want to make it easy. They’re the ones who determine what certificates their customers are allowed to use (or not) and what tools their customers can use in their hosting environments (or not).

1 Like

I know what you’re saying, trust me. It’s frustrating and there’s nothing that can be done about it on our level I expect. When I go into my interface there’s an area for SSLs but it just reroutes me to the front of my account.

They call me on the phone wanting me to pay over a hundred a year. The man on the phone told me that if I could code it myself, the cost of putting it in would be alot cheaper. “Only 99 dollars!” Yeah. Pfft. M’kay bud.

In the meantime, the Godaddy login page has been flagged by my Chrome and by Avast for not being secure.
Also, my login to Adsense.

I understand that you're frustrated, but this statement isn't anywhere close to the truth, even if by "code" you mean only "run text-based commands" (which, well, it just doesn't mean). There are literally hundreds of web hosts who will automatically obtain, install, and renew a Let's Encrypt cert with no more than the click of a button (and in some cases, not even that), and at no additional cost over whatever their hosting costs anyway--you can find an incomplete list at:

Many of these providers even include SSL on free hosting--and in any event, any cost in hosting with a different provider should be offset by not paying for hosting with GoDaddy any more. The problem is that many web hosts (including GoDaddy) have been used to SSL and certificates being a cash cow for many years, and they aren't willing to give that up.

Now, if you don't care to pursue this any further, it's your site and that's your call. But browser prompts for HTTPS (and warnings about sites served without it) aren't going to go away; indeed, they're much more likely to increase in the foreseeable future. If you're running a public web site, you're going to need to deal with this at some point.


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