ISPConfig 2.2.0 released

- Support for 64Bit Linux:
Added x86_64 support for Debian, Ubuntu, Fedora, SuSE, Mandriva, and CentOS.
- Support for Slackware and Trustix Linux.
- All included software packages are now compiled from source for
better portability and are updated to the latest versions.
- Email forwarder configuration in mailuser interface.
- Support for MD5 password encrytion.

Detailed Changelog
------------------
- Support for 64Bit Linux:
Added x86_64 support for Debian, Ubuntu, Fedora, SuSE, Mandriva, and CentOS.
- Installer is now more fault-tolerant (e.g. it keeps asking for the MySQL
login until you type in the correct data).
- The installer compiles now also SpamAssassin, cronolog, zip and unzip from the sources.
- Added support for OpenVZ / Virtuozzo network interfaces (venet+)
in the Bastille firewall script.
- Added Slackware support.
- Added support for MD5 password encrytion.
- Enable / disable PHP filters for Apache2.
- Updated ClamAV to version 0.88.
- Updated Backend-Apache to version 1.3.34.
- Updated Backend-PHP to version 5.1.2.
- Updated Backend-mod_ssl to version 2.8.25-1.3.34.
- Updated Backend-OpenSSL to version 0.9.8a.
- Added option in config file to enable sudo for webquota statistics.
- Added email forwarder configuration in mailuser interface.
- Updated Swedish, French, and Italian language files.
- Added default values in SQL dump.
- Mailquota recipe is removed from configuration if Maildir is used.
- Automatic Co-Domains are added only if the Co-Domain does not
exist for another web site yet.
- Form for creating users now shows the correct email addresses
(if a web sub.example.com with no Co-Domain is created, then the email
address of a new user will be shown as [email protected]
instead of [email protected]).
- The server url is now set dynamically in config.inc.php.
- Added support for custom charsets in control panel interface
(iso-8859-1, iso-8859-2, iso-8859-3, ...).
- Improved Trustix30 support.
- Bugfix: HTTP headers in admin database backup script fixed for IE.
- Bugfix: HTTP headers in client backup script fixed for IE.
- Bugfix: Fixed a bug when copying clients and webs to an other reseller,
the permissions are not updated correctly.
- Bugfix: Use server's hostname for default MX records.
- Bugfix: Fixed bug in clients' recycle bin.
- Bugfix: Creation of multiple MySQL databases at one time is now possible.

If anyone has ISPConfig installed on a PPC machine and is braver than I...please let me know how it goes. I simply cannot break my current install. This is the first upgrade I've seen since 2.1 or so that makes me seriously think about upgrading.

Well I think I'm going to go ahead. According to the logs I kept when I originally set up ISPC, the things you guys fixed such as zip, cronolog, PHP...are exactly the things I had issues with. Am I correct in believing that restoring a backed up /root/ispconfig directory will get me back to my properly running config, should something go wrong?

Well I think I'm going to go ahead. According to the logs I kept when I originally set up ISPC, the things you guys fixed such as zip, cronolog, PHP...are exactly the things I had issues with. Am I correct in believing that restoring a backed up /root/ispconfig directory will get me back to my properly running config, should something go wrong?

Click to expand...

Please make a complete backup of your system if possible before you update. To make an easy restorable ISPConfig backup, backup the directories /root/ispconfig, /home/admispconfig with preserved permissions and the ispconfig database. In case the upgrade fails, just restore these backups to their original places.

Upgrading now. Thanks for the very quick response, Till. I'm not sure if you guys could use it, but I'll keep you updated as to whether or not it works smoothly on the PPC architecture. From the looks of it, the core issues that I remember and have documented have been addressed.

Update: Everything looks to be functioning well. No complaints as of yet Way to go ISPC team.

Boys and Girls... I'm still on the 'old' 2.1.2 version, and I must say that it's really working nice!

I'm about to start adding more sites and clients to the system, but I'm not sure if I should do this before I've updated to the new 2.2.0 version as the update might 'break' things, with the result of installing everything over again.

My question.. Is the update really needed, and is the 2.2.0 the final version, or is it still in 'beta' testing?

If I do the update, I should make a restorable ISPConfig backup... Whats the best way of doing this? I've only got root SSH access to the server (Fedora RC4).

till said:

Please make a complete backup of your system if possible before you update. To make an easy restorable ISPConfig backup, backup the directories /root/ispconfig, /home/admispconfig with preserved permissions and the ispconfig database. In case the upgrade fails, just restore these backups to their original places.

I used to access ISPconfig with my_ip:81.
After the update I could only access some parts of it this way.
It was the same with www.mydomainname.com:81 and mydomainname.com:81..

One of the problems was that I could not access any thing in the Management > Server part (I got an error: "The page cannot be displayed")

Also.. On all pages showing the 'ISP Server Status' the 'nav_lft.gif' and 'nav_rgt.gif' were missing. (see image)

The problems was that host.mydomainname.com was not resolving! (it never did, as I did not set it up to do so)

After adding an 'A Record' for 'host' in the DNS to make host.mydomainname.com resolve to the server IP, all was working fine again.

I can now access ISPconfig with host.mydomainname.com:81 and access the Management > Server (images are also shown) HOWEVER my_ip:81, mydomainname.com:81 and www.mydomainname.com:81 will still not let me access the 'Management > Server' part.. When I try to do this, it will kick me to the loginpage on host.mydomainname.com

I guess that this is all correct as the hostname of the server is: host, and the Domainname is: mydomainame.com
I'm still not sure why I did not have this problem the 'old' ISPconfig setup.

Question... Can I change the 'host' name in ISPconfig to 'www' to make ISPconfig accessable again with only www.mydomainname.com:81 ? (I'm used to this now)

Thanks again for all the help.. and a big thank you to the ISPConfig team.. Your product looks great!