Vesta Control Panel - Forum

Username shortening is not the way to go in case of usernames like: johnnydoesgood johnnydoesverygood If usernames will be shortened to 8 (thus resulting name will be: johnnydo) it will cause conflicts in database creation: johnnydoesgood creates dbuser "johnnydo_mydb" what will be successful and jo...

Unfortunately I now got stuck with a different issue, namely the domain foo.bar.com requires the same certificate as bar.com what is already installed. To not go off-topic here I started a new topic what is treating this issue. Please have a look: https://forum.vestacp.com/viewtopic.php?f=10&t=18883

Hello is it possible to reuse an SSL certificate on different domain (what the user owns)? Scenario After setting up the domain example.com it seems necessary to set up subdomain as well e.g. subdomain.example.com. During the setup of the root domain (example.com) you've already created and linked a...

Can you check if foo.bar.com have apropiate vhost ? I actually did check the vhost in the /home/<user>/conf/web directory and it seemed to be there. However what I didn't realize is that it wasn't loaded, or at least not the SSL config. Yes I should've noted that I use a special nginx/php-fpm confi...

To reproduce consider the following setup: Install VestaCP without DNS support Create the initial first low level user, so besides your admin user what comes with the installation add an new user let's call the user example . Add a website for the example user for this example, example.com would be ...

usr999 wrote: ↑

Thu Jun 21, 2018 11:31 am

Try in /usr/local/vesta/data/templates/web/php-fpm/

This directory is for PHP-FPM configs not for NGINX configs.

This is the directory the OP is looking for:

At the package add/edit form in the shown for the admin user only. There are one or actually two settings which confuse me or vaguely require me to make assumptions. I'm talking about the Quota and Bandwidth fields and to be more specific the text what is behind it between parenthesis " in megabytes...

You have two ways to do this: 1) via web... SERVER -> configure -> Vesta SSL 2) vesta-nginx -> /usr/local/vesta/nginx/conf/nginx.conf and add path to your cettificate: ssl_certificate /home/admin/conf/web/ssl.domain.ru.pem; ssl_certificate_key /home/admin/conf/web/ssl.domain.ru.key; I would like to...

Don't forget to setup the right file permissions:

Same thing happen for me. Did anyone found a solution to this problem?