InterWorx 7 recently reached Maintenance Only status . Public support for InterWorx 7 will end on December 31, 2026.

Because of this, we will be rolling out automated InterWorx 7 to InterWorx 8 upgrades for customers on EL8 servers. These automated upgrades will occur July 6-9, 2026.

Note: The automated upgrade will only occur for our external customers. Liquid Web and Nexcess customers’ servers will be upgraded at a later date. 

Automated update rollout procedure and timeline

• April-May 2026: InterWorx version 7.14.4  will include a banner in NodeWorx, alerting Server Admins about the automatic upgrades
  • This banner will only be shown in NodeWorx, and only to the Server Admin user and secondary NodeWorx users. It will not be shown to SiteWorx users or resellers

• • As we have a weekly release schedule, the ETA for the progression of 7.14.4 will be as follows:

• • • Beta: Week of April 20
    • Release Candidate: Week of April 27
    • Release: Week of May 4
    • Stable: Week of May 11

• • Depending on the server configuration, the banner will include the following information:
    • Vanilla EL8 servers: The server will automatically upgrade to InterWorx 8, the week of July 6th, 2026

• • • EL7, CloudLinux, Litespeed, and clustered servers: The automatic upgrade to InterWorx 8 is not supported for the server.
•  July 6-9, 2026: Servers that meet the criteria to automatically upgrade to InterWorx 8 will do so
• July 13, 2026: If the automatic update to InterWorx 8 failed, or could not complete, the banner in NodeWorx will change to inform the Server Admin, with instructions to contact InterWorx support

What actions should be taken?

• • For most servers, no action is needed. On the date your server is scheduled to upgrade, if all of the pre-flight checks pass, the server will automatically upgrade to IW8 as part of the daily cron
  • If you would like more control over updating from IW7 to IW8, we recommend using the in-place upgrade tool, prior to July 6th: Upgrading from InterWorx 7.x to InterWorx 8.x — InterWorx documentation

• Customers that are using CloudLinux, Litespeed, or clustering, or are still on an EL7 OS, will not receive the automatic upgrade to InterWorx 8

• •  EL8 CloudLinux, Litespeed and clustered servers will need to migrate to a supported version before InterWorx 7 reaches EOL status on December 31, 2026.
  • As public support for EL7 ended at the beginning of this year, those servers must be migrated to a supported environment, immediately

Things to know: 

The automatic upgrade to InterWorx 8 will include the following new features:

• Refreshed GUI
• New UI sidebar, with detailed information and documentation links for forms and tasks
• Improved Migration tool, which includes incremental imports and re-syncs, DNS updates, and other tools to assist with migrations
• Ability to change the docroot of primary or secondary domains via the GUI
• Ability to manage a Subdomain’s docroot and PHP version from the GUI
• Advanced domain configuration options via the GUI

Other Notable Changes:

• Horde is no longer a webmail option, as it does not support the new internal PHP version of PHP 8.2
• Webalizer was removed as a statistics option

Troubleshooting

As mentioned above, there is a pre-flight checklist that is addressed before the upgrade to IW8 occurs. All of these items must pass in order for the upgrade to run. These items are:

• The httpd syntax is error free: If there are any syntax errors in Apache confs or  vhosts, this will fail
• LiteSpeed is not enabled: This upgrade cannot occur on Litespeed servers. Litespeed will either need to be disabled, or the accounts will have to be migrated to a server with IW8 installed
• CloudLinux is not enabled: This upgrade cannot occur on servers running CloudLinux. Those accounts must be imported to a new server with IW8 installed
• The server is not part of a cluster: This update cannot occur on clustered servers. Clustering either has to be disabled/removed or accounts will need to be migrated to new servers with IW8 installed
• Yum dry run: This checks to make sure that yum is up and running
• The server is up to date: This makes sure that the server is up to date
• Server is running EOL OS version: This checks to make sure that the server is on a supported OS. The update to IW8 will not work on EL7 servers. If this fails, accounts must be migrated to a new server with IW8 installed. Supported OSes can be found here: What are the system requirements of InterWorx Control Panel? — InterWorx documentation
• Server is using Dovecot Submission: Servers using courier for port 587 cannot be updated to IW8. The Dovecot MSA must be in use. Information on how to check if the Dovecot MSA is in use on the server, can be found here: Dovecot and php-intl required for Roundcube 1.5.3

If, on July 13th, the banner states that the upgrade to InteWorx 8 could not complete: 

• Check the Preflight Checklist for any triggered flags
  • Navigate to Server > Software Updates
  • At the very bottom of the page is a section called Major Version Upgrade. Click Go to Updates Page.That will take you to the Preflight Checklist.

• If the preflight checklist does not show any triggered flags, check to make sure that the daily cron ran between July 6-9
  • The timestamp on ~iworx/var/last_daily  indicates the last time the daily cron successfully completed.  Example:

    [root@server ~]# ls -la ~iworx/var/last_daily
-rw------- 1 root root 0 April 13 18:43 /home/interworx/var/last_daily
[root@server ~]#

• If the timestamp on that file indicates that the daily cron did not successfully run during that time, further information about the cron failure may be found in ~iworx/var/log/cron.log

If you have any questions, or run into any issues, don’t hesitate to reach out to us at https://support.interworx.com. We will be happy to assist.

InterWorx 7 officially reached Maintenance Only/Deprecated status as of April 7, 2026.

What does this mean?

As of now, we will no longer be providing updates to InterWorx 7, outside of security and bug fixes.

When will InterWorx 7 go EOL?

Public support for InterWorx 7 will end December 31, 2026.

What actions should be taken?

• Customers who are still using InterWorx 7 on EL7 servers will need to migrate to a supported environment.

  Support for EL7 ended January 1st, 2026, and updating to InterWorx 8 is not possible on an EOL OS. Details can be found here: Public Support for EL7 ending January 1, 2026

  If you would like a demo key to facilitate the migration, feel free to reach out to us at support.interworx.com

• For customers using InterWorx 7 on EL8 servers, we will be rolling out automated, in-place IW7 to IW8 updates in the coming months. Communication with specific details, including a timeline, will be provided within the next few weeks
• If you would like more control over updating from IW7 to IW8, we recommend using the in-place upgrade tool: Upgrading from InterWorx 7.x to InterWorx 8.x — InterWorx documentation

If you have any questions or run into any issues, please submit a ticket to https://support.interworx.com and we will be happy to help you. We do not offer installation or migration services, but we assist as much as we can.

Information on service deprecation and removals can be found here: Deprecation Plan — InterWorx documentation

EL7 reached EOL status June 30, 2024: What to know about CentOS Linux EOL

While we will continue best effort support until the end of 2025, our public support of servers running EL7 operating systems (CentOS 7, RHEL 7, and CloudLinux 7) will officially end on January 1, 2026.

After January 1, InterWorx will continue to run on EL7 servers, and the license will still be valid.

However, InterWorx support will be limited to only the following two topics:

• Issues that may arise during a migration to a new server running supported OS
• If the issue is a bug within InterWorx

It is imperative that any server still using EL7 (including hybrid CloudLinux kernels) migrate to a server using a supported OS, as soon as possible.

Information on supported OSes can be found here: What are the system requirements of InterWorx Control Panel? — InterWorx documentation

Things to note:

• If you would like a demo key to facilitate the migration, just reach out to InterWorx support by submitting a ticket here: https://support.interworx.com .

  Or you can use this form: https://www.interworx.com/interworx-demos/

  Just note in the Questions section of the form that you are an existing customer who will be using the demo key for a migration:

• By default, all demo keys will be active for two weeks. However, they can be extended to up to four weeks–if you need the extra time, just add that information to the ticket or demo request form
• When migrating to a new server, you do not need to purchase a new InterWorx license. InterWorx licenses are not version or OS specific, so your current license can be used on the new server
• If the new server has a different IP than the current one, before applying your existing license key to the new server, you must first update the license binding for the key. Information on how to do so can be found here: How to: Change the IP Binding of an InterWorx License — InterWorx documentation
• If the key’s license binding is not changed before applying the license to the new server, you will get an error stating that the license has already been activated on another IP. If that occurs, submit a ticket to the support desk at https://support.interworx.com with the license key information, and we will manually clear the license binding for you.

Information on how to migrate accounts to the new server can be found here: How to: Import Hosting Accounts to InterWorx — InterWorx documentation

Note: It is only possible to migrate SiteWorx accounts. NodeWorx settings are not included and will need to be changed on the new server, manually.

If you have any questions or run into any issues, just submit a ticket to https://support.interworx.com and we will be happy to help you. We do not offer installation or migration services, but we assist as much as we can.

Information on service deprecation and removals can be found here: Deprecation Plan — InterWorx documentation

InterWorx 8 on CloudLinux Support

We are excited to announce that, as of version 8.1.5 (currently in the stable channel), InterWorx 8 now fully supports CloudLinux 8 and 9.

To use CloudLinux, InterWorx 8 must first be installed on RHEL 8 or 9, AlmaLinux 8 or 9, or Rocky Linux 8 or 9.

Once InterWorx is installed, the server can be converted to CloudLinux via the CloudLinux plugin.

Note: CloudLinux 9 support is ONLY for InterWorx 8. InterWorx 7 does not support CloudLinux 9.

If you have any questions or run into any issues, just submit a ticket to https://support.interworx.com and we will be happy to help you. We do not offer installation or migration services, but we will assist as much as we can.

We are pleased to announce the release of both EL9 support, and InterWorx 8 have both reached Public Release status and are considered stable for use on production servers.

EL9 Support:

The following EL9 operating systems are supported:

• RedHat Enterprise 9.x 2 64 bit Architecture
• AlmaLinux 9.x 6 64 bit Architecture
• Rocky Linux 9.x 3 64 bit Architecture
• NOTE: CloudLinux 9 is not supported at this time. We will be announcing when CloudLinux 9 support is available.

Things to Know:

• EL9 is only supported for InterWorx 8. InterWorx 7 does not support EL9
• It is not possible to do an in-place OS-upgrade to EL9. A new, fresh install RHEL 9, AlmaLinux 9, or Rocky Linux 9 is required

InterWorx 8 includes the following new features:

• Refreshed GUI
• New UI sidebar that includes detailed information and documentation links for forms and tasks
• Support for AlmaLinux 9, Rocky Linux 9, and RHEL 9
• Improved Migration tool, which includes incremental imports and re-syncs, DNS updates, and other tools to assist with migrations
• Ability to change the docroot of primary or secondary domains via the GUI
• Ability to manage a Subdomain’s docroot and PHP version from the GUI
• Advanced domain configuration options via the GUI

Other Notable Changes

• Horde is no longer a webmail option, as it does not support the new internal PHP version of PHP 8.2
• Let’s Encrypt and AutoSSL are enabled automatically
• Multiple PHP is now enabled automatically
• Webalizer was removed as a statistics option, as it does not support EL9
• Old file manager was removed, as it is not supported on EL8 or EL9

Documentation for IW8 can be found here: InterWorx — InterWorx documentation

Documentation Changes:

Our official documentation is versioned. Accessing http://docs.interworx.com or https://appendix.interworx.com will always show documentation for the ‘current’ version. This has been updated so that it will show the documentation for IW8, by default.

Documentation for IW7 can still be found by clicking Other Versions at the bottom of the lefthand sidebar, and selecting either 7.13 or current-7.

How to Use IW8:

Note: As EL7 went EOL at the end of June, 2024, InterWorx 8 is not supported on EL7 servers.

Current IW7 servers using EL8:

• There is an in-place upgrade tool to upgrade existing IW7 servers to IW8

• The upgrade from IW7 to IW8 is an opt-in feature. Automated updates to IW8 will not occur until IW7 reaches EOL status. At this time, we do not have a date as to when IW7 will be considered EOL.

  Just as we did with IW6 and IW7, we will support both IW7 and IW8 concurrently, for now. New features will be developed only for IW8.

New Servers

To Install InterWorx 8

IW 8 can be installed on the following Operating Systems:

• RedHat Enterprise 8.x 2 64 bit Architecture
• AlmaLinux 8.x 6 64 bit Architecture
• Rocky Linux 8.x 3 64 bit Architecture
• RedHat Enterprise 9.x 2 64 bit Architecture
• AlmaLinux 9.x 6 64 bit Architecture
• Rocky Linux 9.x 3 64 bit Architecture
• NOTE: CloudLinux is not supported for IW8 at this time. We will be announcing when IW8 can be used on Cloud Linux at a later date.

1. On a new server or VPS, do a fresh, minimum install of any of the above operating systems
2. Enable quotas on the server
3. Run the InterWorx 8 installation script–please take note of the listed minimum requirements, especially if using RHEL (RHEL requires installing a few extra dependency repos, which are listed in the documentation):

   sh <((curl -sL updates.interworx.com/interworx/8/install.sh))


4. Activate your license on the new server

   Note: If you are using an existing InterWorx License, you may need to clear the license binding, first. If you are a direct customer, information on how to do so can be found here: How To: Change the IP Binding of an InterWorx License — InterWorx documentation

   If your license was provided by a reseller, they would be able to clear the binding for you, following the above doc.

• If you would like a demo key for migration purposes, just reach out to InterWorx support by submitting a ticket at https://support.interworx.com

  Or you can use this form: https://www.interworx.com/interworx-demos/

• By default all demo keys will be active for two weeks. However, this can be extended to up to four weeks–if you need the extra time, just add that information to the ticket or demo request form

If you have any questions or run into any issues, just submit a ticket to https://support.interworx.com and we will be happy to help you. We do not offer installation or migration services, but we assist as much as we can.