<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>InterWorx</title>
	<atom:link href="https://www.interworx.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.interworx.com</link>
	<description>Web Hosting Control Panel</description>
	<lastBuildDate>Wed, 21 Oct 2026 19:36:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.11</generator>

<image>
	<url>https://www.interworx.com/wp-content/uploads/favicon.png</url>
	<title>InterWorx</title>
	<link>https://www.interworx.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>PHP Security Vunerability Updates for CVE-2026-109618 and CVE-2026-109619</title>
		<link>https://www.interworx.com/community/php-security-vunerability-updates-for-cve-2026-109618-and-cve-2026-109619/</link>
					<comments>https://www.interworx.com/community/php-security-vunerability-updates-for-cve-2026-109618-and-cve-2026-109619/#respond</comments>
		
		<dc:creator><![CDATA[Jenna Swisher]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 19:36:12 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://www.interworx.com/?p=10898</guid>

					<description><![CDATA[On October 21, 2026, PHP released updates that addressed two critical vulnerabilities: CVE-2026-109618  and CVE-2026-109619. Details can be found here: https://www.php.net/index.php#2026-10-20-1 Updating InterWorx’s Internal PHP Version<span class="excerpt-hellip"> […]</span>]]></description>
										<content:encoded><![CDATA[<p>On October 21, 2026, PHP released updates that addressed two critical vulnerabilities: CVE-2026-109618  and CVE-2026-109619. Details can be found here: <a href="https://www.php.net/index.php#2026-10-20-1">https://www.php.net/index.php#2026-10-20-1 </a></p>
<h2><b>Updating InterWorx’s Internal PHP Version</b></h2>
<p>At  2:45 EST on October 21, 2026, we released an update to the internal PHP versions for InterWorx 7 (iworxphp72-php) and InterWorx 8 (iworxphp82-php).  The updated versions are:</p>
<ul>
<li aria-level="1">InterWorx 7, on EL8: iworxphp72-php-7.2.34-114</li>
<li aria-level="1">InterWorx 8, on EL8 and EL9: iworxphp82-php-8.2.35-4</li>
</ul>
<p>Note: <b>As our public support for EL7 ended December 31, 2025, we will not be providing updates to InterWorx 7 on EL7</b>. It is recommended that any server still using EL7 migrate to a supported environment, immediately.</p>
<p>On a standard InterWorx installation, the update to the iworxphp package will be pulled in the next time the daily cron runs on the server.</p>
<p>However, <b>due to the severity of this vulnerability, we strongly recommend performing a manual update as soon as possible. </b></p>
<p>1. Log in to the server at the CLI as root, either via SSH or from the terminal</p>
<p>2. At the CLI, run the following command to check the current iworxphp version</p>
<ul>
<li aria-level="1">On InterWorx 7:
<pre>rpm -qi iworxphp72-php</pre>
</li>
<li aria-level="1">On InterWorx 8:
<pre>rpm -qi iworxphp82-php</pre>
</li>
</ul>
<p>3. If the version listed in the command output does not match the corresponding version listed, above, run the following to install the updated version:</p>
<pre>     yum clean all
     yum update *.iworx.*</pre>
<p>&nbsp;</p>
<h2><b>Updating the server and domain-level PHP versions</b></h2>
<p><b>Updates to the system PHP version, as well as the versions of PHP provided by the multiple PHP tool, are OS-level updates</b>. If OS updates are enabled in NodeWorx under Server &gt; Software Updates, updates to these versions should be pulled in during the next daily cron.</p>
<p>However, again, <b>due to the severity of the vulnerability we strongly recommend updating manually, as soon as possible.</b></p>
<p>1.  Log in to the server at the CLI as root, either via SSH or from the terminal</p>
<p>2. At the CLI, run the following:</p>
<pre>   yum clean all 
   yum update</pre>
<p><b>Any domains using a version of PHP lower than 7.4 must be moved to a more up-to-date version. </b></p>
<p>Information on managing domain-level PHP versions can be found here:</p>
<ul>
<li aria-level="1">IW8:
<ul>
<li aria-level="2">How to install versions provided by the multiple php tool (versions available are determined by OS, not InterWorx version):<a href="https://appendix.interworx.com/current/nodeworx/webserver/php_options/enable-multiple-php-nodeworx-siteworx.html#to-install-multiple-php-versions"> https://appendix.interworx.com/current/nodeworx/webserver/php_options/enable-multiple-php-nodeworx-siteworx.html#to-install-multiple-php-versions</a></li>
<li aria-level="2">How to enable multiple php versions so SiteWorx accounts have access to them:<a href="https://appendix.interworx.com/current/nodeworx/webserver/php_options/enable-php-versions-siteworx.html"> https://appendix.interworx.com/current/nodeworx/webserver/php_options/enable-php-versions-siteworx.html</a></li>
<li aria-level="2">How to change the PHP version for a domain:<a href="https://appendix.interworx.com/current/siteworx/domains_and_websites/php/change-php-versions.html"> https://appendix.interworx.com/current/siteworx/domains_and_websites/php/change-php-versions.html</a></li>
</ul>
</li>
<li aria-level="1">IW7:
<ul>
<li aria-level="2">How to  install versions provided by the multiple php tool and enable multiple php versions so SiteWorx accounts have access to them: <a href="https://appendix.interworx.com/7.14/nodeworx/webserver/php_options/enable-multiple-php-nodeworx-siteworx.html">https://appendix.interworx.com/7.14/nodeworx/webserver/php_options/enable-multiple-php-nodeworx-siteworx.html<br />
</a></li>
<li aria-level="2">How to change the PHP version for a domain: https://appendix.interworx.com/7.14/siteworx/domains_and_websites/php/change-php-versions.html</li>
</ul>
</li>
<li aria-level="1">These changes can also be made in bulk at the CLI, if needed (this documentation is the same for both InterWorx versions): <a href="https://appendix.interworx.com/current/nodeworx/webserver/php_options/how-to-make-bulk-changes-to-siteworx-account-php-versions.html">https://appendix.interworx.com/current/nodeworx/webserver/php_options/how-to-make-bulk-changes-to-siteworx-account-php-versions.html</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.interworx.com/community/php-security-vunerability-updates-for-cve-2026-109618-and-cve-2026-109619/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Automatic InterWorx 7 to InterWorx 8 Upgrades</title>
		<link>https://www.interworx.com/community/automatic-interworx-7-to-interworx-8-upgrades/</link>
					<comments>https://www.interworx.com/community/automatic-interworx-7-to-interworx-8-upgrades/#respond</comments>
		
		<dc:creator><![CDATA[Jenna Swisher]]></dc:creator>
		<pubDate>Mon, 20 Apr 2026 15:30:03 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://www.interworx.com/?p=10893</guid>

					<description><![CDATA[Automatic InterWorx 7 to InterWorx 8 Upgrades InterWorx 7 recently reached Maintenance Only status . Public support for InterWorx 7 will end on December 31, 2026.<span class="excerpt-hellip"> […]</span>]]></description>
										<content:encoded><![CDATA[<h2><b>Automatic InterWorx 7 to InterWorx 8 Upgrades</b></h2>
<p>InterWorx 7 <a href="https://forums.interworx.com/t/maintenance-only-status-for-interworx-7/24024">recently reached Maintenance Only status </a>. Public support for InterWorx 7 will end on December 31, 2026.</p>
<p>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.</p>
<p><b><i>Note: The automated upgrade will only occur for our external customers. Liquid Web and Nexcess customers’ servers will be upgraded at a later date. </i></b></p>
<h4><b>Automated update rollout procedure and timeline</b></h4>
<ul>
<li aria-level="1"><b>April-May 2026:</b> InterWorx version 7.14.4  will include a banner in NodeWorx, alerting Server Admins about the automatic upgrades
<ul>
<li aria-level="1">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</li>
</ul>
</li>
</ul>
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="1">As we have a weekly release schedule, the ETA for the progression of 7.14.4 will be as follows:</li>
</ul>
</li>
</ul>
<ul>
<li style="list-style-type: none;">
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="1"><b>Beta: </b>Week of April 20</li>
<li aria-level="1"><b>Release Candidate</b>: Week of April 27</li>
<li aria-level="1"><b>Release</b>: Week of May 4</li>
<li aria-level="1"><b>Stable</b>: Week of May 11</li>
</ul>
</li>
</ul>
</li>
</ul>
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="1">Depending on the server configuration, the banner will include the following information:
<ul>
<li aria-level="2"><b>Vanilla EL8 servers:</b> The server will automatically upgrade to InterWorx 8, the week of July 6th, 2026</li>
</ul>
</li>
</ul>
</li>
</ul>
<ul>
<li style="list-style-type: none;">
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="2"><b>EL7, CloudLinux, Litespeed, and clustered servers: </b>The automatic upgrade to InterWorx 8 is not supported for the server.</li>
</ul>
</li>
</ul>
</li>
<li aria-level="1"> <b>July 6-9, 2026:</b> Servers that meet the criteria to automatically upgrade to InterWorx 8 will do so</li>
<li aria-level="1"><b>July 13, 2026:</b> 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</li>
</ul>
<h4><b>What actions should be taken?</b></h4>
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="1">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</li>
<li aria-level="1">If you would like more control over updating from IW7 to IW8, we recommend using the in-place upgrade tool, prior to July 6th:<a href="https://appendix.interworx.com/current-7/nodeworx/general/other/iw7-to-iw8-upgrade.html"> Upgrading from InterWorx 7.x to InterWorx 8.x — InterWorx documentation</a></li>
</ul>
</li>
</ul>
<ul>
<li aria-level="1"><b>Customers that are using CloudLinux, Litespeed, or clustering, or are still on an EL7 OS, will not receive the automatic upgrade to InterWorx 8</b></li>
</ul>
<ul>
<li style="list-style-type: none;">
<ul>
<li aria-level="2"> EL8 CloudLinux, Litespeed and clustered servers will need to migrate to a supported version before InterWorx 7 reaches EOL status on December 31, 2026.</li>
<li aria-level="2">As public support for EL7 ended at the beginning of this year, those servers must be migrated to a supported environment, immediately</li>
</ul>
</li>
</ul>
<h4><b>Things to know: </b></h4>
<p><b>The automatic upgrade to InterWorx 8 will include the following new features:</b></p>
<ul>
<li aria-level="1">Refreshed GUI</li>
<li aria-level="1">New UI sidebar, with detailed information and documentation links for forms and tasks</li>
<li aria-level="1"><a href="https://appendix.interworx.com/current/nodeworx/account_management/siteworx/imports/import-interworx-hosting-accounts.html#using-the-migration-tool">Improved Migration tool</a>, which includes incremental imports and re-syncs, DNS updates, and other tools to assist with migrations</li>
<li aria-level="1"><a href="https://appendix.interworx.com/current/siteworx/domains_and_websites/domain_management/add-delete-secondary-domains.html#to-edit-a-secondary-domain">Ability to change the docroot of primary or secondary domains via the GUI</a></li>
<li aria-level="1"><a href="https://appendix.interworx.com/current/siteworx/domains_and_websites/domain_management/add-edit-delete-subdomains.html#to-edit-a-subdomain">Ability to manage a Subdomain’s docroot and PHP version from the GUI</a></li>
<li aria-level="1"><a href="https://appendix.interworx.com/current/siteworx/domains_and_websites/domain_management/advanced-domain-options.html">Advanced domain configuration options via the GUI</a></li>
</ul>
<p><b>Other Notable Changes:</b></p>
<ul>
<li aria-level="1">Horde is no longer a webmail option, as it does not support the new internal PHP version of PHP 8.2</li>
<li aria-level="1">Webalizer was removed as a statistics option</li>
</ul>
<h4><b>Troubleshooting</b></h4>
<p>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:</p>
<ul>
<li aria-level="1"><b>The httpd syntax is error free</b>: If there are any syntax errors in Apache confs or  vhosts, this will fail</li>
<li aria-level="1"><b>LiteSpeed is not enabled</b>: 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</li>
<li aria-level="1"><b>CloudLinux is not enabled</b>: This upgrade cannot occur on servers running CloudLinux. Those accounts must be imported to a new server with IW8 installed</li>
<li aria-level="1"><b>The server is not part of a cluster</b>: 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</li>
<li aria-level="1"><b>Yum dry run</b>: This checks to make sure that yum is up and running</li>
<li aria-level="1"><b>The server is up to date</b>: This makes sure that the server is up to date</li>
<li aria-level="1"><b>Server is running EOL OS version</b>: 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:<a href="https://appendix.interworx.com/current/getting_started/setup_information/requirements-interworx-control-panel.html"> What are the system requirements of InterWorx Control Panel? — InterWorx documentation</a></li>
<li aria-level="1"><b>Server is using Dovecot Submission</b>: 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:<a href="https://forums.interworx.com/t/dovecot-and-php-intl-required-for-roundcube-1-5-3/23224"> Dovecot and php-intl required for Roundcube 1.5.3</a></li>
</ul>
<p><b>If, on July 13th, the banner states that the upgrade to InteWorx 8 could not complete: </b></p>
<ul>
<li aria-level="1">Check the Preflight Checklist for any triggered flags
<ul>
<li aria-level="2">Navigate to <b>Server &gt; Software Updates</b></li>
<li aria-level="2">At the very bottom of the page is a section called <b>Major Version Upgrade</b>. Click <b>Go to Updates Page</b>.That will take you to the Preflight Checklist.</li>
</ul>
</li>
</ul>
<ul>
<li aria-level="1">If the preflight checklist does not show any triggered flags, check to make sure that the daily cron ran between July 6-9
<ul>
<li aria-level="2">The timestamp on ~iworx/var/last_daily  indicates the last time the daily cron successfully completed.  Example:
<p><code>[root@server ~]# ls -la ~iworx/var/last_daily<br />
-rw------- 1 root root 0 April 13 18:43 /home/interworx/var/last_daily<br />
[root@server ~]#</code></li>
</ul>
</li>
</ul>
<ul>
<li aria-level="1">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</li>
</ul>
<p>&nbsp;</p>
<p>If you have any questions, or run into any issues, don’t hesitate to reach out to us at<a href="https://support.interworx.com/"> https://support.interworx.com</a>. We will be happy to assist.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.interworx.com/community/automatic-interworx-7-to-interworx-8-upgrades/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Maintenance Only Status for InterWorx 7</title>
		<link>https://www.interworx.com/community/maintenance-only-status-for-interworx-7/</link>
					<comments>https://www.interworx.com/community/maintenance-only-status-for-interworx-7/#respond</comments>
		
		<dc:creator><![CDATA[Jenna Swisher]]></dc:creator>
		<pubDate>Tue, 07 Apr 2026 18:27:10 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://www.interworx.com/?p=10889</guid>

					<description><![CDATA[Maintenance Only Status for InterWorx 7 InterWorx 7 officially reached Maintenance Only/Deprecated status as of April 7, 2026. What does this mean? As of now, we<span class="excerpt-hellip"> […]</span>]]></description>
										<content:encoded><![CDATA[<h2>Maintenance Only Status for InterWorx 7</h2>
<p>InterWorx 7 officially reached Maintenance Only/Deprecated status as of April 7, 2026.</p>
<p><strong>What does this mean?</strong></p>
<p>As of now, we will no longer be providing updates to InterWorx 7, outside of security and bug fixes.</p>
<p><strong>When will InterWorx 7 go EOL?</strong></p>
<p>Public support for InterWorx 7 will end December 31, 2026.</p>
<p><strong>What actions should be taken?</strong></p>
<ul>
<li>Customers who are still using InterWorx 7 on EL7 servers will need to migrate to a supported environment.
<p>Support for EL7 ended January 1st, 2026, and updating to InterWorx 8 is not possible on an EOL OS. Details can be found here: <a class="inline-onebox" href="https://forums.interworx.com/t/public-support-for-el7-ending-january-1-2026/23996">Public Support for EL7 ending January 1, 2026</a></p>
<p>If you would like a demo key to facilitate the migration, feel free to reach out to us at <a href="http://support.interworx.com">support.interworx.com</a></li>
<li>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</li>
<li>If you would like more control over updating from IW7 to IW8, we recommend using the in-place upgrade tool: <a class="inline-onebox" href="https://appendix.interworx.com/current-7/nodeworx/general/other/iw7-to-iw8-upgrade.html">Upgrading from InterWorx 7.x to InterWorx 8.x — InterWorx documentation</a></li>
</ul>
<p>If you have any questions or run into any issues, please submit a ticket to <a href="https://support.interworx.com">https://support.interworx.com</a> and we will be happy to help you. We do not offer installation or migration services, but we assist as much as we can.</p>
<p>Information on service deprecation and removals can be found here: <a class="inline-onebox" href="https://appendix.interworx.com/current/deprecations.html">Deprecation Plan — InterWorx documentation</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.interworx.com/community/maintenance-only-status-for-interworx-7/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Public Support for EL7 ending January 1, 2026</title>
		<link>https://www.interworx.com/community/public-support-for-el7-ending-january-1-2026/</link>
					<comments>https://www.interworx.com/community/public-support-for-el7-ending-january-1-2026/#respond</comments>
		
		<dc:creator><![CDATA[Jenna Swisher]]></dc:creator>
		<pubDate>Tue, 04 Nov 2025 18:17:48 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://www.interworx.com/?p=10883</guid>

					<description><![CDATA[Public Support for EL7 ending January 1, 2026 EL7 reached EOL status June 30, 2024: What to know about CentOS Linux EOL While we will continue<span class="excerpt-hellip"> […]</span>]]></description>
										<content:encoded><![CDATA[<p><strong>Public Support for EL7 ending January 1, 2026</strong></p>
<p>EL7 reached EOL status June 30, 2024: <a class="inline-onebox" href="https://www.redhat.com/en/topics/linux/centos-linux-eol">What to know about CentOS Linux EOL</a></p>
<p><strong>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.</strong></p>
<p>After January 1, InterWorx will continue to run on EL7 servers, and the license will still be valid.</p>
<p>However, <strong>InterWorx support will be limited to only the following two topics:</strong></p>
<ul>
<li>Issues that may arise during a migration to a new server running supported OS</li>
<li>If the issue is a bug within InterWorx</li>
</ul>
<p><strong>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.</strong></p>
<p>Information on supported OSes can be found here:<a href="https://appendix.interworx.com/current/getting_started/setup_information/requirements-interworx-control-panel.html#supported-operating-systems"> What are the system requirements of InterWorx Control Panel? — InterWorx documentation</a></p>
<p><strong>Things to note:</strong></p>
<ul>
<li>If you would like a demo key to facilitate the migration, just reach out to InterWorx support by submitting a ticket here:<a href="https://support.interworx.com"> https://support.interworx.com</a> .
<p>Or you can use this form:<a href="https://www.interworx.com/interworx-demos/"> https://www.interworx.com/interworx-demos/</a></p>
<p>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:</li>
<li>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</li>
<li>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</li>
<li>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:<a href="https://appendix.interworx.com/current/nodeworx/general/license_management/change-license-binding.html"> How to: Change the IP Binding of an InterWorx License — InterWorx documentation</a></li>
<li>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<a href="https://support.interworx.com"> https://support.interworx.com</a> with the license key information, and we will manually clear the license binding for you.</li>
</ul>
<p>Information on how to migrate accounts to the new server can be found here:<a href="https://appendix.interworx.com/current/nodeworx/account_management/siteworx/imports/import-interworx-hosting-accounts.html"> How to: Import Hosting Accounts to InterWorx — InterWorx documentation</a></p>
<p>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.</p>
<p>If you have any questions or run into any issues, just submit a ticket to<a href="https://support.interworx.com"> https://support.interworx.com</a> and we will be happy to help you. We do not offer installation or migration services, but we assist as much as we can. <img decoding="async" class="emoji" title=":slight_smile:" src="https://forums.interworx.com/images/emoji/twitter/slight_smile.png?v=14" alt=":slight_smile:" width="20" height="20" /></p>
<p>Information on service deprecation and removals can be found here:<a href="https://appendix.interworx.com/current/deprecations.html"> Deprecation Plan — InterWorx documentation</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.interworx.com/community/public-support-for-el7-ending-january-1-2026/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>InterWorx 8 on CloudLinux Support</title>
		<link>https://www.interworx.com/community/interworx-8-on-cloudlinux-support/</link>
					<comments>https://www.interworx.com/community/interworx-8-on-cloudlinux-support/#respond</comments>
		
		<dc:creator><![CDATA[Jenna Swisher]]></dc:creator>
		<pubDate>Mon, 07 Jul 2025 16:02:03 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://www.interworx.com/?p=10874</guid>

					<description><![CDATA[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<span class="excerpt-hellip"> […]</span>]]></description>
										<content:encoded><![CDATA[<div class="cooked">
<p><strong>InterWorx 8 on CloudLinux Support</strong></p>
<p>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.</p>
<p>To use CloudLinux, InterWorx 8 must first be installed on RHEL 8 or 9, AlmaLinux 8 or 9, or Rocky Linux 8 or 9.</p>
<p>Once InterWorx is installed, the server can be converted to CloudLinux via <a href="https://appendix.interworx.com/current/nodeworx/plugins/install-use-cloudlinux-plugin-interworx.html">the CloudLinux plugin</a>.</p>
<p>Note: <strong>CloudLinux 9 support is ONLY for InterWorx 8</strong>. InterWorx 7 does not support CloudLinux 9.</p>
<p>If you have any questions or run into any issues, just submit a ticket to <a href="https://support.interworx.com">https://support.interworx.com</a> 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.</p>
</div>
]]></content:encoded>
					
					<wfw:commentRss>https://www.interworx.com/community/interworx-8-on-cloudlinux-support/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
