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.
I ran this command: open the site on different computers
It produced this output: SSL certificate is invalid. On my computer, it's ok, no problems, but this is an internet shop. So, some people don't trust it and we are having more actions. Can you check please, what is a problem with certificate?
My web server is (include version):
The operating system my web server runs on is (include version):
I found that this is a Chrome feature called "Safety Tips" which was implemented last year. There are lots of (very technical) details about it available online.
I'm not sure whether this was triggered by the "edit distance of 1" rule (that means changing a single character in the domain name) or by the "skeleton similarity" rule (I don't know what that means and I think the Chrome developers made it up).
Anyway, this is NOT a problem with your site or certificate, nor is it related to the MITM interception certificate that the government of Kazakhstan has been testing. It is a problem about Chrome containing code that is inherently skeptical of this domain name, based on software rules that make Chrome think it's likely to be a fake site.
If that's wrong, it would need to be addressed by the Chrome developers... who have not necessarily come up with a way for web site administrators in Kazakhstan to easily offer them feedback about this kind of problem. Maybe we could help figure that out somehow even though it's not actually a Let's Encrypt issue.
Looking at this a little more closely, I think the Chrome warning is triggered when
a Chrome user has previously actively interacted with the other site (babyk.kz) to a certain extent (I think that's what "engaged domain" means, one that a user previously deliberately interacted with in the same browser), and
that same user then follows a link to the similarly-named site (baby1.kz).
I wasn't able to reproduce the exact behavior easily, but I can't really interact that much realistically with babyk.kz because I don't speak Kazakh, and I think there may be other conditions for the warning message to be displayed.
@Alisa I can see that your site is quite different from the other one in design and content and does not seem to be meant to trick visitors into thinking that they're using the other site. However, this warning is a behavior of the Chrome browser itself based on the similarity of the domain names of the two sites. I think Chrome is wrong to display this warning in this case, but Let's Encrypt has no power to affect that directly. If my interpretation is right, you will have to change your domain name (!), or get visitors to visit your site using a different browser (!), or contact the Chrome developers to get them to change the rules for when this warning is shown (!). I can try to help you with the last option if you want to do it, but I can't guarantee that the developers will care about this problem, or that they'll fix it very quickly if they do care.
I didn't expect this help! Thank you very very very much!
I will try to solve the problem because I really couldn't understand why it can be so, but now I see.
