Faill generate certs

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. crt.sh | 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: skillfactory-12.ru

I ran this command: sudo certbot certonly --standalone -d $DOMAIN --preferred-challenges http --agree-tos -n -m $ALERTS_EMAIL --keep-until-expiring

It produced this output: An unexpected error occurred:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7eff08bb30a0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

My web server is (include version):

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

My hosting provider, if applicable, is: yandex.ru

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

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

2

I can't access your side: do you have any geoblocking or firewall?

3 Likes
3

Hi, I didn't quite understand the question.

for example, the nslookup command is successful, and the web interface is also available on port 8082

4

where you bought the domain from?

3 Likes
5

This means DNS resolving capability of your server is broken, you need to fix that.

4 Likes
6

I looked it up, you may want to use this plugin

2 Likes
7

ah I missed that error, now not sure if your server is acutally have network connection:

3 Likes
8

http://skillfactory-12.ru:8082/ui/login/

9

still you'd need dns plugin, unless you are exposing port 80/443
maybe try --standalone?

3 Likes
10

I'm trying to make ports 80/443 when creating a certificate, and the error attached above occurs.

11

Please refer to my post earlier:

4 Likes
12

your server failed to resolve domain, does your server get to outside intersnet?
ping google.com or something

3 Likes
13

image
image750×98 3.64 KB

14

If you need additional context: it could be that your /etc/resolv.conf is misconfigured or the nameserver configured there is unreachable. In case you use Docker—it also needs additional care with regards to DNS configuration, but my expertise with Docker is very limited.

4 Likes
15

I see you successfully got yourself a certificate :partying_face: crt.sh | 13693735232

4 Likes
16

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