The first release candidate of the upcoming ISPConfig 3.0.5.4 is available for download. RC versions are released for testing purposes and should not be installed on production systems. What's new in ISPConfig 3.0.5.4 - Support for Apache 2.4. - Support for Ubuntu 13.10. - Support for OpenSuSE 12.3 and 13.1. - Added option to disable a whole client with one click. - Clients can be assigned to another reseller. - Added limit templates for resellers. - Added automatic welcome email for clients. - Added min. password length and strength check. - Add functions that allow clients to add their own nginx directives. - The "Login as client" function is now available for resellers too. - Added support for multiple email addresses in "send copy to" field of the mailbox. - Several other minor features have been added and a lot of bugs have been fixed. Please see release notes for a full list of changes. Detailed Changelog http://bugtracker.ispconfig.org/index.php?do=index&tasks=&project=3&due=77&status[]= Download http://www.ispconfig.org/downloads/ISPConfig-3.0.5.4rc1.tar.gz Update instructions Code: cd /tmp rm -rf /tmp/ispconfig3_install wget http://www.ispconfig.org/downloads/ISPConfig-3.0.5.4rc1.tar.gz tar xvfz ISPConfig-3.0.5.4rc1.tar.gz cd ispconfig3_install/install php -q update.php
I Installed RC1, now when sending mail i get following error Code: warning: TLS library problem: 13396:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
I noticed email forwards do not work. The mailqueue shows mail messages with following error: temporary failure. Command output: /usr/bin/maildrop: Unable to create a dot-lock at
The error message means that your server tres to deliver the email locally. so the target that you forward emaisl to must exist as mail domain on your server. Please cross check that, I will test it here but we have already several servers that run the RC in production without issues.
I had amavis commented out as follows Code: # content_filter = amavis : [ 127.0.0.1] : 10024 If you do this mail forwarding will not work unless you commets out following line Code: # receive_override_options = no_address_mappings
Yes, thats correct. its described in the FAQ. If you want to diable amavis on a server, then these both lines have to be commented out: http://www.faqforge.com/linux/contr...ilter-and-antivirus-functions-in-ispconfig-3/
Any chance we can get a release version soon? I am stuck on Ubuntu 13.04 and need to upgrade a production server due to the OpenSSL Heartbleed issue.
The final version will be released in april. If you have to update right now, then you can use the rc version as well, ist quite stable and it has less bugs then 3.0.5.3.
You can install OpenSSL version 1.0.1g to fix the Heartbleed bug. Manually install it if the Ubuntu repo has not been updated or use "sudo apt-get update" followed by "sudo apt-get upgrade openssl" if the repo has been updated (I think it has). You will need to restart apache and that should sort out your Heartbleed problem.
It is my understanding that Ubuntu 13.04, which is out of support as of Jan 2014 is never going to receive the OpenSSL 1.0.1g update.[1] I have done the apt upgrades and openssl is still 1.0.1c. To keep this on topic I will upgrade to ISPConfig 3.0.5.4 RC1 and then to Ubuntu 13.10. [1] http://www.ubuntu.com/usn/usn-2165-1/
DNS SRV record Hi All, I would like to create _autodiscover._tcp.domain.com. srv record but I get this:"ERROR The hostname has the wrong format." in 3.0.5.4.rc1 Is it possible ? Thanks in advance.
An update to anyone who needs to upgrade from Ubuntu 13.04. The installation went very well. I installed 3.0.5.4RC1, then upgraded to Ubuntu 13.10. The issues I ran into were PHP related short_open_tag was off. I turned them back on in /etc/php5/apache2/php.ini and changed each web site as needed back to mod_php in ISPConfig. Squirellmail did not work, but I had previously upgraded to Roundcube, this is still an open issue for now. I did accept each of the 13.10 package config files after viewing the diff changes to see what I needed to put back. I had to re-enable fail2ban ssh in jail.conf and update the bantime to 86400 (1 day). OpenSSL did upgrade nicely to 1.0.1g and solved all of the heartbleed issues. Apache 2.4 doesn't seem to be the compatibly nightmare I had feared as all of my sites seemed to work fine except for the short_php_tags. Thanks to ISPConfig for great software.
I also just performed the upgrade in the same order - first I upgraded to 3.0.5.4RC1 then did the Ubuntu upgrade. The issue I ran into was that I had to manually make the necessary changes in the apache conf files at /etc/apache2/sites-available What I had to do was: Insert the contents of ispconfig.vhost into ispconfig.conf Rename apps.vhost -> apps.conf Rename my other sites' .vhost -> .conf In all of the above files, makes the changes described at http://httpd.apache.org/docs/2.4/upgrading.html Particularly replacing the Order/Allow directives with Require - there may be other things that can/should be updated. Create new symlinks in /etc/apache2/sites-enabled where required a2dissite 000-default.conf Finally I simply reloaded apache and all my sites as well as ispconfig started working again I must admit that I accepted the package config file changes without paying particular attention to the diffs. In retrospect this does worry me a bit as I'm not sure if ispconfig makes any changes to apache2.conf that would need to be preserved? However, the most important stuff seems to be running. I haven't had a chance to check mail but will certainly do so, as well as fail2ban as you've mentioned. I can also report success with the OpenSSL upgrade (by the way, on Ubuntu 13.10 the patched package is 1.0.1e-3ubuntu1.2 as described here) I wonder if my upgrade experience would have been different had I upgraded Ubuntu before upgrading ispconfig? RC2 is out now, hopefully I can upgrade to that without any issues given the manual changes I've made.
Your issues were caused by the wrong update order that you had choosen. You have to upgrade ubuntu first and then ispconfig. It is not nescessary to rename any config files. You will get issues on your server due to the renaming that you made when you update the next time. To fix your setup, undo all steps you listed above, then download ispconfig tar.gz again, unpack it and run the update.php script and let it reconfigure the services.
Hi Till, Thanks for confirming my suspicion regarding the upgrade order. I will do as you suggested and let you know the results.
