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:
I ran this command:
It produced this output:
My web server is (include version): Apache Tomcat
The operating system my web server runs on is (include version): Eclipse Java EE
My hosting provider, if applicable, is:
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): cerbot is windows beta version.
There were frequent requests and refreshes because I didn’t know what was registered on the router.
Previously, certbot was forcibly issued due to a router problem. I have also registered the key and cert files.
ddns address used by asuscomm.org
duckdns have no problems and problems with dnsomatic.
because don’t know the cause of the problem. please help me
asus router(stable asus firmware and merlin firmware) → let’s encrypt added. →
duckdns add is ok (token, ddns), dnsomatic is status failed. → certbot key, cert file add router is fail. → refresh → failed.
FTP client → connect refused.
HTTP Server → connected failed.