ISPConfig 2.2.13 released

Discussion in 'General' started by till, May 21, 2007.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig 2.2.13 is available for download.

    This ISPConfig release adds support for CentOS 4.5, Mandriva 2007 Spring, default

    SPF-Records and custom configuration file templates.
    The installer has been enhanced and PHP has been updated to 5.2.2,
    Clamassassin to 1.2.4 and Spamassassin to 3.2.0.

    Detailed Changelog

    - Added: Support for Mandriva 2007 Spring.
    - Added: Support for CentOS 4.5.
    - Added: Default SPF Records.
    - Added: The installer saves the old SSL certificate when ISPConfig is updated.
    - Added: /etc/Bastille/firewall.d/ will be kept during updates.
    - Added: Custom templates can now be stored in the folder

    These templates override the default templates in /root/ispconfig/isp/conf
    and will be saved during ISPConfig updates.
    - Added: Enabled port ranges in the firewall (e.g. 2000:2100).

    - Update: PHP to 5.2.2
    - Update: Spmasassassin to 3.2.0
    - Update: Clamassassin to 1.2.4
    - Update: Fixed some bugs in Dutch translation.
    - Update: Updated Polish translation.

    - Bugfix: Round Robin DNS now possible (A records with identical hostname, but

    different IP addresses).
    - Bugfix: Files and directories that contain spaces in their name are now handled

    correctly by the Web-FTP module.
    - Bugfix: users did not receive an email from the trouble ticket system when their

    question got answered.
    - Bugfix: when a user is updated, it isn't removed from groups with a GID < min.

    ISPConfig GID anymore.
    - Bugfix: Fixed a bug in the reseller statistics.
    - Bugfix: Fixed a bug in the trouble ticket system.



    Installation Instructions

    Download the ISPConfig-2.2.13.tar.gz from

    If you run ISPConfig on CentOS 4.x please update the HTML::parser perl module as

    described below before you proceed.

    Installation on the shell as root User:

    tar xvfz ISPConfig-2.2.13.tar.gz
    cd install_ispconfig

    The installer automatically detects the installed ISPConfig version and performs an


    Special note for Users of CentOS 4.x

    If you do not use ISPConfig on CentOs 4.x, ignore the instructions below!

    We also need the module HTML::parser. We could install the CentOS package

    perl-HTML-Parser, but this version is too old for the SpamAssassin version that

    comes with ISPConfig. It would result in the following error message during

    ISPConfig installation:

    REQUIRED module out of date: HTML::parser

    Therefore we must install the latest HTML::parser using the Perl shell.

    Run the following command to start the Perl shell:

    perl -MCPAN -e shell

    If you run the Perl shell for the first time you will be asked some questions. In

    most cases the default answers are ok. Because there's no ncftp package for CentOS,

    the Perl shell cannot find the programs ncftpget and ncftp, and you'll see something

    like this:

    Warning: ncftpget not found in PATH
    Where is your ncftpget program? []
    Warning: ncftp not found in PATH
    Where is your ncftp program? []

    It's ok to hit ENTER in both cases.

    Please note: If you run a firewall on your system you might have to turn it off

    while working on the Perl shell in order for the Perl shell to be able to fetch the

    needed modules without a big delay. You can switch it on afterwards.

    Now type in the following command to install the Perl module HTML::parser:

    install HTML::parser

    If the installation is successful, you'll see a line like this at the end:

    /usr/bin/make install -- OK



    afterwards to leave the Perl shell.

  2. magio

    magio New Member


    God job! :D
  3. danf.1979

    danf.1979 ISPConfig Developer ISPConfig Developer

    No problem here, but I noticed that the customized_template directory is completely recreated when installing a new ispconfig version. I had removed the original one from the 2.2.13 beta, and replaced it with a symlink which was now a normal directory again. Apart from that, everything is looking good. No warnings en the logs.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig saves the directory content of the templates itself and restores them after the update to the newly created directory. You can not symlink this directory as it is always removed during update.
  5. payne

    payne New Member

    After ISP Config update, Remoting Framework doesn't work.
    I'm getting
    Error: Server:
    when i'm trying to connect from test.php file. Username and password are really good.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    The remoting framework is not supported by ISPConfig 2.2.13 and all 2.2.x versions before. I guess you have compiled your previous ISPConfig stable version manually with XML support, you will have to do the same with ISPConfig 2.2.13.
  7. joostvdl

    joostvdl Member

    Foldout of ISP Manager not working

    I just updated the ISPConfig. But when I go to ISPCOnfig, I'm unable to unfold the ISP Manager tree in the left of the screen. This fails at: ISP Manager and DNS Manager. On the ISP Invoice there is no problem.

    I have the dutch (nl) install.
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Just checked it, the dutch translation works fine for me. Do you get just a blank page or a link wher you may click to reload the page? Please try to switch to english language, does the problem still exists?
  9. Hans

    Hans Moderator ISPConfig Developer

    Hi Till,
    Thanks for the release!

    I've just installed it on my production server and everything went fine!

    I use the Dutch Interface too.
    There are no problems with unfolding the ISP Manager tree in the left of the screen. I also did not notice that problem with the beta 1 version last week.

    So for this reason i want to ask you: which browser do you use?
    If you use specials Firefox plugins, maybe they are the cause.
    Please unfold the structure tree by using another browser.
    Just to test what happens.
  10. payne

    payne New Member

    Yes,i deleted all disable xml directives in configure. Php info shows that XML Support is active,but nothing changed. I still cannot login.
  11. edge

    edge Active Member Moderator

    Update was no problem here. I'm Dutch, but do not have the Dutch language installed (all customers are English), so I can not give a report on it.
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you also install the remoting plugin again and check if the remoting user is still listed in the remote users list?
  13. payne

    payne New Member

    Yes,i did. I can see in User section my username that i added. Maybe somebody else have same problem?
    Last edited: May 21, 2007
  14. the_spy

    the_spy New Member

    Just updated, all is working, thanks :)
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    We have not changed anything related to remoting, so I really have no idea why it does not work for you. And you installed the latest remoting framework which is not encoded with the ioncube encoder?
  16. payne

    payne New Member

  17. payne

    payne New Member

    With ISPConfig 2.2.12 Remoting Framework works fine,so i think it's something wrong with 2.2.13 version of ISPConfig.
  18. till

    till Super Moderator Staff Member ISPConfig Developer

    We have not changed anything in this part of the software, so I have no idea what might have caused this. I will put it in the bugtracker. We will not release a update for this bug before ISPConfig 2.2.14 will be released regularily in about a month as the remoting framework is not officially available for the 2.2.x branch. Instead I will make available a link to the daily SVN build of the stable branch when this issue is fixed.
  19. Sheridan

    Sheridan New Member

    I've now upgraded my production machine too. Everything worked really smooth and i enjoyed not to have to recreate the certificates like during all the upgrades before.

    Really great work guy's. Thanks. :)

  20. madmucho

    madmucho ISPConfig Developer ISPConfig Developer


    Mandriva 2007 and 2007.1
    When i install or Upgrade ispconfig i must allways do this changes in this files for clamav and spamassasin to work. Tested through mail header.
    vi /home/admispconfig/ispconfig/tools/clamav/bin/clamassassin
    change directive „TMPPATH=/root/tmp“ to „TMPPATH=/tmp“ 
    vi /root/ispconfig/isp/conf/spamassassin.rc.master
    find /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin 
    change to

    and restart.

    /etc/init.d/ispconfig_server restart
    Is that typicaly for mandriva ? Can be this integrated in instlation script please?

Share This Page