This site can’t be reached

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:
https://srimuang.duckdns.org/
I ran this command:
add Proxy Hosts to the instance IP that already obtain SSL
It produced this output:

This site can’t be reached

ERR_CONNECTION_TIMED_OUT
My web server is (include version):

nginx proxy manager v2.9.18

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

debian 11 bulleye

My hosting provider, if applicable, is:
duckdns
I can login to a root shell on my machine (yes or no, or I don't know):
yes
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):

osiris@erazer ~ $ curl -LIv http://srimuang.duckdns.org/
*   Trying 182.232.222.54:80...

Well, HTTP on port 80 is also not responding. Doesn't seem to be a HTTPS/certificate/Let's Encrypt issue if you ask me. Is the IP address still correct in the DNS?

4 Likes

idk why DNS seems like not always update my public IP

That would explain why your site can't be reached - wrong/old IP.

2 Likes

That would be a DuckDNS thing. Maybe the application misbehaves, maybe it isn't run regularly, I dunno.

3 Likes