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. 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.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:inmotionhosting
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): CPanel
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): latest
I've been struggling to launch a website for my business.
I bought a domain from google and bought a basic plan from inmotionhosting
I pointed the domain to the nameservers of inmotionhosting
Turned out that the self assigned certificate that inmotionhosting uses is so unsecure that even my browser blocks my access to the editing environment
After searching a lot I found here and tried to run certbot to geenrate a certificate
but I get the error above, and I don't know what the problem is.
@Osiris as usual has likely pointed you down the right road, but we will happily do our best to answer any questions you may have and address any troubles you may encounter.
I will take a deeper look into things once I return from lunch.
Hmm, I can see it now too.. No, I guess it was issued between when I checked previously and now.. Also, my Chromium doesn't show the SCTs when I check the cert in the Developer Toolbar apparently..
It actually does. It seems @Hannah-N managed to get SSL working
I just went through a free basic SSL issuance. It generated one for me. Interesting is that it also tell me that because there's not a dedicated IP address, it's not seen as a secure website for the visitors.
This is true for many users who are using web browsers made since before about 2006 or 2010.
Some scanning tools and documentation from the 2010-or-so era prominently warn web site operators about this, because it might have seemed like a big deal then. Now probably 2% of Internet users, or fewer, are using such old obsolete browsers, so it's not a big deal today.
It's true that the web platform has been a moving target for a while; as you can see from the "caniuse" site (which addresses details about web technology compatibility), a lot of web developers and web site admins are preoccupied with the way that the technologies supported on the web have changed quickly over time. And there are also a number of different layers and steps to deal with, especially if you're acting as your own system administrator.
Congratulations on the progress you've made on your site so far!
Also, my Chromium doesn't show the SCTs when I check the cert in the Developer Toolbar apparently.. 
