• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

no vhost.conf files?

N_Vas

Basic Pleskian
I originally posted this on the CloudLinux forums as I thought maybe it was related to that, but one of the CloudLinux administrators referred me back here after checking his own test Plesk server and seeing the same thing (well, after not seeing vhost.conf files either)

We're running Plesk 12 with CloudLinux on CentOS 6.6.


There is a httpd.conf file at/var/www/vhosts/system/DOMAIN.COM/conf/httpd.conf, however the very first lines of this file state that this file is auto-generated and not to make changes to it:


#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
#IF YOU REQUIRE TO APPLY CUSTOM MODIFICATIONS, PERFORM THEM IN THE FOLLOWING FILES:
#/var/www/vhosts/system/DOMAIN.COM/conf/vhost.conf
#/var/www/vhosts/system/DOMAIN.COM/conf/vhost_ssl.conf


(and there are settings after these commented lines like for Virtual Host IP, Server Name, Document Root, etc... it's a populated config file)


However when I look for/var/www/vhosts/system/DOMAIN.COM/conf/vhost.conf - this vhost.conf file doesn't exist, here is the directory structure:



# ls -al /var/www/vhosts/system/DOMAIN.COM/conf/
total 80
drwxr-x---. 3 root psaserv 4096 Apr 22 12:08 .
drwx--x--x. 7 root psaserv 4096 Apr 9 13:13 ..
-rw------- 1 root apache 6331 Apr 21 14:12 httpd.conf
-rw------- 1 root apache 6546 Apr 21 14:12 httpd.conf.bak
-rw------- 1 root root 6331 Apr 22 12:08 httpd.conf_saved
-rw------- 1 root apache 9326 Apr 21 13:06 httpd_ip_default.conf
-rw------- 1 root apache 9326 Apr 21 13:06 httpd_ip_default.conf.bak
lrwxrwxrwx 1 root root 10 Apr 21 14:12 last_httpd.conf -> httpd.conf
lrwxrwxrwx 1 root root 21 Apr 21 13:06 last_ip_default.conf -> nginx_ip_default.conf
lrwxrwxrwx 1 root root 10 Apr 21 14:12 last_nginx.conf -> nginx.conf
-rw------- 1 root nginx 2485 Apr 21 14:12 nginx.conf
-rw------- 1 root nginx 2575 Apr 21 14:12 nginx.conf.bak
-rw------- 1 root nginx 2605 Apr 21 13:06 nginx_ip_default.conf
-rw------- 1 root nginx 2366 Apr 20 14:06 nginx_ip_default.conf.bak
drwxr-xr-x 2 root root 4096 Apr 21 14:12 siteapp.d
-rw-r--r-- 1 root root 2 Apr 22 03:48 stat_ttl.conf




So httpd.conf file tells me to modify a file that doesn't exist.

If we had to make some custom virtual host changes, i don't know if I should manually create this vhost.conf file, and if so should it be a 100% copy of httpd.conf (with the changes)? Or only contain the modified "sections" ?

Can anyone please shed some light on this.


Thanks
 
Hi N_Vas,

Can anyone please shed some light on this.
I will try my best... ^^


If you didn't add some additional apache- and/or nginx configurations/directives over the Plesk - Control - Panel, then these files ( vhost.conf / vhost_nginx.conf ) don't exist yet. Just move to

Websites & Domains > YOUR - Domainname > Web Server Settings

and you will see two boxes, one for apache and one for nginx, where you can add additional settings. Once you did that, the corresponding *.conf - files will be created.
 
Last edited by a moderator:
Back
Top