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):
The operating system my web server runs on is (include version):?
My hosting provider, if applicable, is: Godaddy
I can login to a root shell on my machine (yes or no, or I don’t know): 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): Godaddy
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): I think Google Trust Authority. Attached photo of certificate.
Thank you for the quick reply$B!G(Bs. The certificate was on kindlecrack and not on it anymore since I redirected to kcrackbookreviews. I$B!G(Bm totally confused:) I don$B!G(Bt want folks to think my kindlecrack site is going to steal info (
like the photo I sent two notes ago). What should I do?
I think the IP address is from Google since it$B!G(Bs a Blogger web site?
Also why would www not have content? Should I check under Google console?
How does this forwarding works? Looks like you do that in a wrong way, with the service of shortener.secureserver.net, that removes your own certificate.
A "regular forwarding" (with http status 301) works with an own certificate.
So where did you install the certificate (and how)?
Unfortunately, that’s not the kind of forwarding that you need here, and it won’t work with HTTPS. You’ll need to change the DNS setting back to point directly at your server, and then configure your server to send a 301 redirect. This is the same problem that @JuergenAuer was concerned about.