# Confused about how to create auto renew for ssl cetificate **URL:** \ **Category:** Help\ **Created:** [April 23, 2022, 8:00am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416 "2022-04-23T08:00:07Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Firestar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/32/57668_2.png) [@Firestar](https://community.letsencrypt.org/u/Firestar)\ **Post date:** [April 23, 2022, 8:00am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/1 "2022-04-23T08:00:07Z")
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](https://crt.sh/?q=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: [rogerwoolger.org](http://rogerwoolger.org) I ran this command: na It produced this output: na My web server is (include version): I don't understand how to find this The operating system my web server runs on is (include version): My hosting provider, if applicable, is: [tsohost.com](http://tsohost.com) I can login to a root shell on my machine (yes or no, or I don't know): I dont know I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes cpanel, where do I find the name ? The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): I am sorry I do not understand techy language. I can follow step by step instructions. I did some months ago install ssl certif then I had to move my account to a different package in tsohost and now I do not know how to install automatic renewal ssl certif. I have gone to certsage to get new ssl certif and it states - urn:ietf:params:acme:error:unauthorized 199.59.243.200: Invalid response from [http://rogerwoolger.com/.well-known/acme-challenge/i4og19dP3Sqr2Yer\_kBQk-qQwIsj7phfrDrzWsY2CrA:](http://rogerwoolger.com/.well-known/acme-challenge/i4og19dP3Sqr2Yer_kBQk-qQwIsj7phfrDrzWsY2CrA:) anyhelp with what I do now ? ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [April 23, 2022, 9:04am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/2 "2022-04-23T09:04:15Z")
> [@Firestar](#): > > My hosting provider, if applicable, is: [tsohost.com](http://tsohost.com) There is no autorenew for you. If you like shared hosting, you should look for a company that gets a certificate automagically for you. There are several. Right now, I think your best bet would be enrolling in cloudflare, enabling their cdn, and install one of their origin certificates on your server. ---
**Author:** ![Firestar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/32/57668_2.png) [@Firestar](https://community.letsencrypt.org/u/Firestar)\ **Post date:** [April 23, 2022, 9:13am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/3 "2022-04-23T09:13:57Z")
can you help with this - [![](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/90/57668_2.png)](https://community.letsencrypt.org/u/Firestar) [Firestar](https://community.letsencrypt.org/u/Firestar) 1 [1h](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416) 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](https://crt.sh/?q=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: [rogerwoolger.org](http://rogerwoolger.org/) I ran this command: na It produced this output: na My web server is (include version): I don't understand how to find this The operating system my web server runs on is (include version): My hosting provider, if applicable, is: [tsohost.com](http://tsohost.com/) I can login to a root shell on my machine (yes or no, or I don't know): I dont know I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes cpanel, where do I find the name ? The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): I am sorry I do not understand techy language. I can follow step by step instructions. I did some months ago install ssl certif then I had to move my account to a different package in tsohost and now I do not know how to install automatic renewal ssl certif. I have gone to certsage to get new ssl certif and it states - urn:ietf:params:acme:error:unauthorized 199.59.243.200: Invalid response from [http://rogerwoolger.com/.well-known/acme-challenge/i4og19dP3Sqr2Yer\_kBQk-qQwIsj7phfrDrzWsY2CrA:](http://rogerwoolger.com/.well-known/acme-challenge/i4og19dP3Sqr2Yer_kBQk-qQwIsj7phfrDrzWsY2CrA:) ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:15am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/4 "2022-04-23T09:15:50Z")
Hi again 🙂 > [@Firestar](#): > > My domain is: `rogerwoolger.org` > [@Firestar](#): > > `http://rogerwoolger.com/.well-known/acme-challenge/i4og19dP3Sqr2Yer_kBQk-qQwIsj7phfrDrzWsY2CrA` I'm noticing both a `.org` and a `.com` here. Are you entering `.com` into CertSage when you should be entering `.org`? ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:20am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/5 "2022-04-23T09:20:26Z")
> [@9peppe](#): > > Right now, I think your best bet would be enrolling in cloudflare, enabling their cdn, and install one of their origin certificates on your server. Cloudflare terminates TLS/SSL and thus decrypts all of its clients' traffic, thus acting as a man-in-the-middle. Some people (myself included) don't want to be in bed with Cloudflare in this way. ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [April 23, 2022, 9:22am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/6 "2022-04-23T09:22:39Z")
Neither do I, but they provide a valuable service. I can like them or not but I still trust them more than a random shared hosting provider, if somebody has to have my keys. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:25am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/7 "2022-04-23T09:25:37Z")
The hosting provider still needs to have the private key for the backend server in order for SSL to work. In the case of Cloudflare Origin CA certificates, BOTH Cloudflare AND the hosting provider have the private key for the backend server, not that it much matters since Cloudflare already has decrypted copies of all traffic anyhow. TSOHost is owned by GoDaddy, one of the largest hosting providers on Earth. ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [April 23, 2022, 9:28am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/8 "2022-04-23T09:28:42Z")
I wouldn't trust GoDaddy either, but at the end it's a matter of threat model: TLS is usually meant to protect your users, not you. It doesn't matter if cloudflare or GoDaddy have your keys, it's in-transit interception you usually want to avoid. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:30am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/9 "2022-04-23T09:30:06Z")
Fair enough. I've been a GoDaddy user for decades and have never heard of them having a breach, but to each their own. 😉 ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [April 23, 2022, 9:31am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/10 "2022-04-23T09:31:08Z")
I don't know them from a technical standpoint. But their marketing and business practices just irk me too much. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:31am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/11 "2022-04-23T09:31:43Z")
You're not alone in your feelings there. 🙃 ---
**Author:** ![Firestar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/32/57668_2.png) [@Firestar](https://community.letsencrypt.org/u/Firestar)\ **Post date:** [April 23, 2022, 9:31am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/12 "2022-04-23T09:31:50Z")
Hi yes you are right I have redone the certsage and this is ok. Now how do I renew then as the file certsage.php is already in the website ? thanks. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:34am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/13 "2022-04-23T09:34:18Z")
> [@Firestar](#): > > how do I renew then as the file certsage.php is already in the website ? The "renewal process" is simply acquiring a new certificate and installing it into cPanel in the exact same way you originally did. You're just replacing the expiring certificate and its private key with the new certificate and its private key. If you already have `certsage.php` installed, great! You don't need to install it again. Just use it! 🙂 CertSage should overwrite any existing certificate and its private key in the CertSage folder with the new certificate and its private key. Once that's done, you just need to install those into cPanel. ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 9:39am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/14 "2022-04-23T09:39:55Z")
Right now it looks like a default, self-signed (snake oil) certificate is installed for `rogerwoolger.org`. ---
**Author:** ![Firestar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/32/57668_2.png) [@Firestar](https://community.letsencrypt.org/u/Firestar)\ **Post date:** [April 23, 2022, 9:59am UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/15 "2022-04-23T09:59:55Z")
Hi not sure what that means, but does not sound good. I find it hard to know where actually to go as all the websites are under one primary domain. Under the cpanel which is for a primary domain, I am not sure why the certif are being listed in the primary file and not the domain [rogerwoolger.org](http://rogerwoolger.org) ? ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/c/3/c35cab3e06f80287563f9efdc29014f7e28e61d6.jpeg) ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [April 23, 2022, 12:03pm UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/16 "2022-04-23T12:03:55Z")
It looks like you [got a new cert for the **.org** site several hours ago](https://decoder.link/sslchecker/rogerwoolger.org/443). Are you still having trouble accessing that site securely? Note to other volunteers: The site is sending the "short chain" (R3) so possibly that hosting service has that as default. I see your **.com** site is using an ECDSA cert chain (E1) and expires in less than 3 weeks. It is unusual to have that kind of cert from a hosting service. You should work with them to ensure that cert is updated too. ---
**Author:** ![Firestar](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/firestar/32/57668_2.png) [@Firestar](https://community.letsencrypt.org/u/Firestar)\ **Post date:** [April 23, 2022, 1:16pm UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/17 "2022-04-23T13:16:43Z")
Hi I have managed to cert the [rogerwoolger.org](http://rogerwoolger.org) site but I am having issues with my other website [regresyondmp.com](http://regresyondmp.com) Ihave successfully got the certif [CertSage](http://regresyondmp.com/certsage.php) but when I go to the cpanel nothing is there except for the old certif I uploaded in jan this year. any ideas of where/ and what to do ? is it because of too many folders called cert ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/9/f/9f297ca81df0b006b857eb442206677fa7227093.png) ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [April 23, 2022, 5:15pm UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/18 "2022-04-23T17:15:30Z")
FYI to all: `.com` and `.org` are being hosted at two separate IPs: [we can `ignore` that `.com` within this thread] ```nohighlight Name: rogerwoolger.org Address: 92.205.8.227 Name: rogerwoolger.com Address: 199.59.243.200 ``` ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [April 23, 2022, 6:15pm UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/19 "2022-04-23T18:15:05Z")
> [@Firestar](#): > > nothing is there except for the old certif I uploaded in jan Maybe the latest cert is in the _CertSage_ folder right under _public\_html_? (just a guess) ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [April 23, 2022, 7:55pm UTC](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416/20 "2022-04-23T19:55:56Z")
If you go to the file manager in cPanel and edit the `certsage.php` file located in the webroot folder of whichever domain is of interest, you will find a `dataDirectory` variable at the top inside the `certsage.php` file that will indicate where the relevant `CertSage` folder is located relative to that webroot folder. By default, the `CertSage` folder is located in the parent folder of the webroot folder where `certsage.php` is located. [Next page](https://community.letsencrypt.org/t/confused-about-how-to-create-auto-renew-for-ssl-cetificate/176416.md?page=2)