Basically you install letsencrypt and run the command that starts a step by step prompt to guide you through various options, and generates the files as below. But it will stop the prompt if the configuration fails to meet the requirements. I know I could go search for another package but at least this one streamlines the set up and options for you.
sudo apt-get install python-letsencrypt-apache sudo letsencrypt --apache -d skylinedev.net -d www.skylinedev.net :/var/www/SkylineDevelopment$ ls /etc/letsencrypt/ accounts archive csr keys live options-ssl-apache.conf renewal :/var/www/SkylineDevelopment$ ls /etc/letsencrypt/live/ :/var/www/SkylineDevelopment$ sudo ls /etc/letsencrypt/live/skylinedev.net cert.pem chain.pem fullchain.pem privkey.pem :/var/www/SkylineDevelopment$ sudo ls /etc/letsencrypt/keys/ 0000_key-letsencrypt.pem On Monday, January 2, 2017 at 5:50:41 PM UTC-7, Graham Dumpleton wrote: > > You do not have to use the Apache configuration snippets that letsencrypt > generates. Instead use them as a guide only as to what you should add > manually as not everything they do may be appropriate for your setup. > > What was in the files that letsencrypt generated? > > Graham > > On 3 Jan 2017, at 11:48 AM, Jaqen Nki <[email protected] <javascript:>> > wrote: > > ok never mind i got a better working www redirect, since rewrite is more > convoluted and not recommended. I added this virtual host on top of my > original virtual host: > > # sld.conf > > <VirtualHost *:80> > ServerName skylinedev.net > Redirect permanent / http://www.skylinedev.net/ > </VirtualHost> > > <VirtualHost *:80> > ServerName skylinedev.net > WSGIScript ETC... > </VirtualHost> > > Now the issue with letsencrypt command is that you can only have one > virtual host per conf file for setting up SSL: > > sudo letsencrypt --apache -d skylinedev.net -d www.skylinedev.net > > I tried to put each virtual host block in its own conf file and > > sudo a2ensite www-sld.conf > sudo a2ensite ssl-sld.conf > > But then the www redirect stopped working. Is there something simple I'm > missing, in order to get these separate vhost files to apply to the same > application? Personally I would rather put both :80 vhosts and :443 > vhost in the same file but LE obviously has technical reasons for keeping > them separate. > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at https://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
