Certbot failed to authenticate some domains

[Tigeralhimik]

Hi!
My domain is:

Разработка мобильных приложений

I ran this command:
sudo certbot certonly --webroot -w /opt/node/adonisjs/sosedy/public/ -d http://sosedi.appsofter.ru

It produced this output:
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: sosedi.appsofter.ru
Type: unauthorized
Detail: 2a03:6f00:6:1::b972:f7e8: Invalid response from https://sosedi.appsofter.ru/.well-known/acme-challenge/zx_U8Jqotwf188m9GL0bLKV3RDx3QOUfo6r8vBXI4e8: 404
My web server is (include version):AdonisJS

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

My hosting provider, if applicable, is:
Self-hosted server

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

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

[MikeMcQ]

@Tigeralhimik

I ran this command:
sudo certbot certonly --webroot -w /opt/node/adonisjs/sosedy/public/ -d http://sosedi.appsofter.ru

Detail: 2a03:6f00:6:1::b972:f7e8: Invalid response from https://sosedi.appsofter.ru/.well-known/acme-challenge/zx_U8Jqotwf188m9GL0bLKV3RDx3QOUfo6r8vBXI4e8: 404

My web server is (include version):AdonisJS

An nginx server is responding to HTTP requests to your domain. Is that -w path the root folder in the nginx server block? Because you mention an AdonisJS server too but that does not look like the one responding to HTTP (see below)

curl -I6 http://sosedi.appsofter.ru/.well-known/acme-challenge/Test404
HTTP/1.1 301 Moved Permanently
Server: nginx/1.24.0
Location: https://sosedi.appsofter.ru/.well-known/acme-challenge/Test404

curl -I6 https://sosedi.appsofter.ru/.well-known/acme-challenge/Test404
HTTP/2 404
server: nginx/1.24.0

curl -I4 http://sosedi.appsofter.ru
curl: (7) Failed to connect to sosedi.appsofter.ru port 80 after 109 ms: 
Connection refused

Also, any request to your IPv4 address fails to connect. That will not prevent you from getting a Let's Encrypt cert but it will cause problems for people trying to use IPv4. Check the DNS A record IP address.

[Tigeralhimik]

OK. Thanks