Announcement

Collapse
No announcement yet.

LVE Manager & Hosting Limits

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • LVE Manager & Hosting Limits

    no vhost.conf files?

  • #2
    Im new to both Cloudlinux and to Plesk, but if I understand correctly - once CloudLinux is installed, there are no /var/www/vhosts/system/XXXXXX.COM/conf/vhost.conf files ? Is that the case or should there be a vhost.conf file for each web site? (I dont see any so this is why Im asking, Plesk documentation mentions vhost.conf files)

    I am also asking because hosting limits arent the only things that can go in a vhost.conf file (other items can be php settings, rewrite settings), so Im a bit confused about not finding any vhost.conf files.

    I see through LVE Manager we can limit processes, memory, etc per site. But what about other settings that would normally go in an Apache config (httpd.conf or vhost.conf)?

    Thanks

    Comment


    • #3
      Hello,

      Do you have any website created in Plesk? If so its vhost should really be in /var/www/vhosts/system/DOMAIN.COM/conf/httpd.conf (not vhost.conf but httpd.conf, on plesk 12).

      The hostinglimits_module should not be included in every vhost file, it is alive in global /etc/httpd/conf.d/modhostinglimits.confand actually is included only once, you may check if its loaded using following command:

      # httpd -M | grep hosti

      > Syntax OK
      > hostinglimits_module (shared)

      About limits, they are actually all possible limits available in system - CPU/memory/process number/entryprocesses/ . Other limits are done by Plesk , like quotas number of websites/ftp users, mysql databases etc.

      Comment


      • #4
        Hello Bogdan,

        Thank you, so yes - 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... its a populated config file)

        However when I look for /var/www/vhosts/system/DOMAIN.COM/conf/vhost.conf - this vhost.conf file doesnt 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 this is why Im a bit lost here (httpd.conf file tells me to modify a file that doesnt exist). If we had to make some custom changes, i dont know if I should manually create this vhost.conf file, and if so should it be a 100% copy of httpd.conf (with changes)? Or only contain the modified "sections"?

        Thank you

        Comment


        • #5
          Well, thats really strange. I am not Plesk guru however really looks like they are missing some Include directive for vhost.conf file there (Ive just checked our test plesk server). And did not found answer to this in google. Could you please ask parallels(odin) support about it? And... I would really like to know their reply.

          Thank you.

          Comment


          • #6
            Hi Bognan,

            Thanks I just asked Plesk/IOdin and they explained this which makes sense:

            --
            If you didnt add some additional apache- and/or nginx directives over the Plesk - Control - Panel, then these files ( vhost.conf / vhost_nginx.conf ) dont 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.
            --

            So that explains everything

            Comment


            • #7
              Yeah, that explain how they should be used.

              Thanks for getting back here

              Comment

              Working...
              X