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

Help
1

sudo certbot --nginx

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.

1: www.78.24.219.199

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): www.78.24.219.199.ru
** Error - Invalid selection **
Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.

1: www.78.24.219.199

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Requesting a certificate for www.78.24.219.199
An unexpected error occurred:
Error creating new order :: Cannot issue for "www.78.24.219.199": Domain name does not end with a valid public suffix (TLD)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

2

You can only get Let's Encrypt certs for domain names that exist in the public DNS system. Once acquired they can be used on private servers. But, the control of the domain name occurs in the public internet.

8 Likes
4

Hi @goLEXYgo, and welcome to the LE community forum :slight_smile:

You need a working web site before you can secure it using HTTP-01 authentication.
How can anyone on the Internet reach "http://www.78.24.219.199/"?

Additionally, as already mentioned (by @MikeMcQ), LE won't provide a cert for "http://78.24.219.199/".

7 Likes
5

Hello!
I have a domain (www.alexeymirniy.ru) which is linked to this IP (78.24.219.199).
Maybe the problem is in the nginx settings?

6

Yes.

Make sure that the Internet can reach "http://www.alexeymirniy.ru/" before you continue.
[not via the "default" nginx vhost]

8 Likes
7

remove nginx
remove certbot
install nginx
install certbot

Works!

I think the problem is here:
/var/www/78.24.219.199/html - Wrong
/var/www/alexeymirniy.ru/html - Right

2 Likes
8

I don't think removing and reinstalling certbot was ever part of the problem.
And you might have been able to reconfigure nginx to do what it is doing now.
But I am glad that you found a solution.
:slight_smile:

8 Likes
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.