Vesta Control Panel - Forum

I think what you are looking for is

/etc/httpd/conf.d/phpMyAdmin.conf

I'm a little confused abut how VestaCP handles php.

I was under the impression that php-fpm was being used and I can see php-fpm running as a process.

That said phpinfo has Apache 2.0 Handler as the API.

Am I misunderstanding something basic or is there something I need to change?

CentOS 7.2 -- Digital Ocean After that I didn't change anything -- just did a default install of VestaCP 0.9.8-16 I actually am likely to abandon the use of a panel at this point and just configure everything myself. I am not selling hosting and the panel was just for personal use but I am having wa...

Yes it is possible -- I've seen ISPs do it using a user.ini file which is a user specific php.ini -- I've never done it myself nor do I know anything about how to configure that but it is possible.

1) Buy a SSL certificate -- I'm paying under $20 for 3 years so no point in messing around trying to get free options 2) Install the certificate using VestaCP -- basically you just copy and paste some files that the SSL issuer e-mails you plus the key that VestaCP generated into the appropriate boxe...

It violates most residential ISP terms of service to run a webserver from home -- at least in North America. Also again depending on your location the performance of a residential ISP connection is just not sufficient. Even people who have fast connections tend to only have a fast downstream with a ...

I've been working with the config file. You should use jail.local rather than jail.config. I've come to the conclusion that most of the pattern detections are wrong and by replacing them I've been able to get the mail stuff to detect some but not all of the attempted logins. The problem with doing t...

I haven't changed any settings in VestaCP but the VestaCP logfile /var/log/vesta/auth.log is recording failed attempts but not dates or times. This causes issues with Fail2Ban

Any suggestions?

You need to copy the certs that you installed to replace the self-signed certs in /usr/local/vesta/ssl then restart the Vesta service. I had the same issue a few days ago -- see here for topic https://forum.vestacp.com/viewtopic.php?f=10&t=13076 Basically I started by going to /usr/local/vesta/ssl a...

I know it is doable -- but my question is does VestaCP automatically handle setting up SNI if you add a second site with SSL or does one have to do it manually?