ISPConfig 3.0.5.4 Patch 1 is available for download. This is a patch release for ISPConfig 3.0.5.4 that fixes some issues that were found in the last version. See changelog below for details. ----------------------------------------------------- - Download ----------------------------------------------------- The software can be downloaded here: http://prdownloads.sourceforge.net/ispconfig/ISPConfig-3.0.5.4p1.tar.gz ------------------------------------ - Changelog ------------------------------------ http://bugtracker.ispconfig.org/index.php?do=index&tasks=&project=3&due=79&status[]= -------------------------------------- - Known Issues: -------------------------------------- Please take a look at the bugtracker: http://bugtracker.ispconfig.org -------------------------------------- - BUG Reporting -------------------------------------- Please report bugs to the ISPConfig bugtracking system: http://bugtracker.ispconfig.org ---------------------------------------- - Supported Linux Distributions ---------------------------------------- - Debian Etch (4.0) - Wheezy (7.0) and Debian testing - Ubuntu 7.10 - 14.04 - OpenSuSE 11 - 13.1 - CentOS 5.2 - 6.5 - Fedora 9 - 15 ----------------------------------------- - Installation ----------------------------------------- The installation instructions for ISPConfig can be found here: http://www.ispconfig.org/ispconfig-3/documentation/ 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: ispconfig_update.sh 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. A "reconfigure services" is not required for this patch update. Detailed instructions for making a backup before you update can be found here: http://www.faqforge.com/linux/controlpanels/ispconfig3/how-to-update-ispconfig-3/ If the ISPConfig version on your server does not have this script yet, follow the manual update instructions below. ------------------------------------------- - Manual update instructions ------------------------------------------- Code: cd /tmp wget http://www.ispconfig.org/downloads/ISPConfig-3-stable.tar.gz tar xvfz ISPConfig-3-stable.tar.gz cd ispconfig3_install/install php -q update.php
I do an auto-update from 3.053 to 3.054p1 by running ispconfig_update.sh. It works flawlessly and completely! Thanks!
Hello, everything works fine for me with this version, but since I didn't see any movement on the patch2 bugtracker for weeks (http://bugtracker.ispconfig.org/index.php?do=roadmap&project=3) I was wondering if everything was running well for the ispconfig team. Thanks for all your great work.
Everything is fine. We are working on the p2 release and also on the next major release 3.1. The bugtracker does not reflect the actual development activity. If you like to see the changes, take a look at our git repository: http://git.ispconfig.org/ and even the git repo does not refeect alll activity as we work also on the documentation, do tests, build new setups to test new technologies, improve the website, do community support etc.
Im running 3.0.5.4p1 and there is no System > Interface Config > Misc > Monitor for the monitor app.. Fordwrench Never mind I found it... System > Main Config > Misc > Monitor Keyword
I really think you should consider my proposal - making the client email mandatory. http://bugtracker.ispconfig.org/index.php?do=details&task_id=3242
When under Server config > Web > SSL for CA path I set /usr/local/ispconfig/interface/ssl/ispserver.crt when I run server.sh I get error 14.07.2014-16:46 - ERROR - CA path error, file does not exist:/usr/local/ispconfig/interface/ssl/ispserver.crt/openssl.cnf # ls -al /usr/local/ispconfig/interface/ssl/ispserver.crt -rw------- 1 root ispconfig 1854 Jul 11 13:06 /usr/local/ispconfig/interface/ssl/ispserver.crt
The ca path is a directory where the files of your own SSL CA are installed, it is not the path to a openssl certificate file.
