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:videogamemarkt.ru
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: insales.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):
you have created one new certificate ( https://check-your-website.server-daten.de/?q=videogamemarkt.ru#ct-logs ):
||CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
videogamemarkt.ru, www.videogamemarkt.ru - 2 entries
||duplicate nr. 1
So that part has worked.
But you don't use it. Instead, there is a wildcard certificate:
expires in 31 days *.myinsales.ru - 1 entry
So your nginx doesn't use the certificate.
PS: Does your hoster support own certificates? If you don't have root access, that may not work.
looks like he created new thread for this instead of reply on this tread. can you merge this thread into this?
Приватный ключ и цепочку сертификатов можете их предоставить. Мой домен videogamemarkt.ru
Google translation for record:
My hosting provider asks for a private key and a chain of certificates you can give them
You can provide a private key and certificate chain. My domain is videogamemarkt.ru
I’ll move this thread to help.
Здесь вы можете научиться их создавать.
Thanks @orangepizza - done.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.