Category: NewsInterWorx Version 5 beta 4 & Build 470 of 4.11.4 released!

Share this post...Tweet about this on TwitterShare on Google+0Share on Facebook0

We’re proud to announce the release of 5 beta 4 as well as 4.11.4 build 470! These are primarily bug fix releases, and we’d like to especially thank all of the users who have subscribed to the beta channel and provided feedback!

Interested in trying the beta? You can 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:
    • Release – the default channel.
    • Stable – The Stable channel is updated with the contents of Release after a period of stability. This applies to ALL updates – including security updates.
    • Release Candidate – This channel contains features that have passed through the Beta process and are scheduled for near-future release.
    • Beta – 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.

Below is a summary of changes in 5 beta 4 and 4.11.4 build 470.

Version 5 beta 4 includes the following:

Fixes:

  • Fixed issues with deleting an IPv6 address that just added via System IPs
  • Fixed an issue that prevented SimpleScripts from installing scripts on secondary domains
  • Fixed potential infinite loop in Siteworx CLI
  • Fixed empty name issue with repositories
  • Fixed “Unknown IP Address ‘0’” error when importing an InterWorx backup
  • ~iworx/bin/ip.pex — list now shows all domains
  • Fixed “device” column in IPs table
  • Fixed issue with ipv6 iworx.ini entries not not having values set on install
  • Fixed issue with increase in cpu usage by iworx-db resulting from bandwidth cron
  • Fixed issue where, when setting up clustering with no ipv6 addresses configured, ipv6 quorum ip option prevents cluster setup
  • Accepting EULA no longer results in stacktrace
  • Improved sections of htaccess interface in Siteworx
  • Fixed issue with secondary domain server aliases
  • Fixed issue where adding a cluster node fails claiming the node has siteworx accounts when it does not
  • Added SPFv3 support
  • Added a bin script to overwrite vhost file from the original skel
  • Added way for SiteWorx users to download zipped, rotated-out Apache logs
  • /webmail is now disabled for domains that don’t use that server for email
  • Fixed issue with BLK_PORTS setting in /etc/apf/conf.apf
  • Improved accuracy of bandwidth overage notification emails
  • Fixed issue where deleting the “default” MySQL server results in fail

Version 4.11.4 build 470 includes the following:

Fixes

  • Fixed SpamAssassin incorrectly checking blacklists and applying scores to messages sent through Horde
  • Updated FTP information in API documentation
  • Fixed issue where CM allowed users to add a node with no VIPs set
  • Fixed an error message in the sasql_db squirrelmail module
  • Fixed a minor issue in cpanel importer
  • Fixed issue with adding load balancer services
  • Fixed issue where adding a package during SiteWorx creation broke the command queue
  • Adding a cluster node with external NFS in use now firewall-whitelists the external NFS on the CM and the node
  • Fixed issue where Command Queue/cluster-account-add dies if a SiteWorx account is moved to a reseller that does not have default nameservers set
  • IP System now matches interfaces with names like Auto_eth1

All InterWorx servers that have auto-updates enabled will be updated according to their subscribed release channel over the next 24 hours. To see the full changelog for these and previous releases, head here: http://www.interworx.com/developers/changelog

4.115.0
Apr 8, 2013, 4:45 pmBy: InterWorx (0) Comments

Leave a Reply
Surround code blocks with <pre>code</pre>

Your email address will not be published.

Forum Posts

  • SSL Certificate Option December 5, 2016
    Hi, Question, I have 12 domain being hosted within my Interworx CP. Why would only some of them, whe […]
    hostpanda
  • Turing off catchall results in mailbox failure December 5, 2016
    Hi all, a custopmer wanted a catchall adress set up but now realized he gets way too much spam that […]
    mdeinhardt
  • Catchall December 5, 2016
    We have some clients who still like to use a catchall address even though we strongly discourage it […]
    Bertie