To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
Assuming you have checked the obvious:
You have a DNS A/AAAA record for the domain?
and that you can place a file in your domain/.well-known and can access it on the web.
LetsEncript looks for your domain on the internet. - a A/AAAA record pointing to where your domain is. If LE can find it then it places a file in the .well-known directory (it does this to validate your domain) - called a challenge test. If it can do that it continues to supply/write a certificate.
So if you cannot put a simple file in there and access it then LE can’t.
As I seem to be able to get to your unsecured site. I must assume that the A record exists and is correct.
This looks odd why try to request certs on ports 10000 and 20000 ?
maybe the OP has set some .htaccess rules so the .well-known directory can not be reached, as the last update that worked was Tuesday, 14 November 2023 at 11:41:25 so something has changed since then
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
DNS-based validation failed :
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Renewing an existing certificate
Reusing existing private key from /etc/letsencrypt/live/tagtoconnect.com/privkey.pem.
Performing the following challenges:
dns-01 challenge for admin.tagtoconnect.com
dns-01 challenge for mail.tagtoconnect.com
dns-01 challenge for tagtoconnect.com
dns-01 challenge for webmail.tagtoconnect.com
dns-01 challenge for www.tagtoconnect.com
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Waiting for verification…
Challenge failed for domain admin.tagtoconnect.com
Challenge failed for domain mail.tagtoconnect.com
Challenge failed for domain tagtoconnect.com
Challenge failed for domain webmail.tagtoconnect.com
Challenge failed for domain www.tagtoconnect.com
dns-01 challenge for admin.tagtoconnect.com
dns-01 challenge for mail.tagtoconnect.com
dns-01 challenge for tagtoconnect.com
dns-01 challenge for webmail.tagtoconnect.com
dns-01 challenge for www.tagtoconnect.com
Cleaning up challenges
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Some challenges have failed.
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: admin.tagtoconnect.com
Type: unauthorized
Detail: No TXT record found at
_acme-challenge.admin.tagtoconnect.com
Domain: tagtoconnect.com
Type: unauthorized
Detail: No TXT record found at _acme-challenge.tagtoconnect.com
Domain: webmail.tagtoconnect.com
Type: unauthorized
Detail: No TXT record found at
_acme-challenge.webmail.tagtoconnect.com
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
The following errors were reported by the server:
Domain: mail.tagtoconnect.com
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.mail.tagtoconnect.com - check that a DNS record
exists for this domain
Domain: www.tagtoconnect.com
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.www.tagtoconnect.com - check that a DNS record
exists for this domain
put a file in the .well-known directory and try to navigate to it
so create ./well-known/test.html and put
<html>
<p> hello world</p>
</html>
in it then navigate to http://tagtoconnect.com/.well-known/test.html, if you see ‘hello world’ in your browser LE should renew if not you still have a problem with ‘.well-known’ not being accessible , may check there are no directives in the apache config file for the domain & also try restarting apache
This shouldn’t happen. The redirects that Virtualmin sets up exclude .well-known. So…I dunno what’s happening here. What’s the actual Apache VirtualHost configuration for this domain? (Show us the actual config file for this VirtualHost, not a GUI view.)
Note this is unrelated to the others ones. The “unauthorized” ones are a different problem, unrelated to Virtualmin.
