ISPConfig available

Discussion in 'General' started by till, Jun 18, 2012.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is available for download. This release is a bugfix release for ISPConfig 3.0.4.

    For a detailed list of changes, please see the changelog section below.

    *** New! The ISPConfig 3 manual is now available! ***

    Version 1.3 for ISPConfig >= 3.0.4 (Date: 10/25/2011)
    Author: Falko Timme <[email protected]>

    333 pages

    The manual can be downloaded from these two links:

    - Download

    The software can be downloaded here:

    - Changelog

    - Known Issues:

    Please take a look at the bugtracker:

    - BUG Reporting

    Please report bugs to the ISPConfig bugtracking system:

    - Supported Linux Distributions

    - Debian Etch (4.0) - Squeeze (6.0) and Debian testing
    - Ubuntu 7.10 - 12.04
    - OpenSuSE 11 - 12.1
    - CentOS 5.2 - 6.2
    - Fedora 9 - 15

    - Installation

    The installation instructions for ISPConfig can be found here:

    or in the text files (named INSTALL_*.txt) which are inside the docs folder of the .tar.gz file.

    - Update

    To update existing ISPConfig 3 installations, run this command on the shell:

    Select "stable" as the update resource. The script will check if an updated version of ISPConfig 3 is available and then download the tar.gz and start the setup script.

    Detailed instructions for making a backup before you update can be found here:

    If the ISPConfig version on your server does not have this script yet, follow the manual update instructions below.

    - Manual update instructions

    cd /tmp
    tar xvfz ISPConfig-3-stable.tar.gz
    cd ispconfig3_install/install
    php -q update.php
  2. edge

    edge Active Member Moderator

    Debian Squeeze servers updated with no problem!

    Thank you!
    Last edited: Jun 18, 2012
  3. pehden

    pehden New Member

    As soon as update files for postfix.

    postconf: warning: /etc/postfix/ unused parameter: smtpd_bind_address=
    /usr/sbin/postconf: warning: /etc/postfix/ unused parameter: smtpd_bind_address=

    fis by correcting the spelling to smtp_bind_address=
  4. falko

    falko Super Moderator ISPConfig Developer

    You can simply remove the smtpd_bind_address= line from the end of your It's just a warning and will be fixed in ISPConfig 3.0.5.
  5. ikrudolf

    ikrudolf Member

    Update succesful, tnx!
  6. riaanroux

    riaanroux New Member


    Hi all.

    Upgrade was done 100% but now my Autoresponders is not working.
    I updated ispconfig to but my Autoresponder is not working here is the mail logs there is no error in the mail log just show the mail coming in but not sending the autoresponder.

    Jun 21 11:25:41 svr postfix/smtpd[11229]: connect from localhost.localdomain[]
    Jun 21 11:25:41 svr postfix/smtpd[11229]: 2AE77540CD6: client=localhost.localdomain[]
    Jun 21 11:25:41 svr postfix/cleanup[11225]: 2AE77540CD6: message-id=<[email protected]om>
    Jun 21 11:25:41 svr postfix/qmgr[10993]: 2AE77540CD6: from=<[email protected]>, size=2076, nrcpt=1 (queue active)
    Jun 21 11:25:41 svr postfix/smtpd[11229]: disconnect from localhost.localdomain[]
    Jun 21 11:25:41 svr amavis[6282]: (06282-11) Passed CLEAN, [] [] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]om>, mail_id: Y-SAPZ7jcvuy, Hits: -0.8, size: 1467, queued_as: 2AE77540CD6, [email protected], 775 ms
    Jun 21 11:25:41 svr postfix/smtp[11226]: A31A6540A9E: to=<[email protected]>, relay=[]:10024, delay=2, delays=1.2/0.01/0/0.78, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=06282-11, from MTA([]:10025): 250 2.0.0 Ok: queued as 2AE77540CD6)
    Jun 21 11:25:41 svr postfix/qmgr[10993]: A31A6540A9E: removed
    Jun 21 11:25:41 svr postfix/pipe[11230]: 2AE77540CD6: to=<[email protected]>, relay=maildrop, delay=0.18, delays=0.07/0.01/0/0.1, dsn=2.0.0, status=sent (delivered via maildrop service)
    Jun 21 11:25:41 svr postfix/qmgr[10993]: 2AE77540CD6: removed
    Jun 21 11:25:44 svr imapd: Connection, ip=[::1]
    Jun 21 11:25:44 svr imapd: LOGIN, [email protected], ip=[::1], port=[46582], protocol=IMAP
    Jun 21 11:25:44 svr imapd: LOGOUT, [email protected], ip=[::1], headers=1490, body=0, rcvd=352, sent=3960, time=0
    Any help will be great.

  7. riaanroux

    riaanroux New Member


    Don't stress about the last post autoresponder is working just had to reboot hte server after updates was installed.

    Thanks for ISPconfig it works great.
  8. yoplait

    yoplait Member

    Everything's good on Debian stable.
  9. vygism

    vygism New Member

    I have problem after updating from to Traffic data is stopped at data what was before update and now not changes after anyone activity.I have ISPConfig3 installed on CentOS 6.2.Already tried all possible restarts,reboots and etc., but nothing helps.Where problem can be?

    Regards, Vygis
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Web traffic data is counted only once every night now as there were a lot of stability problems with vlogger on servers that use latest mysql versions. So there is no problem with your server, just wait until the next day as traffic stats are now generated like all other stats once every night.
  11. vygism

    vygism New Member

    Ok,big thx for info.I only think ,that maybe is possible to add some info to ISPConfig page with Web Traffic - something similar to "Web traffic stat is updated every night at ...". This would help for other users who migrate from older versions to latest and met same problem like me.

  12. popper2001

    popper2001 New Member

    Upgrade from

    I have an older master / slave configuration here which has been running ISPConfig on Debian lenny for some years now. Is it still possible to do an in-place upgrade (with the update script) to the current version or do we need to first update to an intermediate version?
    Last edited: Jul 1, 2012
  13. falko

    falko Super Moderator ISPConfig Developer

    It should work, however, we recommend that you upgrade to first and then to
  14. popper2001

    popper2001 New Member

    Thanks, Falko!

    Anything else we need to take care of (beside backup)? In which order should we proceed in that case (slave / master first)?
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    Update the master server first. The ispconfig updater is doing a backup, yust answer with yes when the updater asks you.
  16. PermaNoob

    PermaNoob Member

    Update is even more noob-friendly--THANKS!
  17. cfoe

    cfoe ISPConfig Developer ISPConfig Developer

    I might be wrong but...Slaves before Master server was my idea of best practice for updates. I am sure I read it somewhere here on the site or the manual.
  18. falko

    falko Super Moderator ISPConfig Developer

    This advice is deprecated - update the master first.
  19. Balam

    Balam New Member

    update via ssh works fine !!!

    thank you


    Kimsufi/OVH server
  20. till

    till Super Moderator Staff Member ISPConfig Developer

    Please post the exact error message that you got and make a new thread for your problem.

Share This Page