Whenever I try to request a certificate from Let's Encrypt I get the following output:
Parsing account key... Parsing CSR... Registering account... Already registered! Verifying somedomain.info... mrforged.info verified! Verifying www.somedomain.com... www.mrforged.com verified! Verifying somedomain.com... mrforged.com verified! Verifying www.somedomain.info... www.mrforged.info verified! Verifying www.somedomain.net... Traceback (most recent call last): File "/usr/libexec/webmin/webmin/acme_tiny.py", line 203, in main(sys.argv[1:]) File "/usr/libexec/webmin/webmin/acme_tiny.py", line 199, in main signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca) File "/usr/libexec/webmin/webmin/acme_tiny.py", line 128, in get_crt wellknown_path, wellknown_url)) ValueError: Wrote file to /home/someuser/domains/somedomain.com/public_html/.well-known/acme-challenge/pv4y1NqqQKKMacTKkpB87us5dQ4aKYa-hQAQ2qC3Rus, but couldn't download http://www.somedomain.net/.well-known/acme-challenge/pv4y1NqqQKKMacTKkpB...
I have verified that all of the aliases point to the correct server, with and without the www and when I look in the web server's directory I see that the .well-known/acme-challenge folder has, indeed, been created. However, the directory is empty.
Your help is much appreciated.
Comments
Submitted by JamieCameron on Mon, 06/06/2016 - 22:40 Comment #1
Make sure that your system can access it's own websites - in some cases when the Virtualmin machine is behind a NAT gateway, it can't connect to its own external IP.
Submitted by DaveOverton on Wed, 06/08/2016 - 04:06 Pro Licensee Comment #2
I too have this error, and am trying to figure it out. 2 domains, on 2 different servers have the same error. One of them has wordpress, with wordfence, so anything is possible, but the other is a straight simple .html site, no .htaccess file or anything to interfere. I can open a file in that folder, using a browser or curl, and if I comment out the line that deletes the file its created properly, and I can open that file too.
Suggestions? This all worked on these 2 domains when I created them, just when it goes to renew things get strange.
Submitted by andreychek on Wed, 06/08/2016 - 08:25 Comment #3
Could you create the exact path and file name mentioned in the error message it gave you, and then share the URL to that file with us? We'd like to do some testing with that URL (and we'll provide you with a command that you can use to test it from your server as well).