Error crm bitrix centos7

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. https://crt.sh/?q=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: you can see in image top Error: https://yadi.sk/i/ozrmMkzAfCuDZQ

I ran this command: /home/letsencrypt/letsencrypt-auto certonly --standalone -d crm.finbh.ru

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know): Y

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

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

Hi @finbh

your https answers. Your http not ( https://check-your-website.server-daten.de/?q=crm.finbh.ru ):

Domainname Http-Status redirect Sec. G
http://crm.finbh.ru/
5.101.206.82 -14 10.030 T
Timeout - The operation has timed out
https://crm.finbh.ru/
5.101.206.82 200 0.630 N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
http://crm.finbh.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
5.101.206.82 -14 10.033 T
Timeout - The operation has timed out

Ok, you use --standalone. But is there a blocking firewall?

Perhaps add a http vHost, then it's easier to debug your configuration.

1 Like

after what time you can re-order the certificate made a mistake in the configuration process

Normally after one hour if the certificate was not issued due to a validation error, or after 7 days if too many certificates were issued.

What's the output of your command?

Rechecking your domain there is a timeout checking http + /.well-known/acme-challenge. But that's normal if you use --standalone.

So we can't see why the command doesn't work.

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