I would like some help because is the first time I’m trying to get an SSL certificate. I just need to know how can I get the certificate.
I already talked with the hosting company - InMotion Hosting. They don’t “support Lets Encrypt” for shared servers. They informed me that I do have ssh access to my server and they will support on setting them up if I get the certificate from a third party.
In this situation I just need to get the certificate. What I have to do for that?
First, you’ll need to post your thread in the Help section. This isn’t an feature requests Further, you might want to take a look on https://certbot.eff.org, the home of Let’s Encrypt official client.
Next would be to fill in the following information (which you would have gotten if you posted in the Help section )
Please fill out the fields below so we can help you better.
My domain is:
I ran this command:
It produced this output:
My operating system is (include version):
My web server 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):
First, you'll need to post your thread in the Help section. This isn't an feature requests Further, you might want to take a look on https://certbot.eff.org3, the home of Let's Encrypt official client.
I moved the topic to the Help section and updated the title. Thanks.
Do you know if you have root access on the server? Is it a shared server with other customers, or a virtual server dedicated exclusively to you? Are you familiar with command line server administration at all?
If the answer to the first and last questions is “yes”, then please take a look over https://certbot.eff.org/ for information on installing Certbot on your server, to directly obtain and install the certificates there. We’re happy to help you with any problems you encounter in this process.
If the answer to these questions is “no”, the easiest option is probably a web-based client like https://zerossl.com/. This will let you get the certificate and its other associated files inside of your web browser, and you can then provide them to the hosting company.
One thing to bear in mind in this case is that the certificate will expire in 90 days and you’ll have to repeat the process (and again every 90 days thereafter). The certificates are always free of charge but you will have to get a new certificate periodically, which some people find annoying or may forget to do (resulting in visitors to their web sites getting an expired certificate error). That’s one reason that we recommend automation if possible, either by installing software like Certbot on the server or getting hosting companies to add official support for Let’s Encrypt and handle the process for their customers automatically.
Thank you all for your help. Please understand that is the first time when I’m using this website and I was not sure where I should post my thread.
Based on the information I received from inmotion:
I do have SSH Shell access;
I’m using a shared server with other customers;
Not an expert with command line server administration, but inmotion informed that they will support me if I get the certificate first;
I checked the website https://certbot.eff.org/ and I know that I’m using Apache on CentOS 6 and i got a file “certbot-auto”. Now I’m not sure what is my next step?
I assume you found the info about certbot-auto on the following page: Certbot
The next step would be to run certbot-auto as demonstrated on the above page.
Do note however, certbot-auto assumes you've got root access to your server, which is unlikely in a shared hosting environment. You might want to try the certonly option for certbot-auto in combination with thewebroot plugin for authentication. But I'm not sure it would run without root. If it doesn't, you can always use one of the Bash plugins from the list of 3rd party clients. Personally, I find acme.sh well documentated.
Unfortunately after having discussions with InMotion about this type of certificate, they told me that on a shared server can’t be installed this certificate only on VPS. Possible I must look for a different hosting company or another type of certificate.
you seem to be bouncing back and forwards on your facts for example:
They don't "support Lets Encrypt" for shared servers. They informed me that I do have ssh access to my server and they will support on setting them up if I get the certificate from a third party.
Hosting providers either let you install 3rd party certificates or they do not.
You have both CPANEL and SSH access which means you should be able to configure your web servers to support SSL.
@catalin-chitu, it seems like what the hosting company has told you is somewhat inconsistent, because first they suggested that if you get the cert yourself, you can use it with their service, and then later they apparently said this is not the case—I suppose that's what was confusing @ahaw021.
Sometimes what hosting companies tell users is different depending on the support person who answers, or depending on how the question was asked (for example "we don't support Let's Encrypt" might mean "we have never heard of Let's Encrypt", "we don't have an automated way for you to get and install LE certs", "we won't actively help you with this process", "you can get and install the cert yourself, but our infrastructure won't help you request it (or you're not allowed/able to install LE clients on our infrastructure so you have to run the client elsewhere)", "if you get the cert yourself, we can install it for you, but we can't help you get it", "as a matter of policy we don't want to install an LE cert for you", "as a matter of policy no third party certs are permitted on our service", among other possibilities!).
Anyway, I hope you're able to figure out a useful path forward. There is a pretty long list of hosting providers who support Let's Encrypt (in some way) at
As the list notes, it's also possible to use LE certificates on most VPS services if you have root access, whether or not the service provider has taken steps to actively support LE.