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.
My domain is:cyndeerae.com
I ran this command: I am trying to get started with certbot
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:spectrum business
I can login to a root shell on my machine (yes or no, or I don't know):yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):no all done as ftp on filezilla
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Does that mean you have a hosting service that runs your Apache server?
Do you admin Apache yourself?
I ask because your IP address looks to be controlled by Ntirety Inc. Are they your hosting company by chance?
Your cyndeerae.com domain is using a cert right now issued by Sectigo for a domain exceptionalhealing.com. Is that your domain? How is that related to this one and why not just use a Sectigo cert like you did for that?
Certbot is only for cases where you're administrating the server yourself. It doesn't sound like you're doing that, but it's not clear to us what exactly you are doing. Most "shared hosting" where you just upload files would automatically handle getting a certificate and SSL as well. But the short of it is that if you're not administrating your web server yourself, you need to contact whomever is.
Let's Encrypt has never worked this way, and I'd say it's likely you misunderstood what they told you.
Can you link to any pages in their support site describing how to set up TLS, SSL, and/or a certificate?
Edit: and what makes you think certbot is the tool you need to use?
Edit 2: Perhaps a bit of history will help. In the past, getting a certificate was a largely manual process, in which you'd manually interact with a certificate authority, generally through some kind of web interface, and they'd eventually give you a set of certificate files. As I mentioned above, Let's Encrypt has never worked this way--it's designed from the ground up for automation. You'd use a piece of software (and certbot is one such piece of software, though not one that I recommend) to interact with the Let's Encrypt API, solve a challenge, and install the certificate. And you'd set up this software to run on a schedule, because the certificate is only valid for 90 days. Everything is intended to be handled automatically.
If Spectrum/Charter has set up their legacy (apparently it's only available for customers prior to 2020) web-hosting service with the expectation that you'll manually upload certificate files in SiteControl, Let's Encrypt just isn't going to be a good choice for you--either use a different CA, or use less user-hostile web hosting.
Strictly speaking it's possible to manually get a certificate by uploading the challenge file using FTP and then send the cert and private key to the hoster.. But as you've already mentioned I would not recommend this manual process as it would need to be repeated quite often.
Better to change to a hosting provider which simply offers Let's Encrypt free of charge in their product.
Sure, no worries. But perhaps look for a hosting service that allows you to focus on the content of your site and not all the technical bits. There are numerous such services.
You could keep Spectrum Business for the connectivity (your ISP) but somewhere else for your website.