This way you can restore the previous software version in case of an error. (This backup process is now integrated in the ISPConfig updater and will be executed automatically if you want to create a backup during the update).īefore you update software, it is always a good idea to backup all relevant data. The ISPConfig updater will then update the ispconfig files and restart services, if the configuration has been changed. If you dont need a new SSL certificate, take the default (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". As the last step, you wre asked if the crontab shall get reconfigured, you can select yes here by just pressing return.Ĭreate new ISPConfig SSL certificate (yes,no) : Otherwise enter the port number and then press enter. Port 8080 is the default, if you have not changed it, press enter. In the next step, select the ispconfig port: So its always a good choice to select 'yes' here. But in this case, new features in ISPConfig might not work or functions might stop working until you adjusted the config files manually. You should choose "yes" here, only if you modified your system configuration manually, it might be better to choose no. For single server installations, choose 'no'. Then you were asked if the services shall be reconfigured: If this is a slave server in a multiserver setup, then choose "yes" here on at least one of the slave servers. Reconfigure Permissions in master database? (yes,no) : The update script will then start to install incremental database updates for ISPConfig, if required. 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/Ĭreating backup of "/usr/local/ispconfig" directory. Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) : This application will update ISPConfig 3 on your server. The updater will then check the version of your system, download the latest update and starts the update process. The "svn" version is only suitable for ISPConfig 3 development. You should always select "stable" on a production system. The update from svn is only for development systems and may break your current setup. In the case of a Multiserver setup, update the master server first and then the slave servers. ispconfig_update.sh -forceįor Multiserver setups, it is recommended to enable maintenance mode under System > Interface > Main config in ISPConfig to avoid other users doing changes in ISPConfig while the nodes of the multiserver setup are not in sync. If you want to force an update in case your current version is the same, use -force option. ![]() To update ISPConfig 3, log in as root user on your server's shell and run the command: ispconfig_update.sh This tutorial applies to ISPConfig 3.0, ISPConfig 3.1, and also ISPConfig 3.2. If you want to make a manual backup of ISPConfig, see the instructions at the end of the article. The ISPConfig update script is an easy way to update an ISPConfig 3 installation.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |