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:cloudrancho.kittenmcnuggets.com
I ran this command: replace cert
It produced this output:failed to connect to let’s encrypt, confirm domain is valid
My web server is (include version):synology, no website setup
The operating system my web server runs on is (include version):DSM6
My hosting provider, if applicable, is:not hosted, parked at namecheap
I can login to a root shell on my machine (yes or no, or I don’t know):don’t know
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot):?
I have ports 80 and 443 fwd’d to 5000/5001 in my router. (they are off now, I open them when I’m trying to get this to work)
with those items, I can log into my synology DSM just fine via any pc just fine with quickconnect turned off.
MXtools says my domain checks and email redirect policy are in place.
After some failed attempts I tried to generate the cert using my synology ddns (xxx.synology.me) and lets encrypt created the cert. my understanding is that since this is not a paid domain, the cert will not function the same with the ddns cert.
I have since tried to replace the ddns cert using the cloudrancho.kittenmcnuggets.com domain multiple times all failing. I have tried logged in locally, logged in remotely by accessing it with the cloudrancho.kittenmcnuggets.com link, I have tried installing the web package and setting up a virtual host (not sure if I completed that correctly), but all give the same error in the title.
I need another suggestion to start researching…