Failure when I request SSL Certificate for autoconfig

Each time I add a new domain to my Virtualmin server I get a failure error. Why is that happening and what can I do to resolve it?

Here is one that I just added and this is the error I’m receiving.

Requesting a certificate for dlkonlinelearning.com, www.dlkonlinelearning.com, mail.dlkonlinelearning.com, admin.dlkonlinelearning.com, webmail.dlkonlinelearning.com, autoconfig.dlkonlinelearning.com, autodiscover.dlkonlinelearning.com from Let’s Encrypt …
… request failed : Web-based validation failed : Failed to request certificate :

Traceback (most recent call last):
File “/usr/share/webmin/webmin/acme_tiny.py”, line 198, in
main(sys.argv[1:])
File “/usr/share/webmin/webmin/acme_tiny.py”, line 194, in main
signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca, disable_check=args.disable_check, directory_url=args.directory_url, contact=args.contact)
File “/usr/share/webmin/webmin/acme_tiny.py”, line 149, in get_crt
raise ValueError(“Challenge did not pass for {0}: {1}”.format(domain, authorization))
ValueError: Challenge did not pass for autoconfig.dlkonlinelearning.com: {‘identifier’: {‘type’: ‘dns’, ‘value’: ‘autoconfig.dlkonlinelearning.com’}, ‘status’: ‘invalid’, ‘expires’: ‘2020-08-29T15:55:57Z’, ‘challenges’: [{‘type’: ‘http-01’, ‘status’: ‘invalid’, ‘error’: {‘type’: ‘urn:ietf:params:acme:error:unauthorized’, ‘detail’: ‘Invalid response from http://autoconfig.dlkonlinelearning.com/.well-known/acme-challenge/XCaI4TvyhKndOJSmBOQf2IAPsLUN_B0HhTeivhHWTGk [184.90.94.33]: “\n\n404 Not Found\n\n

Not Found

\n<p”’, ‘status’: 403}, ‘url’: ‘https://acme-v02.api.letsencrypt.org/acme/chall-v3/6704986210/ou3LWA’, ‘token’: ‘XCaI4TvyhKndOJSmBOQf2IAPsLUN_B0HhTeivhHWTGk’, ‘validationRecord’: [{‘url’: ‘http://autoconfig.dlkonlinelearning.com/.well-known/acme-challenge/XCaI4TvyhKndOJSmBOQf2IAPsLUN_B0HhTeivhHWTGk’, ‘hostname’: ‘autoconfig.dlkonlinelearning.com’, ‘port’: ‘80’, ‘addressesResolved’: [‘184.90.94.33’], ‘addressUsed’: ‘184.90.94.33’}]}]}

, DNS-based validation failed : Neither DNS zone dlkonlinelearning.com or any of its sub-domains exist on this system

The SSL certificate request is failing when it does not find the subdomain autoconfig. Create the subdomain in the control panel of your service provider and point it to the IP address of the Virtualmin server. While you are at it, check to see if you have created DNS records for all the other domains and subdomains that you are requesting a certificate for.

If you wait for the DNS records pertaining to the new subdomain to propagate and then apply to SSL certs again, it should work.

Addendum: alternatively, you could request a cert for all the domains and subdomains except autoconfig and autodiscover

This isn’t a subdomain, it’s a domain that I’ve created using Virtualmin. And this is on a server here at my home. I’m not using a hosting provider. I planned on using “Let’s Encrypt” because it was free and I’m just trying things out. Maybe I need to actually buy an SSL certificate if I’m going to keep this domain. Everything works when I use https, but it still tells me it’s insecure.

From what you had originally posted, I see you have created one top level domain and several subdomains in Virtualmin. I leave it to you to Google the distinction between domain and subdomain.

You are using a service provider (that is the term I had used in my previous message) which, I gather from the ns records of your domain, is Hover. If you read my earlier message in light of this, you will create the subdomain autoconfig and, after you have waited for the new dns to propagate, apply for a SSL cert and it just might work. Or you could exclude the autoconfig and autodiscover subdomains when requesting a SSL cert, as I had also suggested in my earlier message, and that should work too.

Addendum: you had moved /home to a custom location, I recall from an earlier interaction you had on this forum. You should also check if it is this that is jamming the works.

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