We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
SSL renewal keeps resetting custom DocumentRoot (nginx+apache2) Topic is solved
SSL renewal keeps resetting custom DocumentRoot (nginx+apache2)
I have a server(Ubuntu 16.04 LTS) with VestaCP (0.9.8-23) and nginx+apache setup. I use laravel for my app and my DocumentRoot looks like this "/home/admin/web/domain.xx/pubcli_html/public" (in apache2 conf) and I use LetsEncrypt for SSL.
My problem is that when LetsEncrypts updates SSL cert it refreshes DocumentRoot in apache config for that domain to "/home/admin/web/domain.xx/pubcli_html". I googled before posting here and was unable to find a solution to my problem, so any help will be appreciated.
My problem is that when LetsEncrypts updates SSL cert it refreshes DocumentRoot in apache config for that domain to "/home/admin/web/domain.xx/pubcli_html". I googled before posting here and was unable to find a solution to my problem, so any help will be appreciated.
Re: SSL renewal keeps resetting custom DocumentRoot (nginx+apache2)
I think your best bet would be to create a new template for laravel sites, so that when the site is regenerated it will provide the correct path. Brief instructions:
Look in here:
/usr/local/vesta/data/templates/web/apache2/
Copy the default.tpl and default.stpl to laravel.tpl and laravel.stpl
Edit those files to have the correct path.
Back in the admin area, select that template for your laravel site.
Look in here:
/usr/local/vesta/data/templates/web/apache2/
Copy the default.tpl and default.stpl to laravel.tpl and laravel.stpl
Edit those files to have the correct path.
Back in the admin area, select that template for your laravel site.