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: vpn2.daltm.ru
I ran this command:certbot certonly -v -d vpn2.daltm.ru --standalone
It produced this output:
My web server is (include version):openconnect vpn server
The operating system my web server runs on is (include version): debian 12
My hosting provider, if applicable, is:
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, only cli
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.11.0
My problem below:
root@debian12:/home/user# certbot certonly -v -d vpn2.daltm.ru --standalone
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Requesting a certificate for vpn2.daltm.ru
Performing the following challenges:
http-01 challenge for vpn2.daltm.ru
Waiting for verification...
Challenge failed for domain vpn2.daltm.ru
http-01 challenge for vpn2.daltm.ru
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: vpn2.daltm.ru
Type: connection
Detail: 194.186.115.186: Fetching http://vpn2.daltm.ru/.well-known/acme-challenge/RJnDpZW9i_jt-eqLtucZ7SlyieQsXjxP7iGJeAxnvhI: Connection reset by peer
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Cleaning up challenges
Some challenges have failed.
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.