Perhaps this domain is at risk group and is blacklisted on the Let's Encrypt side

Help
1

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: ns18.iasolucions (Actually i have 3, ns16.iasolucions, ns17.iasolucions, ns18.iasolucions)

I ran this command: I used plesk interface

It produced this output: The error mesage was this
Could not issue an SSL/TLS certificate for ns18.iasolucions
Details
Could not issue a Let's Encrypt SSL/TLS certificate for ns18.iasolucions.

Perhaps this domain is at risk group and is blacklisted on the Let's Encrypt side.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order
Details:
Type: urn:ietf:params:acme:error:rejectedIdentifier
Status: 400
Detail: Invalid identifiers requested :: Cannot issue for "ns18.iasolucions": Domain name does not end with a valid public suffix (TLD)

My web server is (include version): Plesk Obsidian v18.0.76_build1800260406.11 os_Debian 12.0

The operating system my web server runs on is (include version): Debian 12.13

My hosting provider, if applicable, is: OVH

I can login to a root shell on my machine (yes or no, or I don't know): No

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Not sure what you mean

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Not sure

2

iasolutions doesn't exist in the root zone database Root Zone Database, can't be resolved and so can't be verified as globally unique.

Maybe you forgot a .com or .org at the end of the domain name.

3

.iasolucions is not a public TLD.

so you don't get a cert for that.

4

Sorry, my bad.

It is iasolucions.net (ns16.iasolucions.net, ns17.iasolucions.net, ns18.iasolucions.net)

I Totally missed that on the copy paste sorry

5

And what error do you get with these corrected hostnames? Or is it working now?

6

Could not issue an SSL/TLS certificate for ns18.iasolucions
Details
Could not issue a Let's Encrypt SSL/TLS certificate for ns18.iasolucions.

Perhaps this domain is at risk group and is blacklisted on the Let's Encrypt side.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order
Details:
Type: urn:ietf:params:acme:error:rejectedIdentifier
Status: 400
Detail: Invalid identifiers requested :: Cannot issue for "ns18.iasolucions": Domain name does not end with a valid public suffix (TLD)

7

You need to include the .net

Like:
ns18.iasolucions.net

If your plesk panel doesn't allow this, talk to their support. They might have a misconfiguration in their panel that doesn't add the root zone to the label that the customer owns.

8

I'm curious...
Since those are nameservers, why do they need a certificate?

9

they do have a web server running on them, so guess they are dual purpose:

10

Maybe they want to offer DoH or DoT?

11

There is an RFC for opportunistic DoT and DoQ to the authoritative nameservers (RFC 9539 - Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS), but I doubt operator of such service would be using Plesk dashboard to obtain certificates for it.