SSL problem: Failed to request certificate

Hi guys,

I have install Centos7 & Webmin/Virtualmin
CentOS Linux 7.8.2003
Webmin version 1.942

One server (main hostname) gets SSL without any problem. Anyway, for another Virtual Server I can’t setup SSL. This is output

Requesting a certificate for domainname, www.domainname from Let’s Encrypt …
… request failed : Web-based validation failed : Failed to request certificate :
Traceback (most recent call last):
File “/usr/libexec/webmin/webmin/acme_tiny.py”, line 198, in
main(sys.argv[1:])
File “/usr/libexec/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/libexec/webmin/webmin/acme_tiny.py”, line 143, in get_crt
raise ValueError(“Wrote file to {0}, but couldn’t download {1}: {2}”.format(wellknown_path, wellknown_url, e))
ValueError: Wrote file to /home/user/public_html/.well-known/acme-challenge/gTCol2NPIQOSPcstDAk6ysEEbTsiyfytBmayhW8EbsU, but couldn’t download http://domainname/.well-known/acme-challenge/gTCol2NPIQOSPcstDAk6ysEEbTsiyfytBmayhW8EbsU: Error:
Url: http://domainname/.well-known/acme-challenge/gTCol2NPIQOSPcstDAk6ysEEbTsiyfytBmayhW8EbsU
Data: None
Response Code: None
Response: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)>
, DNS-based validation failed : Failed to request certificate :
usage: acme_tiny.py [-h] --account-key ACCOUNT_KEY --csr CSR --acme-dir
ACME_DIR [–quiet] [–disable-check]
[–directory-url DIRECTORY_URL] [–ca CA]
[–contact [CONTACT [CONTACT …]]]
acme_tiny.py: error: argument --acme-dir is required

This does not appear to be a valid URL, I wonder if you have entered an incorrect or malformed domain name at the time of creating the virtual server.

Could you check if you are able to visit the website associated with the domain via http?

1 Like

Thanks for try. URL was valid, and accessible via web browser. However, I was migrating from one server to another, and DNS propagation could mess up with let’s encrypt .

Today I finally manage to install certificate on master domain. Tomorrow I’ll do migration (site , one by one).

Thanks for answering. I didn’t sure what was the problem, but suggesting that DNS wasn’t clear in that time.

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