letsencrypt https only works after extra tweaks
Posted: Thu Jan 18, 2018 9:48 am
I'm completely new to Linux but set up a VPS with the help of a friend who is considerably better than I am at this sort of stuff. Anyway, we had a lot of trouble with getting letsencrypt working properly, and he eventually figured how to do it. I was playing around a bit and managed to refine the process as much as I could, but I'm wondering if this is intentional on the part of Vesta or if something is being done wrong?
1. On Vesta CP log into user and create a new website called site.com
2. Either tick the letsencrypt support checkbox (and wait 5 min), or run the code after creation:
3. Run letsencrypt-auto, select the new website, choose reinstall certificate, and https redirection (this creates the -le-ssl.conf file, which https doesn't seem to work without)
4. Add the newly created file into vesta.conf
5. Restart apache
Anything less than this doesn't work with https, but it's a pain to do for every single created new website. Is there a way to automate or prevent it from being required?
Oh also just as a heads up, I use lastpass so usually pick long passwords, this forum complained that a 100 character password didn't match and 64 character password was too short.
1. On Vesta CP log into user and create a new website called site.com
2. Either tick the letsencrypt support checkbox (and wait 5 min), or run the code after creation:
Code: Select all
letsencrypt-vesta user site.com
Code: Select all
/usr/local/certbot/letsencrypt-auto
Code: Select all
nano /etc/apache2/conf.d/vesta.conf
Include /home/user/conf/web/site.com.apache2-le-ssl.conf
Anything less than this doesn't work with https, but it's a pain to do for every single created new website. Is there a way to automate or prevent it from being required?
Oh also just as a heads up, I use lastpass so usually pick long passwords, this forum complained that a 100 character password didn't match and 64 character password was too short.