Obtaining a new certificate An unexpected error occurred: > The request message was malformed :: Error creating new authz :: DNS name does not have enough labels > Please see the logfiles in /var/log/letsencrypt for more details. >
IMPORTANT NOTES:
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
INFO:bench.utils:sudo service nginx start
There was a problem trying to setup SSL for your site
I have a valid domain associated with the site and working…
why isn’t it working
You need to rename your site “foodthink” to as example “foodthink.com” using mv sites/foothink/ sites/foothink.com/
and set nginx configuration to multitenant mode sudo bench config dns_multitenant on sudo bench setup nginx sudo service nginx restart
and then sudo bench setup lets-encrypt foodthink.com bench use foodthink.com
then did sudo bench setup lets-encrypt erp.thinkfoodco.com
and got the following output
Running this will stop the nginx service temporarily causing your sites to go offline
Do you want to continue? [y/N]: y
INFO:bench.utils:sudo service nginx stop
INFO:bench.utils:/opt/certbot-auto --config /etc/letsencrypt/configs/erp.thinkfoodco.com.cfg certonly
The standalone specific supported challenges flag is deprecated. Please use the --preferred-challenges flag instead.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for erp.thinkfoodco.com
Waiting for verification…
Cleaning up challenges
IMPORTANT NOTES:
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/erp.thinkfoodco.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/erp.thinkfoodco.com/privkey.pem
Your cert will expire on 2018-02-11. To obtain a new or tweaked
version of this certificate in the future, simply run certbot-auto
again. To non-interactively renew all of your certificates, run
“certbot-auto renew”
If you like Certbot, please consider supporting our work by: