The templates for the configuration files are located in the folder:


The templates for the default index pages are in the folder:


The templates for the error pages are in the folder:


ISPConfig 3: Where are the templates for the config files and default pages?

8 thoughts on “ISPConfig 3: Where are the templates for the config files and default pages?

  • December 27, 2011 at 4:12 pm


    I set these templates (in my case, standard_index.html_es and user_standard_index.html_es) in my /usr/local/ispconfig/server/conf-custom/index but ISPConfig Version: does not use them. My users have spanish language by default. Is the same with /usr/local/ispconfig/server/conf-custom/mail/ welcome_email_es.txt What else do I need to do?

    Many thanks for your great job!

    • December 28, 2011 at 9:41 am

      The templates are used in the language that is set in the server configuration file. Please check that you selected “es” as language in the file /usr/local/ispconfig/server/lib/

      • December 28, 2011 at 10:28 am

        oops, many thanks 🙂

  • November 8, 2012 at 8:42 pm

    Is it possible to use an index.php file rather than the default index.html file instead? If so, how do I do this? Thanks Till for your continuous support.

    • September 13, 2013 at 2:41 pm

      Did you ever get an answer for this question? I want to do the same thing

      • October 1, 2013 at 11:42 am

        Just so people looking for the same thing that I was, the file that creates and moves all the new site files is ispconfig/server/plugins_available/ Ta

        • February 6, 2018 at 11:31 am

          No idea how old this thread is, but you could always
          copy /usr/local/ispconfig/server/conf/vhost.conf.master to
          /usr/local/ispconfig/server/conf-custom/vhost.conf and change the line
          AddType application/x-httpd-php .php
          AddType application/x-httpd-php .php .html
          and edit the skeleton index.html to include the desired php-code.

          From that moment on, each new site will get the edited index.html and it will be parsed as PHP

          I think that would be the least intrusive method and it should be upgrade-proof.

  • October 11, 2013 at 11:40 am

    If you want to specify 403.php rather than the default 403.html in a site, you can enter the following in the apache directives area under the website’s ‘options’ tab:

    ErrorDocument 400 /error/400.php
    ErrorDocument 401 /error/401.php
    ErrorDocument 403 /error/403.php
    ErrorDocument 404 /error/404.php
    ErrorDocument 405 /error/405.php
    ErrorDocument 500 /error/500.php
    ErrorDocument 502 /error/502.php
    ErrorDocument 503 /error/503.php

    This is on a per-domain basis


Leave a Reply

Your email address will not be published. Required fields are marked *