We’re proud to announce the release of InterWorx 4.11.4, which, in addition to a few bug fixes, also allows users the option to test the next major release of InterWorx: 5 beta 3!
All InterWorx servers that have auto-updates enabled will have this update applied over the next 24 hours. After you update to 4.11.4, you’ll be able to change the release channel you are subscribed to by doing the following:
Log into NodeWorx
Go to Server --> Software Updates
Change the InterWorx Release Channel to one of the following:
[LIST]
[B]Release[/B] - the default channel.
[B]Stable[/B] - The Stable channel is updated with the contents of Release after a period of stability. This applies to ALL updates - including security updates.
[B]Release Candidate[/B] - This channel contains features that have passed through the Beta process and are scheduled for near-future release.
[B]Beta[/B] - contains pre-release versions. Recommended for customers that want not-yet-released features or bug fixes, and are willing to help test and provide bug reports.
[/LIST]
Below is a summary of changes in both 4.11.4 and 5 beta 3.
Version 4.11.4 includes the following:
Features
Added tiered InterWorx repositories for stable, release, release-candidate, and beta versions.
E-mail box quotas can now be set larger than 2GB, in addition to unlimited.
[B]Fixes[/B]
Fixed CPU usage graph failing on servers with 32 cores or higher.
Fixed an issue with deleting secondary domains from cluster nodes.
Fixed an issue with the SiteWorx file manager when extracting certain archives.
Fixed an issue with private IP detection.
Fixed an issue with Web Setup InterWorx activation crashing.
[B][U]
Version 5 beta 3 includes the following:[/U][/B]
Features
IPv6 Support
[LIST]
Add / edit / delete IPv6 addresses
Auto-assign IPv6 addresses to domains
ip6tables firewall support
IPv6 cluster loadbalancing support on compatible OS's (el6)
Multiple IP addresses per SiteWorx account
Added tiered InterWorx repositories for stable, release, release-candidate, and beta versions
Brand new default InterWorx theme "Heliotrope"
Improvements to the InterWorx theme system that allow theme authors more fine-grained control of the system's layout in addition to look/feel
Updated and improved file manager in SiteWorx
Added reCaptcha validation to NodeWorx and SiteWorx login forms (after failed login attempts)
Improved navigation guides on menus
Improved backend management of php/suphp integration
New Yum Repository management interface in NodeWorx > Server > Software Updates
DNS Template records now use special variables as placeholders rather than reserved values
Added ipv4.{domain} and ipv6.{domain} default records for zones
Added import support for Plesk 10.2+ imports
Updated backup and restore to support multiple IPv4 and IPv6
[B]Other Changes[/B]
Improved the calculation of the default threshold for CPU High Load alerts
Fixed a problem where a missing my.cnf file caused crashes in InterWorx
Fixed REMOTEASSIST and MASTER permission inconsistencies in NodeWorx
Added check to ClamAV and Secure IMAP problem detectors to ensure they are actually problems
Improved detection of VM/VPS environments
Fixed edge case delivery problems of e-mail vacation settings
Fixed a minor issue in the CloudFlare Plugin
Fixed a problem with malformed theme uploads causing unexpected file deletion
Added "advisory" messages for form inputs in some places - suggestions, rather than errors
Updated various RPM packages to assist in passing PCI compliance scans
Changed the default SSLCipher settings for system webserver and InterWorx webserver to more secure options
Fixed Bug: long unix names in the DirectAdmin importer would fail
Fixed Bug: imports containing a secondary domain with SSL failed when imported to a shared IP
Various other improvements and fixes throughout the system
Added IP Range validation to the APF Whitelist. IP Ranges can no longer contain system IPs, which would cause security issues.
Implemented infrastructure to better analyze and improve user experience
Fixed CPU usage graph failing on servers with 32 cores or higher
Fixed an issue with deleting secondary domains off of cluster nodes
Fixed an issue with the SiteWorx file manager when extracting certain archives
Fixed an issue with private IP detection
Fixed an issue with Web Setup InterWorx activation crashing
We encourage all users to update their servers to the latest version for the latest features and bug fixes. As always, the full changelog is located at http://www.interworx.com/developers/changelog/.
Feel free to discuss this release or ask questions here, but for the serious issues, open a ticket at the support desk.
[QUOTE=bear;21124]nice new theme, I like it
some great additions
where do I set mail quotas larger than 2gb, cannot find it
thanks[/QUOTE]
Thanks!
Regarding the mail quotas, they can be set when adding or editing an e-mail box in siteworx. “No Quota” was always an option, it’s just that if there was going to be a quota set, it had to be less than 2GB, prior to this update.
We’ve just fired up a new box with our dev license on it to test the new v5 beta, and have ran into an issue (probably something simple).
When first setup, the software updates page seems to think that the server is already on the beta release channel, but the software that is installed is from the release channel. If we try to change that, nothing happens and we are presented with the following:
“? Uncaught IWorx_Exception: Trying to write an ini file without first reading
A system error has occurred. Please try your request again in a few minutes.
If the error persists, please contact support.”
This is a brand new install on CentOS 6.4 minimal. This is the only error we get, and I can’t see anything obvious in the logs.
We’ve just fired up a new box with our dev license on it to test the new v5 beta, and have ran into an issue (probably something simple).
When first setup, the software updates page seems to think that the server is already on the beta release channel, but the software that is installed is from the release channel. If we try to change that, nothing happens and we are presented with the following:
“? Uncaught IWorx_Exception: Trying to write an ini file without first reading
A system error has occurred. Please try your request again in a few minutes.
If the error persists, please contact support.”
This is a brand new install on CentOS 6.4 minimal. This is the only error we get, and I can’t see anything obvious in the logs.
Any ideas would be much appreciated.
Jon[/QUOTE]
Hi Jon,
When an error like that happens, there’s almost always a useful “stacktrace” in the iworx log file at ~iworx/var/log/iworx.log. That’s what we would need to get a better idea of what is going wrong. You could dig that out, or just open a support ticket an we’ll be happy to take a look that way as well. That might be necessary anyway, if we need to login and try to reproduce it ourselves and watch the problem in real time.
How odd - rebuilt the machine and this time it’s all as you would expect: release channel there as default, and able to switch to beta without issues.
Very weird as we’d rebuilt the machine before to try and solve this, thinking it was something I’d done during the install process. Ah well - it’s working now and that’s the main thing.
Thanks!