I am waiting a lot of time for setting up SSL, my provider cannot do anything

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:

I ran this command:

It produced this output: i'm waiting 4 days and Beget.com cannot set up SSL to my websites, the all time try to reset and said wait-wait-wait. Please help me.

My web server is (include version): beget.com

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

My hosting provider, if applicable, is: beget.com

I can login to a root shell on my machine (yes or no, or I don't know): i do not know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): wordpress

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

it looks like this domain is not like the others, as it's redirecting to https regardless of what you ask for (and there is nobody listening on https).

$ podman run -i docker.io/certbot/certbot certonly --standalone --dry-run -d www.sk-dream.ru,www.ramenskoe.sk-dream.ru,www.domodedovo.sk-dream.ru,www.voskresensk.sk-dream.ru,www.egoryevsk.sk-dream.ru,www.kolomna.sk-dream.ru,www.ryazan.sk-dream.ru
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Enter email address (used for urgent renewal and security notices)
 (Enter 'c' to cancel): nobody@example.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf. You must
agree in order to register with the ACME server. Do you agree?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: y
Account registered.
Simulating a certificate request for www.sk-dream.ru and 6 more domains

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
  Domain: www.ramenskoe.sk-dream.ru
  Type:   connection
  Detail: Fetching https://www.ramenskoe.sk-dream.ru/.well-known/acme-challenge/BjUvwcZ4Do_ljj3y60gUxzH18uaH-C6tqp8lhu1wGD8: Connection refused

  Domain: www.ryazan.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://ryazan.sk-dream.ru/.well-known/acme-challenge/2kzkDH6MgYmTXliFAFqZBFBcr6GUGSFWsehx2eydSiA: 404

  Domain: www.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://sk-dream.ru/.well-known/acme-challenge/Z6AcQQ6xuvl7HBaRgG3MOod3Vx8AIBn21el0_DC2U3I: 404

  Domain: www.voskresensk.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://voskresensk.sk-dream.ru/.well-known/acme-challenge/X9tFslwuMsP2R38GbhCSmSi3X0R-NVQKVLrcxIDmwBQ: 404

  Domain: www.domodedovo.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://domodedovo.sk-dream.ru/.well-known/acme-challenge/SFTbGGPXHHD7tO7pNgexZCjNyRMrgjF0AVMg-1_aU-U: 404

  Domain: www.egoryevsk.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://egoryevsk.sk-dream.ru/.well-known/acme-challenge/-KOiERLBvNR2THyy93BOyIRD8Bmnh9BQ7GkWLisa6Pk: 404

  Domain: www.kolomna.sk-dream.ru
  Type:   unauthorized
  Detail: Invalid response from http://kolomna.sk-dream.ru/.well-known/acme-challenge/NGRA-yATbG07SN0oQN0vAyZlljsLHfS4604bX2_uU00: 404

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.

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.

What we have to do to improve it?

First of all you have to understand why and how its configuration differ from all other domains.

You probably have to read your nginx config files, if you have access to them


Possibly switch provider.

1 Like

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