.services: Domain name does not end with a valid public suffix (TLD)

Help
1

Domain name does not end with a valid public suffix (TLD) le

My domain is: enlightened.services
I ran this command:

It produced this output:

My web server is (include version): enlightened.services

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

My hosting provider, if applicable, is: Synology

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):

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

2

don't see same error from that string: are you sure you didn't made a typo in commend?

1 Like
3

image.png
image.png1920×1032 390 KB

Here is screenshot"Let's encrypt says domain suffix is not recognized.
See : www.enlightened.services

Greetings,

Herbrand Hofker

4

That's not what it says in Dutch at all?

6 Likes
5

Let's encrypt cannot validate this domain name. Please make sure port 80 of your Synology NAS and router is open for LE domain validation over the Internet
All other communication with LE will be over https to protect your Synology NAS.

that's just complaining about port 80 not open to internet:

4 Likes
6

Let's Debug confirms this: Let's Debug

However, from The Netherlands itself, I can connect to port 80 just fine.

Looks like some kind of geoblocking going on.

2 Likes
7

Yup. This test site can only connect from the Netherlands and Germany:

For information on geoblocking and why Let's Encrypt needs to check from many places around the world:

4 Likes
8

I don't think the ISP Freedom Internet itself has geoblocking.. (Can't find it in their management panel.) So it must be some on-premise device doing the blocking.

1 Like