Do you have a test.txt file in the acme-challenge folder?
If so, it can only be reached via redirection (not best practice - as that requires working HTTPS to complete):
telnet five.epicollect.net 80
GET /.well-known/acme-challenge/test.txt HTTP/1.1
HTTP/1.1 301 Moved Permanently
Date: Wed, 14 Jun 2017 22:55:22 GMT
Server: Apache/2.4.18 (Ubuntu)
Content-Type: text/html; charset=iso-8859-1
Um, I don’t quite understand your deployment setup. Are you still supplying -w /var/www/html_prod/shared/public/?
If you run echo "This also works" > /var/www/html_prod/shared/public/.well-known/acme-challenge/test2.txt, will that cause there to be a http://fi–ec5dev3.dide.ic.ac.uk/.well-known/acme-challenge/test2.txt file?
I am definitely an idiot, /shared/ is the wrong folder, thanks for spotting it.
I have just run sudo certbot certonly --webroot -w /var/www/html_prod/current/public/ -d five.epicollect.net -d fi--ec5dev3.dide.ic.ac.uk pointing /current/ and bingo:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for five.epicollect.net
http-01 challenge for fi--ec5dev3.dide.ic.ac.uk
Using the webroot path /var/www/html_prod/current/public for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Unable to clean up challenge directory /var/www/html_prod/current/public/.well-known/acme-challenge
- Congratulations! Your certificate and chain have been saved at
/etc/letsencrypt/live/five.epicollect.net/fullchain.pem. Your cert
will expire on 2017-09-12. To obtain a new or tweaked version of
this certificate in the future, simply run certbot again. To
non-interactively renew *all* of your certificates, run "certbot
- If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
Donating to EFF: https://eff.org/donate-le
I will go ahead with the https setup and report back if I have any more issues