The first beta version of the upcoming ISPConfig 3.0.4 is available for download. Beta versions are released for testing purposes, it is not recommended to use them on production systems. ISPConfig 3.0.4 is a major release with many new features and bugfixes. - New module for virtual server management. It uses OpenVZ containers to virtualize servers. Tutorials for this new module will get released soon. If you want to try it out right now, then you can use the basic setup from this tutorial: http://www.howtoforge.com/installing-and-using-openvz-on-debian-squeeze-amd64 Please be aware that the Debian openvz kernel requires that filesystem quota is disabled. So it is recommended that you dont use a server that hosts websites as virtual machine host, or your websites will loose the quota restriction. - Added support for nginx (>= 0.8.21) Webserver Please note that nginx version >= 0.8.21 is required if you want to use ISPConfig 3 with nginx. In addition to that, PHP-FPM has to be installed (Lighttpd's spawn-fcgi is not supported). For example, installation instructions for nginx/PHP-FPMcan be found here: Ubuntu 11.04: http://www.howtoforge.com/installing-nginx-with-php5-and-php-fpm-and-mysql-support-on-ubuntu-11.04 CentOS 6.0: http://www.howtoforge.com/installing-nginx-with-php5-and-php-fpm-and-mysql-support-on-centos-6.0 OpenSUSE 11.4: http://www.howtoforge.com/installing-nginx-with-php5-and-php-fpm-and-mysql-support-on-opensuse-11.4 For CGI support, fcgiwrap has to be installed, as shown in chapter 4 on http://www.howtoforge.com/serving-cgi-scripts-with-nginx-on-debian-squeeze-ubuntu-11.04 - Added support for mailman mailinglists - Added support for IPv6 addresses in websites - IP addresses can now assigned statically to clients - Protect web folders with .htaccess / .htpasswd files. Note: The javascript YUI framework has been replaced with JQuery. If you use custom themes, you will have to modify your theme. Changelog http://bugtracker.ispconfig.org/index.php?do=index&tasks=&project=3&due=29&status[]= Download http://www.ispconfig.org/downloads/ISPConfig-3.0.4-beta1.tar.gz Update instructions Code: cd /tmp rm -rf /tmp/ispconfig3_install wget http://www.ispconfig.org/downloads/ISPConfig-3.0.4-beta1.tar.gz tar xvfz ISPConfig-3.0.4-beta1.tar.gz cd ispconfig3_install/install php -q update.php
Faq hi all, it is great work on new version 3.0.4, thanx. I have a little question - how is a recommended configuration PHP for component FAQ? on my dev server after add "Section" get errors: Warning: Invalid argument supplied for foreach() in /usr/local/ispconfig/interface/lib/classes/listform.inc.php on line 286 Warning: Invalid argument supplied for foreach() in /usr/local/ispconfig/interface/lib/classes/listform_actions.inc.php on line 89 debian lenny , PHP/5.2.17-0.dotdeb.0 thx, Petr
Hi, I noticed a problem with php-fpm and precisely in the fact that yes ISPConfig adds the configuration for php-fpm but php-fpm does not run this configuration and must be manually restarted. The problem is when we delete a virtual host and ISPConfig does not remove the configuration for php-fpm, and it did not restart. Version: php5-fpm: 5.3.8, Nginx 1.0.6, debian squeeze Thx, Andy
I don't know if this is really a bug or something weired on my server. With 3.0.4 Beta 1 and even the current svn from today the redirect functions of subdomains and domain aliases do not work anymore. I tried to debug it and in the apache2 plugin the rewrite_rules array is correctly filled and sent to tpl system via setLoop(). The master conf section looks like this HTML: <tmpl_if name="rewrite_enabled"> RewriteEngine on <tmpl_if name='seo_redirect_enabled'> RewriteCond %{HTTP_HOST} ^<tmpl_var name='seo_redirect_origin_domain'>$ [NC] RewriteRule ^(.*)$ http://<tmpl_var name='seo_redirect_target_domain'>/$1 [R=301,L] </tmpl_if> <tmpl_loop name="redirects"> RewriteCond %{HTTP_HOST} <tmpl_var name='rewrite_domain'>$ [NC] RewriteRule ^/(.*)$ <tmpl_var name='rewrite_target'>$1 <tmpl_var name='rewrite_type'> </tmpl_loop> </tmpl_if> The RewriteEngine On entry is correctly put into the vhost file, but the redirects loop puts out nothing. The SEO rewrite for the main domain works as intended, but no additional redirect rewrite rules. Edit: It is a fresh install of ispc on debian squeeze, no update. The domain alias entries are inserted correctly into the vhost file.
Thanks for the bugreport. I've added it to the bugtracker. http://bugtracker.ispconfig.org/index.php?do=details&task_id=1798
Polish theme bug Error as in the attached graphic file, marked in red. Theme ISPConfig set to default_no_navimg and language PL. Browser: Firefox 7.0.1, Chrome 14.0.835.202
I've just fixed the problem. The problem was the new <tmpl_loop name="vhosts"> loop in vhosts.conf.master so that we have a nested <tmpl_loop name="redirects"> loop. Nested loops need a special treatment.
hi.. pls. is possible testing this error? if create new web vhost in isp 3.0.4 , and delete him, after restart server ( or apache ) , apache not starting ( error v100 vhost not exist ). vhost created in old version isp is seems deleted no problem. ( maybe is problem only my server? ) debian lenny , PHP/5.2.17-0.dotdeb.0 thx Petr
I don't know exactly how to reproduce this, but I had a similar problem once. It seems to be related to deleting and adding (or adding and deleting) the same domain (vhost) too fast - so the first job has not finished. Sometimes the cron seems to not delete the vhost symlink in sites-enabled although the file in sites-available is deleted - this leads to the apache restart error. As soon as you delete the symlink by hand the apache restart works again.
I have two things related to awstats statistics in latest ispc beta: 1.) I have enabled awstats 1-2 days ago and if i call the /stats/ dir and enter the correct access data I get the period select-box on top, but below it says: A file called awsindex.html exists and contains the correct statistic data. 2.) If I did not set a password for the statistics and call the /stats/ url I get an error 500 because the server cannot find the .htpasswd_stats file. Maybe this file should be there (empty) on web creation?
I don't know if this is fixed in stable branch, but in trunk theres a problem with the seo-redirect: Code: <tmpl_if name='seo_redirect_enabled'> RewriteCond %{HTTP_HOST} ^<tmpl_var name='seo_redirect_origin_domain'>$ [NC] RewriteRule ^(.*)$ http://<tmpl_var name='seo_redirect_target_domain'>/$1 [R=301,L] </tmpl_if> This leads to a double // at the end of the domain. Code: <tmpl_if name='seo_redirect_enabled'> RewriteCond %{HTTP_HOST} ^<tmpl_var name='seo_redirect_origin_domain'>$ [NC] RewriteRule ^(.*)$ http://<tmpl_var name='seo_redirect_target_domain'>$1 [R=301,L] </tmpl_if> should be correct.