It looks like you're new here. If you want to get involved, click one of these buttons!
Sign In RegisterIt looks like you're new here. If you want to get involved, click one of these buttons!
cd
/usr/local/directadmin/scripts
./letsencrypt.sh
request vps.mydomain.com 4096
After executing the listed commands above with SSH I receive the following:
[root@vps scripts]# ./letsencrypt.sh request vps.mydomain.com 4096
Setting up certificate for a hostname: vps.mydomain.com
Getting challenge for vps.mydomain.com from acme-server...
Waiting for domain verification...
Challenge is valid.
Getting challenge for www.vps.mydomain.com from acme-server...
Error: http://www.vps.mydomain.com/.well-known/acme-challenge/letsencrypt_1498052888 is not reachable. Aborting the script.
dig output for www.vps.mydomain.com:
Please make sure /.well-known alias is setup in WWW server.
It seems that I have to make sure that the alias is setup in WWW server. I searched for information and followed the support guide on DirectAdmin's support forum:
https://help.directadmin.com/item.php?id=646
I was able to successfully execute the acme challenge test and view the 'text' message in my web browser Chrome.
I would like to know if anyone is experiencing similar problems while working within the Centos 6 and Direct Admin environment. I also have noticed that this 'alias error' is currently affecting the automatic license update of DirectAdmin. Now I have to manually update it before it expires a the end of the scheduled thirty day period.
I thank all of you for time and assistance.
Best regards,
mjflint
Comments
After searching out more information and receiving ideas from other administrators I was guided to the importance of checking the following file on my server:
/usr/local/directadmin/conf/ca.san_config
I was told that there were bad url references and this was causing the error. Therefore, I deleted all bad url reference and left my hostname domain vps.mydomain.com as the only reference. After executing the script above to renew the license everything worked flawlessly and I now have a secure SSL environment within DirectAdmin. I hope this information serves for anyone else that might run into this situation.
Best regards,
mjflint