This Site cant be reached

Help
1

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:plastocards.com (addon domains niber.co.in
plasticcardmart.com
shreekalifestyle.com
srika.co.in
stiksnax.com)

I ran this command: all addon domains automatically have taken the certificate

It produced this output: once in a while we get this error ( this site can not be reached )

My web server is (include version):

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

My hosting provider, if applicable, is:mochahost

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

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

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

Screenshot_1
Screenshot_1833×630 57.7 KB

2

Everything seems to be working here. Also, the error you’re getting, “DNS_PROBE_FINISHED_NXDOMAIN” is a name server (DNS) issue, which has nothing to do with Let’s Encrypt or TLS or certificates.

By the way, speaking of DNS servers, there’s something weird in your NS records when I do a dig +trace ${hostname}:

shreekalifestyle.com.	14400	IN	A	204.93.167.45
shreekalifestyle.com.	86400	IN	NS	ns2.missing-nameserver.local.
shreekalifestyle.com.	86400	IN	NS	ns1.missing-nameserver.local.
;; Received 125 bytes from 204.93.157.119#53(ns56.mochahost.com) in 195 ms

I’m pretty sure a DNS server shouldn’t reply with those strange NS records…

3

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