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.
Can't make domains to work from public_shtml directory
Can't make domains to work from public_shtml directory
Hello.
I use Vesta panel with the following configuration:
Debian 9.9 and nginx + php-fpm
And I have a problem when I'm adding a new domain.
All my sites will be using https protocol, so when adding a domain for the SSL directory, I select the public_shtml directory and set the checkbox for Lets Encrypt Support.
Templates for Web Template (NGINX) and Backend Template (PHP-FPM) I leave as default.
After adding new domain, the SSL directory spontaneously changes to public_html, I change it back to public_shtml and save it again. I check again, the SSL directory is left public_shtml, as I chose.
Then I go to the site let's say https://mysite.com and I see that the index page is loaded from the public_html folder, not the public_shtml, as indicated in the Vesta panel.
I checked this by changing the h1 header from mysite.com to https://mysite.com in default index.html file for public_shtml folder what was generated by Vesta.
Then I check the nginx config for my domain mysite.com.nginx.ssl.conf, and the root directory for the domain is correct: root /home/my-user/web/mysite.com/public_shtml;
I decided to reboot nginx, than the server completely, also did a rebuild web for the user under which I added domains, but nothing helped.
If I do redirect from http to https, then I’ll see in the browser:
This page isn’t working right mysite.com redirected you too many times.
ERR_TOO_MANY_REDIRECTS
What could be the problem?
I would be very grateful for the advice.
I use Vesta panel with the following configuration:
Debian 9.9 and nginx + php-fpm
And I have a problem when I'm adding a new domain.
All my sites will be using https protocol, so when adding a domain for the SSL directory, I select the public_shtml directory and set the checkbox for Lets Encrypt Support.
Templates for Web Template (NGINX) and Backend Template (PHP-FPM) I leave as default.
After adding new domain, the SSL directory spontaneously changes to public_html, I change it back to public_shtml and save it again. I check again, the SSL directory is left public_shtml, as I chose.
Then I go to the site let's say https://mysite.com and I see that the index page is loaded from the public_html folder, not the public_shtml, as indicated in the Vesta panel.
I checked this by changing the h1 header from mysite.com to https://mysite.com in default index.html file for public_shtml folder what was generated by Vesta.
Then I check the nginx config for my domain mysite.com.nginx.ssl.conf, and the root directory for the domain is correct: root /home/my-user/web/mysite.com/public_shtml;
I decided to reboot nginx, than the server completely, also did a rebuild web for the user under which I added domains, but nothing helped.
If I do redirect from http to https, then I’ll see in the browser:
This page isn’t working right mysite.com redirected you too many times.
ERR_TOO_MANY_REDIRECTS
What could be the problem?
I would be very grateful for the advice.