The ISPConfig update script is a easy way to update a ISPConfig 3 installation. If you want to create a manual backup of ISPConfig, take a look at the instructions at the end of the article.

To update ISPConfig 3, login as root user on the shell of your server and run the command:

ispconfig_update.sh

>> Update

Please choose the update method. For production systems select 'stable'.
The update from svn is only for development systems and may break your current setup.

Select update method (stable,svn) [stable]:

You should always select "stable" on a production system. The "svn" version is only suitable for ISPConfig 3 development.

The updater will then check the version of your system, download the latest update and starts the update process.

This application will update ISPConfig 3 on your server.

Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]:

You should choose "yes" here. This will create a backup of the ISPConfig scripts (/usr/local/ispconfig), the /etc directory and the ISPC0nfig MySQL database in the directory /var/backup/

Creating backup of "/usr/local/ispconfig" directory...
Creating backup of "/etc" directory...
Checking ISPConfig database .. OK
Starting incremental database update.

The update script will then start to install incremental database updates for ISPConfig, if required.

Reconfigure Permissions in master database? (yes,no) [no]:

If this is a slave server in a multiserver setup, then choose "yes" here on at least one of the slave servers. For single server installations, choose 'no'. Then you were asked if the services shall be reconfigured:

Reconfigure Services? (yes,no) [yes]:

You should choose "yes" here, only if you modified your system configuration manually, it might be better to choose no. But in this case, new features in ISPConfig might not work or functions might stop working until you adjusted the config files manually. So its always a good choice to select 'yes' here. In the next step, select the ispconfig port:

ISPConfig Port [8080]:

Port 8080 is the default, if you have not changed it, press enter. Otherwise enter the port number and then press enter. As the last step, you wre asked if the crontab shall get reconfigured, you can select yes here by just pressing return.

Create new ISPConfig SSL certificate (yes,no) [no]:

If your SSL certificate for the ISPConfig interface has been expired and you want to renew it or if you want to enable SSL encryption for the ISPConfig interface, then choose "yes". If you dont need a new SSL certificate, take the default (no).

Reconfigure Crontab? (yes,no) [yes]:

The ISPConfig updater will then update the ispconfig files and restart services, if the configuration has been changed.

Backup before updates

(This backup procedure is now integrated into the ISPConfig updater and gets executed automatically when you choose to create a backup during update)

Before you update a software, it is always a good idea to backup all relevant data. This enables you to restore the software version that you had before in case of an error. The steps to create a backup of the ispconfig software and settings are:

Create a backup folder:

mkdir /home/backup
chmod 700 /home/backup
cd /home/backup

Backup the database

mysqldump -u root -p dbispconfig > dbispconfig.sql

Backup the ISPConfig software

tar pcfz ispconfig_software.tar.gz /usr/local/ispconfig

Backup the configuration files in /etc

tar pcfz etc.tar.gz /etc

This backup does not include the emails and website data.

How to Update ISPConfig 3
Facebooktwittergoogle_plusredditlinkedinmail
Tagged on:

60 thoughts on “How to Update ISPConfig 3

  • March 12, 2010 at 7:06 am
    Permalink

    mysqldump -u root -p dbispconfig > dbispconfig.sql
    this is an error should be:
    mysqldump -u root -p dbispconfig > dbispconfig.sql

    Reply
    • March 26, 2010 at 11:27 am
      Permalink

      I don’t see any errors. Everything is clear.

      Reply
      • November 3, 2011 at 1:18 am
        Permalink

        lol they’r exactly the same

        Reply
        • November 25, 2011 at 9:44 am
          Permalink

          They are !

          The first one is dbisponfig(colon)sql

          The second one is dbispconfig(period)sql

          Look Closely !

          Reply
          • January 19, 2012 at 12:15 am
            Permalink

            nope they are both dots man. (look below at my other comment)

    • January 19, 2012 at 12:11 am
      Permalink

      You probably wanted to say that
      mysqldump -u root -p dbispconfig > dbispconfig.sql
      in the text above ist with a html > (>)
      while it should show the corresponding > (greater than) sign to symbolize that the output should be postet to the file dbispconfig.sql…

      Reply
      • January 19, 2012 at 12:14 am
        Permalink

        However in the comments the > got converted into a > 😉 funny stuff if you can’t properly code a comment form on faqforge.
        try to htmlencode that stuff… and ignore html code here please.

        Reply
        • November 12, 2013 at 5:10 am
          Permalink

          I just spent 10 minutes scratching my head over that :o| I need to read comments more thoroughly before bashing out commands.

          Reply
  • May 14, 2010 at 5:09 pm
    Permalink

    How do I restore my backup ?

    Reply
    • May 18, 2010 at 11:51 pm
      Permalink

      The SQL dump can be restored with e.g. phpmyadmin. The tar backup can be extracted with “tar pcfz backupfile.tar.gz” and then copy or move the complete directory tree or the files that you need back to their original location.

      Reply
  • June 30, 2010 at 8:50 pm
    Permalink

    HI, I have Fedora 5, and I have installed ISPConfig 2, you can upgrade to the 3.0 version of ISPConfig .. I await your response.

    Reply
  • July 1, 2010 at 3:24 pm
    Permalink

    ISPConfig 2 and 3 are completely different software packages. ISPConfig 2 can not be updated to ISPConfig 3.

    Reply
  • July 13, 2010 at 3:29 am
    Permalink

    I am still getting errors when entering the port number. ISPConfig Port [8080]:

    Any help if my port is a different one that “standard?” We had it in a lab doing some testing and I dont know who did what to it. Cheers

    Reply
    • July 13, 2010 at 8:28 am
      Permalink

      You may use any port that you like as long as it is not already in use by another application.

      Reply
  • August 8, 2010 at 11:58 pm
    Permalink

    This artical should start with the “Backup before updates” part.. 😉

    Better for the beginners to know you alway backup first.

    Reply
  • August 23, 2010 at 5:55 am
    Permalink

    I see the backup process doesn’t back up e-mails. How would you back up and restore e-mails?

    Reply
  • October 8, 2010 at 2:57 pm
    Permalink

    tar pcfz vmail.tar.gz /var/vmail/

    Reply
  • October 9, 2010 at 11:02 am
    Permalink

    Upgrade from 3.0.2.2 to 3.0.3 went good for me with the “ispconfig_update.sh” command.
    Using Debian (Leny) provided by OVH Kimsufi.
    Only things is I have now to login through HTTP instead of HTTPS.

    Reply
  • October 14, 2010 at 11:00 am
    Permalink

    How do you backup and restore websites?

    Reply
  • October 15, 2010 at 10:47 am
    Permalink

    Put the backup instructions on top of the document, I notices the backup advice after the backup script did run.
    Luckily successfully.

    Reply
  • October 18, 2010 at 12:46 pm
    Permalink

    The backup in the doc does not include emails and website database backups

    the following is for the emails; tar pcfz vmail.tar.gz /var/vmail/
    I need to backup website database, We are moving everything to a new server with a new installation.

    Reply
    • October 20, 2010 at 10:21 am
      Permalink

      These backup intructions are for a backup that contains all data that gets overwritten by a ispconfig update, it is not meant as a full server backup.

      Reply
  • October 21, 2010 at 2:37 pm
    Permalink

    Hi, I need to update 2 to 3. Anyone can help me? Thanks.

    Reply
    • October 21, 2010 at 2:40 pm
      Permalink

      ISPConfig 2 and 3 are completely different software packages which have different system requirements. ISPConfig 2 is based on linux system users while ISPConfig 3 uses virtual users for Email and FTP. So ISPConfig 2 can not be updated to ISPConfig 3.

      Reply
  • October 25, 2010 at 8:30 am
    Permalink

    Can someone please help me. How do I do a full Server backup ISPConfig.

    Reply
  • March 21, 2011 at 11:36 am
    Permalink

    Hello,
    we have 1 server in master and some other server in slave config. They run 3.0.1 and 3.0.2 . Should we upgrade the master, will it be necessary to upgrade also the slaves? And would the procedure be the same you described above with same script?

    thanks
    Eddison

    Reply
  • April 29, 2011 at 12:07 pm
    Permalink

    hi …
    i have installed ISPconfig 3.0.3.2 … when i try to update it to 3.0.3.3 with ispconfig_update.sh i get this response : “This software cannot be installed on a server wich runs ISPConfig 2.x.” … !!!
    any help anyone ?
    George

    Reply
    • May 2, 2011 at 9:09 am
      Permalink

      I guess you use one of the ispconfig 2 install folders on your server. Ensure that there is no folder /home/admispconfig or /root/ispconfig on your system.

      Reply
  • June 20, 2011 at 12:05 am
    Permalink

    Hi, i have this errors, why ? update for 3.0.3.2 3.0.3.3, Debian Lenny

    Operating System: Debian Lenny or compatible

    This application will update ISPConfig 3 on your server.

    Warning: mysql_connect(): Access denied for user ‘root’@’localhost’ (using password: YES) in /tmp/ispconfig3_install/install/lib/mysql.lib.php on line 78

    Fatal error: Cannot use string offset as an array in /tmp/ispconfig3_install/install/lib/update.lib.php on line 98

    Reply
    • June 20, 2011 at 11:30 am
      Permalink

      You use the wrong mysql root password. Most likely you changed the root password after you installed ispconfig without chaning it in /usr/local/ispconfig/lib/mysql_clientdb.conf file too.

      Reply
  • August 3, 2011 at 7:10 pm
    Permalink

    i had installed ispconfig 3 and the mail pop and smtp is showing turned off and phpmyadmin not getting installed.. can some one help. we have a centos 5.5

    Reply
  • December 5, 2011 at 1:36 pm
    Permalink

    I backed up the server as per the instructions given in the main article. I now have the following files in my /home/backup folder:-

    -rw-r–r– 1 root root 203424 Oct 9 12:35 dbispconfig.sql
    -rw-r–r– 1 root root 1163693 Oct 9 12:35 etc.tar.gz
    -rw-r–r– 1 root root 2760087 Oct 9 12:35 ispconfig_software.tar.gz
    -rw-r–r– 1 root root 77090 Oct 9 12:36 vmail.tar.gz

    I have lately messed up with file and folder permissions and ownership on the server’s root with recursive option. Would a restore of these files get the server functional again?

    How do i go about restoring these files? and where do I restore them.

    Thanks.

    Reply
    • December 5, 2011 at 5:29 pm
      Permalink

      The backup contains only the ispconfig files, database and the files from /etc/. Backups that you create with tar pcfz can be unpacked with tar xfz filename.tar.gz

      Reply
      • December 5, 2011 at 8:40 pm
        Permalink

        would that restore the files to their desired directories, or would i have to specify that manually?

        Reply
  • December 8, 2011 at 9:39 am
    Permalink

    I’m running 3.0.1.4 on a production server with many clients and Domains.
    I would like to try out the new features like Invoice and such but am not in the mood for any f-ups and down time that might happen with an update. I know I need to backup first but I was just wondering what the error quota is on updating to 3.0.4? Can I do this this quickly and smoothly w/o probs or should I just never change a running system?
    Any pitfalls to look out for?

    Sanks ferry matsch 🙂

    Reply
  • January 19, 2012 at 8:55 pm
    Permalink

    What happened to the ISPConfig Update Button? It’s replaced with some manual help text now.
    It was my favourite part of ISPconfig3.

    Reply
  • February 29, 2012 at 2:46 am
    Permalink

    Update instructions worked just fine for me. Thanks a lot. Nice tutorial.

    Reply
  • March 17, 2012 at 6:55 pm
    Permalink

    For Ubuntu 10.04
    Apache/2.2.14 (Ubuntu)
    MySQL client version: 5.1.61

    Note: If you have a password with a $ in it then specify that in the password text like this:
    “MyPa$$word” would become “MyPa\$\$word”. Otherwise it fails.

    Also, mysql has a virtual db called “information_schema” – mysqldump wil not work on this so change the code in the backup script from this:

    Ad a variable in the user vars section:
    mschema = “information_schema”

    Line 311–
    Change this:
    log “Starting mysqldump $i”
    `mysqldump -u$dbuser -p$dbpassword $i –allow-keywords –comments=false –add-drop-table > $tmpdir/db-$i-$FDATE.sql`
    $TAR $ARG $BACKUPDIR/$MDATE/db-$i-$FDATE.tar.bz2 -C $tmpdir db-$i-$FDATE.sql
    rm -rf $tmpdir/db-$i-$FDATE.sql
    log “Dump OK. $i database saved OK!”
    —————-
    to this::
    —————-
    log “Starting mysqldump $i”
    if [ “$i” != “$mschema” ] ; then
    `mysqldump -u$dbuser -p$dbpassword $i –allow-keywords –comments=false –add-drop-table > $tmpdir/db-$i-$FDATE.sql`
    $TAR $ARG $BACKUPDIR/$MDATE/db-$i-$FDATE.tar.bz2 -C $tmpdir db-$i-$FDATE.sql
    rm -rf $tmpdir/db-$i-$FDATE.sql
    log “Dump OK. $i database saved OK!”
    fi

    Reply
  • April 22, 2012 at 9:43 am
    Permalink

    Thx for the nice how to update! Work’s quite fine for me on Debian squeeze

    Reply
  • May 11, 2012 at 11:45 am
    Permalink

    Update didn’t work good from 3.0.2 to 3.0.4. Users couldn’t get their emails, because the users were unknown. Websites worked. What did I do wrong? Where do I get the 3.0.3 version? I just entered the standard settings above in FAQ.

    Reply
    • May 11, 2012 at 3:08 pm
      Permalink

      The update works fine from 3.0.2 to 3.0.4 here with the instructions above, so it must be a issue specific to your installation. Please post in the ispconfig forum to get support:

      http://www.howtoforge.com/forums/

      Reply
  • June 19, 2012 at 8:49 am
    Permalink

    Klasse!
    Das Update funktioniert problemlos. (Debian6)
    Im Terminal “ispconfig_update.sh” eingeben, die Fragen sorgfältig abarbeiten, – das war’s.
    Und die Erstellung von SSL-Zertifikaten ist in das Update-Script auch gleich mit eingearbeitet.
    Alles in Allem eine halbe Stunde Arbeit. – Ein richtig gutes Update-Script. – Respekt.

    Reply
  • November 13, 2012 at 2:54 pm
    Permalink

    Perfect! Thanks for this great article from germany. *like*

    Reply
  • February 26, 2013 at 11:32 pm
    Permalink

    I have ISPConfig 3.0.4 installed on 2 VPS systems as Cluster.
    Now i want to update to ISPConfig 3.0.5 do i have to use the updater on both VPS Servers?

    Kindly regards,

    P. Sopacua

    Reply
    • February 26, 2013 at 11:48 pm
      Permalink

      Yes, the updater has been executed on both servers. You sgould start on the master and choose to update permissions in master server when the updater asks.

      Reply
      • June 1, 2013 at 10:29 pm
        Permalink

        I can’t thank you enough for this — it’s awesome the support you guys provide.

        Reply
  • October 31, 2013 at 11:09 am
    Permalink

    Hi,

    ISPConfig 3.0.5.3

    What version of php provided with MySQL?

    Reply
  • March 27, 2014 at 5:03 pm
    Permalink

    When try to upgrade to ISPConfig 3.0.5.4 beta following this post: http://www.ispconfig.org/blog/1/entry-124-ispconfig-3054-beta-released/

    PHP Parse error: syntax error, unexpected ‘[‘ in /usr/local/ispconfig/server/plugins-available/mongo_clientdb_plugin.inc.php on line 253

    My System;

    Debian GNU/Linux 7.1

    mongod version v2.4.6 – Thu Mar 27 01:13:17.570 git version: b9925db5eac369d77a3a5f5d98a145eaaacd9673

    PHP 5.3.3-7+squeeze14 with Suhosin-Patch (cli) (built: Aug 6 2012 14:18:06)
    Copyright (c) 1997-2009 The PHP Group
    Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
    with XCache v1.3.0, Copyright (c) 2005-2009, by mOo
    with Suhosin v0.9.32.1, Copyright (c) 2007-2010, by SektionEins GmbH

    Reply
  • October 17, 2014 at 9:36 pm
    Permalink

    I have 2 ISPCpnfig running servers.
    I can not update to the latest release.

    PHP Parse error: syntax error, unexpected T_VARIABLE, expecting T_FUNCTION in /tmp/ispconfig3_install/install/dist/lib/fedora.lib.php on line 247

    I get this on both of them.

    Reply
  • October 22, 2014 at 3:29 am
    Permalink

    I just make last update. Worked fine until I do not restart server. After that no ISPconfig3 working and Squirrelmail as well. All other function of my email server, DNS, Nginx, Apache works…. Just cannot reach ISPConfig and Squirremail

    Anybody help me please.

    Reply
    • October 22, 2014 at 3:13 pm
      Permalink

      If you need help, then please post in the ISPConfig forum.

      Reply
  • September 13, 2015 at 2:52 am
    Permalink

    The update worked fine from 3.0.2 to 3.0.4 , thank you for this article.

    Reply
  • January 23, 2016 at 4:10 pm
    Permalink

    My update at my master ISPCONFIG 3 server stops at /etc auto backup. There´s plenty disk space yet and I dunno why it doesn´t update. All of my slaves are updated without any problems. Debian Wheezy here. :/

    Reply
    • February 17, 2016 at 11:35 pm
      Permalink

      Though that should also mention:
      This Version: 3.0.5.4p5

      Upgrading to:
      New Version : 3.0.5.4p8

      Operating System: Debian 7.0 (Wheezy/Sid) or compatible

      This application will update ISPConfig 3 on your server.

      Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]:

      Creating backup of “/usr/local/ispconfig” directory…
      Creating backup of “/etc” directory…
      [email protected]:/#

      It quits just like that. no error no log no nothing.

      Reply
  • February 16, 2016 at 10:14 pm
    Permalink

    The article should start with paragraph “Backup before updates”. You really shouldn’t place it at the end. #justsaying 🙂

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *