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), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: Siteground
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): yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Good evening, I'm trying to install SSL certificates on my siteground site, but for some reason I get the following error:
No domains can be authorized
I recently changed the name of the servers and assigned the domain to another website. I would like to know if it is a DNS propagation problem, otherwise I would like to know how to solve this problem for my website.
I can see from the issued certificates, crt.sh | silleraviajera.com that you've been successful for about 4 years. I suspect the DNS Name Servers of SITEGROUND.NET have undergone some change recently.
Did you perhaps change the DNS service provider for silleraviajera.com? Because it looks like the .com. DNS zone still has an old (probably) DS RR set. But there is no corresponding DNSKEY in the silleraviajera.com. zone, making DNSSEC "bogus".
You should either fix DNSSEC entirely or remove the DS RR from the .com. zone to disable DNSSEC. The latter is usually done at the DNS registar level (which seems to be Tucows).
Yes i change the DNS service provider to Siteground And I would like to know if the error is that I have to wait for the propagation to finish to install the SSL.
Your site is hosted somewhere, i.e., the software that determines how your site looks, feels, works et c. This seems to be Siteground.
Your domain is hosted somewhere, i.e., your DNS service provider. This DNS service provider is the place where you can modify and add the DNS Resource Records (RRs) for your domain and, if you want, subdomains et c. This also seems to be Siteground.
Your domain is registered somewhere. This is the company that is able to tell the TLD registry (.com in your case) that your domain is actually registered and can tell the TLD which DNS nameservers should be used for your specific domain. It is also the company that is able to add and remove DNSSEC RRs (DS RR to be exact) in the .com. DNS zone, which is the RR which tells every DNS client that your domain has DNSSEC enabled. This seems to be "Tucows Domains Inc." according to the whois and rdap information for your domain.
In addition to the latter, when looking at the whois info for your domain, it might be that Siteground has some business relations with Tucows:
Registration Service Provider:
SiteGround Spain S.L., tucows@domains.siteground.com
+34.900838543
This company may be contacted for domain login/passwords,
DNS/Nameserver changes, and general domain support questions.
Looking at that email address.. Maybe Siteground simply "uses" Tucows as the registar under the hood without bothering you with it.
So probably best to ask Siteground to fix your DNSSEC. Perhaps they can fix it or perhaps they'll refer you to Tucows, I dunno.