Vesta Control Panel - Forum

Given that Ubuntu 16.04/18.04 uses systemd, you can also overrule the environment by creating a service config: systemctl edit vesta Add to the new config file: [Service] Environment="LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl.so.4.4.0" Don't forget to update the daemon: systemctl daemon-reload An...

I found that the problem get's resolved with installing libcurl3/bionic:

sudo apt install libcurl3/bionic

See https://stackoverflow.com/questions/506 ... -not-found

It looks like the problem is that the permissions on the public_html (public_shtml) directories are too tight. When VestaCP build the directories it assigns 751 permissions (drwxr-x--x). This causes NGINX to log the 13: Permissions denied error. When the permissions for both directories are changed ...

One step further. Reinstallation finished and button has reappeared (did not run installation script as root before). But clicking the Sitebuilder is now resulting in the following error messages and now continuation on the url https://<server>:8083/siteprobuilder/?domain=<domain>: Notice: Undefined...

After upgrading VestaCP to R17 from 16, the Site Builder button in the web panel has disappeared. It looks like all the Site Builder functionality is gone. I tried reinstalling with the instructions from Site.pro but to no effect.

Has this functionality been tested on R17?

You should have a look which process take most of the memory. For example use the following command to see how much MB each process uses:

I'm guessing that Let's Encrypt does not work if VestaCP is not installed fresh (i.e. was updated through GUI last 2 releases). Can you outline the steps which are required to upgrade an existing VestaCP to support Let's Encrypt?

I've tried to install VestaCP on a fresh Ubuntu 14.04 server (fully updated) using nginx+php-fpm as webserver. But unfortunately the installation procedure grinds to a halt mid-way with the message: start: Unknown job: php5-fpm Error: php-fpm start failed I used the following installation parameters...

Unfortunately there is a bug in the IP address field, it only accepts a plain IP address without a /. Currently the only option to circumvent this is, is to edit the firewalls through the cli. In the file /usr/local/vesta/data/firewall/rules.conf you can add CIDR format IP's (be careful and double c...

I'm having the same issue. My setup is Nginx only (no Apache2) with php-fpm on VestaCP Version:0.9.8 (amd64) Release:16. The result is like yours that template changes are not taken at first but require another trigger (i.e. change in web server setup like adding certificate or changing to different...