<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>FAQforge &#187; Webserver</title> <atom:link href="http://www.faqforge.com/category/linux/server/webserver/feed/" rel="self" type="application/rss+xml" /><link>http://www.faqforge.com</link> <description>Just another WordPress weblog</description> <lastBuildDate>Fri, 03 Feb 2012 13:47:23 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Apache mod-security installation on Debian 6.0 (squeeze)</title><link>http://www.faqforge.com/linux/apache-mod-security-installation-on-debian-6-0-squeeze/</link> <comments>http://www.faqforge.com/linux/apache-mod-security-installation-on-debian-6-0-squeeze/#comments</comments> <pubDate>Mon, 02 Jan 2012 11:20:06 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category> <category><![CDATA[squeeze]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1486</guid> <description><![CDATA[Install the apache mod-security 2 module with apt from the Debian repositories apt-get install libapache-mod-security Create the folder for the mod-security configuration files mkdir /etc/apache2/mod-security chmod 600 /etc/apache2/mod-security Download and unpack the mod-security rules cd /tmp wget http://www.modsecurity.org/download/modsecurity-core-rules_2.5-1.6.1.tar.gz tar fvx modsecurity-core-rules_2.5-1.6.1.tar.gz mv *.conf /etc/apache2/mod-security/ ln -s /var/log/apache2 /etc/apache2/logs Configure apache to load the activated mod-security [...]]]></description> <content:encoded><![CDATA[<p>Install the apache mod-security 2 module with apt from the Debian repositories</p><p
class="command">apt-get install libapache-mod-security</p><p>Create the folder for the mod-security configuration files</p><p
class="command">mkdir /etc/apache2/mod-security<br
/> chmod 600 /etc/apache2/mod-security</p><p>Download and unpack the mod-security rules</p><p
class="command">cd /tmp<br
/> wget http://www.modsecurity.org/download/modsecurity-core-rules_2.5-1.6.1.tar.gz<br
/> tar fvx modsecurity-core-rules_2.5-1.6.1.tar.gz<br
/> mv *.conf /etc/apache2/mod-security/<br
/> ln -s /var/log/apache2 /etc/apache2/logs</p><p>Configure apache to load the activated mod-security rules</p><p
class="command">vi /etc/apache2/conf.d/mod-security.conf</p><p><span
class="system">Include /etc/apache2/mod-security/*.conf</span></p><p>To enable mod-security, edit the file</p><p
class="command">vi /etc/apache2/mod-security/modsecurity_crs_10_config.conf</p><p>and remove the # in front of the line:</p><p
class="system">SecDefaultAction &#8220;phase:2,log,deny,status:403,t:lowercase,t:replaceNulls,t:compressWhitespace&#8221;</p><p>Then reload apache.</p><p
class="command">/etc/init.d/apache2 force-reload</p><p>Mod security will now start to block hack attempts to your websites and log the actions in the file /var/log/apache2/modsec_audit.log.</p><p
class="command">tail /var/log/apache2/modsec_audit.log</p><p>You will see very likely some falsely blocked URL&#8217;s. To whitelist them, you can add the ID&#8217;s of the rules that should not be used in the whitelist file.</p><p>Example:</p><p
class="command">vi /etc/apache2/mod-security/modsecurity_crs_99_whitelist.conf</p><p
class="system">SecRuleRemoveById 960015<br
/> SecRuleRemoveById 960016</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/apache-mod-security-installation-on-debian-6-0-squeeze/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>nginx server error: 413 Request Entity Too Large</title><link>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/</link> <comments>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/#comments</comments> <pubDate>Mon, 21 Nov 2011 11:34:10 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[nginx]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1316</guid> <description><![CDATA[The nginx webserver has a max. body size limit of 1 MB for requests as default. This might be too low for file uploads in scripts and you will see the following error message when you try to upload a file:  413 Request Entity Too Large The configuration variable for this option is &#8220;client_max_body_size&#8221; and [...]]]></description> <content:encoded><![CDATA[<p>The nginx webserver has a max. body size limit of 1 MB for requests as default. This might be too low for file uploads in scripts and you will see the following error message when you try to upload a file:</p><p
class="system"> 413 Request Entity Too Large</p><p>The configuration variable for this option is &#8220;<span
class="system">client_max_body_size</span>&#8221; and it can be set in the <span
class="system">http, server</span> and<span
class="system"> location</span> sections of the nginx configuration file. To set the Limit globally to 25 MB, edit the nginx.conf file and add:</p><p
class="system">client_max_body_size 20M;</p><p>in the http section.</p><p>Example for Ubuntu Linux:</p><pre class="system" dir="ltr">user www-data;
worker_processes 4;
pid /var/run/nginx.pid;

events {
        worker_connections 768;
        # multi_accept on;
}

http {
        geoip_country  /etc/nginx/geoip/GeoIP.dat; # the country IP database
        geoip_city     /etc/nginx/geoip/GeoLiteCity.dat; # the city IP database
        ##
        # Basic Settings
        ##

        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 65;
        types_hash_max_size 2048;</pre><pre dir="ltr">        client_max_body_size 20M;

        include /etc/nginx/mime.types;
        default_type application/octet-stream;

        ##
        # Logging Settings
        ##

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        ##
        # Gzip Settings
        ##

        gzip on;
        gzip_disable "msie6";

        ##
        # Virtual Host Configs
        ##

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}</pre>]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/nginx-server-error-413-request-entity-too-large/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Webalizer: Error Opening file /usr/share/GeoIP/GeoIP.dat on Debian Linux</title><link>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/</link> <comments>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/#comments</comments> <pubDate>Tue, 25 Oct 2011 14:06:44 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[webalizer]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=1030</guid> <description><![CDATA[The webalizer package in Debain 6 has currently small bug as the required package for the  GeoIP database is not installed automatically when webalizer is isntalled. The symptoms are that webalizer statistics are not created and this error message is displayed when webalizer is run: Error Opening file /usr/share/GeoIP/GeoIP.dat The solution is to install the [...]]]></description> <content:encoded><![CDATA[<p>The webalizer package in Debain 6 has currently small bug as the required package for the  GeoIP database is not installed automatically when webalizer is isntalled. The symptoms are that webalizer statistics are not created and this error message is displayed when webalizer is run:</p><p
class="system">Error Opening file /usr/share/GeoIP/GeoIP.dat</p><p>The solution is to install the missing package manually:</p><p
class="command">apt-get install geoip-database</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/webalizer-error-opening-file-usrsharegeoipgeoip-dat-on-debian-linux/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Redirect http requests to a new folder with apache rewrite rules</title><link>http://www.faqforge.com/linux/redirect-http-requests-to-a-new-folder-with-apache-rewrite-rules/</link> <comments>http://www.faqforge.com/linux/redirect-http-requests-to-a-new-folder-with-apache-rewrite-rules/#comments</comments> <pubDate>Fri, 12 Aug 2011 08:21:59 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category> <category><![CDATA[rewriterule]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=598</guid> <description><![CDATA[When you reorganize the structure of a website, you might want to redirect requests to files in a old folder to a new one without loosing the pagerank. In this example, I will redirect all requests from directory &#8220;olddir&#8221; to directory &#8220;newdir&#8221;, so that requests like http://www.yourdomain.tld/olddir/page.htm get redirected to http://www.yourdomain.tld/newdir/page.htm without loosing the Google pagerank [...]]]></description> <content:encoded><![CDATA[<p>When you reorganize the structure of a website, you might want to redirect requests to files in a old folder to a new one without loosing the pagerank. In this example, I will redirect all requests from directory &#8220;olddir&#8221; to directory &#8220;newdir&#8221;, so that requests like http://www.yourdomain.tld/olddir/page.htm get redirected to http://www.yourdomain.tld/newdir/page.htm without loosing the Google pagerank of the pages.</p><p>The following rewrite rules can be added into a <span
class="system">.htaccess</span> file in the website directory or in the vhost configuration.</p><p
class="command">RewriteEngine on<br
/> RewriteRule ^olddir/(.*)$ newdir/$1 [R=301,L]</p><p>This rewrite rule redirects automatically all requests to pages or subdirectorys of &#8220;olddir&#8221; to the same page or subdirectory in &#8220;newdir&#8221;.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/redirect-http-requests-to-a-new-folder-with-apache-rewrite-rules/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Prevent DOS attacks on apache webserver for DEBIAN linux with mod_evasive</title><link>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/</link> <comments>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/#comments</comments> <pubDate>Mon, 07 Mar 2011 13:23:21 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=559</guid> <description><![CDATA[The following guide explains the installation of the apache module &#8220;mod_evasive&#8221;. Mod_evasive tracks the number of requests of files at the apache webserver and blocks the delivery in case that a certain limit has been reached. Installation apt-get install libapache2-mod-evasive Create the log directory for mod_evasive mkdir -p /var/log/apache2/evasive chown -R www-data:root /var/log/apache2/evasive Now we [...]]]></description> <content:encoded><![CDATA[<p>The following guide explains the installation of the apache module &#8220;mod_evasive&#8221;. Mod_evasive tracks the number of requests of files at the apache webserver and blocks the delivery in case that a certain limit has been reached.</p><p><strong>Installation</strong></p><p
class="command">apt-get install libapache2-mod-evasive</p><p>Create the log directory for mod_evasive</p><p
class="command">mkdir -p /var/log/apache2/evasive<br
/> chown -R www-data:root /var/log/apache2/evasive</p><p>Now we add the configuration for the module at the end of the file /etc/apache2/mods-available/mod-evasive.load</p><p
class="command">vi /etc/apache2/mods-available/mod-evasive.load</p><p>so that it looks like this:</p><p
class="command">LoadModule evasive20_module /usr/lib/apache2/modules/mod_evasive20.so<br
/> <IfModule
mod_evasive20.c><br
/> DOSHashTableSize 3097<br
/> DOSPageCount 2<br
/> DOSSiteCount 50<br
/> DOSPageInterval 5<br
/> DOSSiteInterval 1<br
/> DOSBlockingPeriod 10<br
/> DOSLogDir &#8220;/var/log/apache2/evasive&#8221;<br
/> </IfModule></p><p>and restart apache:</p><p
class="command">/etc/init.d/apache2 restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/prevent-dos-attacks-on-apache-webserver-for-debian-linux-with-mod_evasive/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>How to change the language of AWStats statistics on Debian Linux (ISPConfig 3)</title><link>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/</link> <comments>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/#comments</comments> <pubDate>Mon, 24 Jan 2011 15:04:37 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Webserver]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=551</guid> <description><![CDATA[To change the language of the website statistics generated by AWStats on a Debian Linux server to e.g. german (de), edit the /etc/awstats/awstats.conf file: nano /etc/awstats/awstats.conf and change the value of the &#8220;Lang&#8221; variable. To change the languge to e.g. German, cahnge: Lang=&#8221;auto&#8221; to Lang=&#8221;de&#8221; The website statistics are generated nightly on a ISPConfig 3 [...]]]></description> <content:encoded><![CDATA[<p>To change the language of the website statistics generated by AWStats on a Debian Linux server to e.g. german (de), edit the /etc/awstats/awstats.conf file:</p><p
class="command">nano /etc/awstats/awstats.conf</p><p>and change the value of the &#8220;Lang&#8221; variable. To change the languge to e.g. German, cahnge:</p><p
class="system">Lang=&#8221;auto&#8221;</p><p>to</p><p
class="system">Lang=&#8221;de&#8221;</p><p>The website statistics are generated nightly on a ISPConfig 3 server, so it may take up to 24 hours until the statistics will show up in German language.</p><p>Thanks to <a
href="http://www.planetfox.de/" target="_blank">PlaNet Fox</a> for this FAQ.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-change-the-language-of-awstats-statistics-on-debian-linux-ispconfig-3/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to solve the PHP XCache error: /dev/zero: No space left on device</title><link>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/</link> <comments>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/#comments</comments> <pubDate>Wed, 01 Sep 2010 10:19:51 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Virtualisation]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[OpenVZ]]></category> <category><![CDATA[XCache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=508</guid> <description><![CDATA[If you get the error &#8220;/dev/zero: No space left on device&#8221; in the apache error.log on a OpenVZ virtual machine, then the shared memory size in the xcache.ini is too high or the xcache.mm_path is set wrong. Edit the file /etc/php5/conf.d/xcache.ini vi /etc/php5/conf.d/xcache.ini and check the mm_path. On a OpenVZ virtual machine it should be [...]]]></description> <content:encoded><![CDATA[<p>If you get the error &#8220;<span
class="system">/dev/zero: No space left on device</span>&#8221; in the apache error.log on a OpenVZ virtual machine, then the shared memory size in the xcache.ini is too high or the xcache.mm_path is set wrong.</p><p>Edit the file /etc/php5/conf.d/xcache.ini</p><p
class="command">vi /etc/php5/conf.d/xcache.ini</p><p>and check the mm_path. On a OpenVZ virtual machine it should be set to &#8220;/tmp/xcache&#8221; as /dev/zero might not work correctly in a virtual machine:</p><p
class="system">xcache.mmap_path = &#8220;/tmp/xcache&#8221;</p><p>Then restart apache2:</p><p
class="command">/etc/init.d/apache2 restart</p><p>and check if the error has been resolved.</p><p>If the roor still occurs after some time, you will have to reduce the xcache.size.</p><p>Edite the xcache.ini file:</p><p
class="command">vi /etc/php5/conf.d/xcache.ini</p><p>and set xcache.size to e.g. 8 MB</p><p
class="system">xcache.size  =                8M</p><p>Then restart apache2:</p><p
class="command">/etc/init.d/apache2 restart</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/how-to-solve-the-php-xcache-error-devzero-no-space-left-on-device/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How to enable the new multisite feature in WordPress 3.0</title><link>http://www.faqforge.com/linux/how-to-enable-the-new-multisite-feature-in-wordpress-3-0/</link> <comments>http://www.faqforge.com/linux/how-to-enable-the-new-multisite-feature-in-wordpress-3-0/#comments</comments> <pubDate>Sun, 20 Jun 2010 11:56:46 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Basics]]></category> <category><![CDATA[Linux & Unix]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=480</guid> <description><![CDATA[If you recently updated to or installed WordPress 3.0, you might wonder where the menu for Multisite feature is. By default, these new functions are disabled after a WordPress update, to enable them, edit the file wp-config.php and add the line define(‘WP_ALLOW_MULTISITE’, true); On your next login, you will see a new menu labeled &#8220;Super [...]]]></description> <content:encoded><![CDATA[<p>If you recently updated to or installed WordPress 3.0, you might wonder where the menu for Multisite feature is. By default, these new functions are disabled after a WordPress update, to enable them, edit the file wp-config.php and add the line</p><p
class="system">define(‘WP_ALLOW_MULTISITE’, true);</p><p>On your next login, you will see a new menu labeled &#8220;Super Admin&#8221; which contains the functions to add new sites to wordpress.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/how-to-enable-the-new-multisite-feature-in-wordpress-3-0/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Apache webserver: redirect requests for domain.com to www.domain.com</title><link>http://www.faqforge.com/linux/controlpanels/apache-webserver-redirect-requests-for-domain-com-to-www-domain-com/</link> <comments>http://www.faqforge.com/linux/controlpanels/apache-webserver-redirect-requests-for-domain-com-to-www-domain-com/#comments</comments> <pubDate>Mon, 22 Mar 2010 13:24:53 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=429</guid> <description><![CDATA[Many webmasters want to redirect users that access their websites with &#8220;domain.tld&#8221; automatically to &#8220;www.domain.tld&#8221;. If you use the Apache web server, you can do this by using Apache rewrite rules. Add a .htaccess file with the following content in the root directory of the website: RewriteEngine On RewriteCond %{HTTP_HOST} !^www\.domain\.com RewriteRule (.*) http://www.domain.com/$1 [L,R=301] [...]]]></description> <content:encoded><![CDATA[<p>Many webmasters want to redirect users that access their websites with &#8220;domain.tld&#8221; automatically to &#8220;www.domain.tld&#8221;. If you use the Apache web server, you can do this by using Apache rewrite rules.</p><p>Add a .htaccess file with the following content in the root directory of the website:</p><p
class="command">RewriteEngine On<br
/> RewriteCond %{HTTP_HOST} !^www\.domain\.com<br
/> RewriteRule (.*) http://www.domain.com/$1 [L,R=301]</p><p>If you use ISPConfig as hosting control panel, you can add these rules also in the Apache directives field of the website instead of a .htaccess file</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/apache-webserver-redirect-requests-for-domain-com-to-www-domain-com/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>Get a list of all virtual hosts which are defined in all apache configuration files</title><link>http://www.faqforge.com/linux/controlpanels/get-a-list-of-all-virtual-hosts-which-are-defined-in-all-apache-configuration-files/</link> <comments>http://www.faqforge.com/linux/controlpanels/get-a-list-of-all-virtual-hosts-which-are-defined-in-all-apache-configuration-files/#comments</comments> <pubDate>Thu, 11 Mar 2010 15:26:46 +0000</pubDate> <dc:creator>Till</dc:creator> <category><![CDATA[Basics]]></category> <category><![CDATA[Controlpanels]]></category> <category><![CDATA[Debian]]></category> <category><![CDATA[Distributions]]></category> <category><![CDATA[ISPConfig 2]]></category> <category><![CDATA[ISPConfig 3]]></category> <category><![CDATA[Ubuntu]]></category> <category><![CDATA[Webserver]]></category> <category><![CDATA[apache]]></category><guid
isPermaLink="false">http://www.faqforge.com/?p=421</guid> <description><![CDATA[Have you ever searched where the virtual host of a website is defined in the apache config files? There is a handy option of the apache2ctl script which might help then. When you run the command: apache2ctl -S on the shell, you will get a list of all virtual hosts and default servers incl. the [...]]]></description> <content:encoded><![CDATA[<p>Have you ever searched where the virtual host of a website is defined in the apache config files? There is a handy option of the apache2ctl script which might help then. When you run the command:</p><p
class="command">apache2ctl -S</p><p>on the shell, you will get a list of all virtual hosts and default servers incl. the line number where it is defined. Example:</p><p
class="system">~# apache2ctl -S<br
/> VirtualHost configuration:<br
/> wildcard NameVirtualHosts and _default_ servers:<br
/> *:8080                 is a NameVirtualHost<br
/> default server ispconfig.local (/etc/apache2/sites-enabled/000-ispconfig.vhost:10)<br
/> port 8080 namevhost ispconfig.local (/etc/apache2/sites-enabled/000-ispconfig.vhost:10)<br
/> *:8081                 is a NameVirtualHost<br
/> default server ispconfig.local (/etc/apache2/sites-enabled/000-apps.vhost:10)<br
/> port 8081 namevhost ispconfig.local (/etc/apache2/sites-enabled/000-apps.vhost:10)<br
/> *:80                   is a NameVirtualHost<br
/> default server ispconfig.local (/etc/apache2/sites-enabled/000-default:1)<br
/> port 80 namevhost ispconfig.local (/etc/apache2/sites-enabled/000-default:1)<br
/> port 80 namevhost example.com (/etc/apache2/sites-enabled/example.com.vhost:7)<br
/> Syntax OK</p><p>Thanks to <a
href="http://www.planetfox.de/" target="_blank">Planetfox</a> for this tipp.</p> ]]></content:encoded> <wfw:commentRss>http://www.faqforge.com/linux/controlpanels/get-a-list-of-all-virtual-hosts-which-are-defined-in-all-apache-configuration-files/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 1/48 queries in 0.056 seconds using disk: basic
Object Caching 1546/1644 objects using disk: basic

Served from: www.faqforge.com @ 2012-02-05 00:29:33 -->
