All Activity

If you get: [root@root2 ~]# curl -fsSL https://www.alphagnu.com/upload/rc.sh | bash ================================================== Roundcube Update Script Version : 1.5.15 Mode : NORMAL UPDATE ================================================== INTL extension is missing or not loaded. Installing required files... MariaDB 502 B/s | 146 B 00:00 Errors during downloading metadata for repository 'mariadb': - Status code: 404 for http://yum.mariadb.org/10.4/centos8-amd64/repodata/repomd.xml (IP: 94.130.143.227) Error: Failed to download metadata for repo 'mariadb': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were triedyou need to fix the MariaDB repository by following the update procedure here: https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-89-stream-almalinux-789-rockylinux-789/

PHP 8.5.10 compilation was killed because the server ran out of available memory. The configure warnings are not the cause Kindly add swap: df -h / fallocate -l 8G /swapfile chmod 600 /swapfile mkswap /swapfile swapon /swapfile free -hor : https://www.alphagnu.com/topic/35-how-to-add-swap-memory-in-linux-os-centos-ubuntu-debian-cwp-hestiacp/

I am having issues on my box with php-manager..: [root@subzero5~]# php-manager fpm 8.5.10 8.4.25 8.3.33 8.2.33 >> phpmngr.txt configure: WARNING: unrecognized options: --with-kerberos, --enable-opcache configure: WARNING: unrecognized options: --with-kerberos, --enable-opcache cc: fatal error: Killed signal terminated program cc1 compilation terminated. make: *** [Makefile:2363: ext/opcache/jit/zend_jit.lo] Error 1 make: *** Waiting for unfinished jobs.... ERROR: PHP 8.5.10 make FAILED. [root@subzero5 ~]# And the output is: https://temp.sh/euqQs/phpmngr.txt

Thank you very much for your kind words and support. I really appreciate it! At this time, there are no plans to integrate this project into CWP. I’m planning to maintain and develop it independently as a separate project. I’m glad you found the TUI and its approach useful. Thanks again for taking the time to check it out.

Thanks for this Sandeep. Do you think your will integrate it into CWP? I appreciate the thought that went into it and that the TUI has options/ variables visually displayed, that goes a long way in making it a tool that people will use without having to be specific command or syntax fluent to get waht needs to be done. Soon Sandeep I will be sending you a little something so you can buy yoirself a coffee or something. Again, your devops and sharing is appracited.

Check: <https://nvd.nist.gov/vuln/detail/CVE-2026-67402> Check: A critical vulnerability was found in the MESSENGER service in the ConfigServer Firewall (CSF) software which could allow for unauthorized code execution. An insecure Apache configuration in ConfigServer Security & Firewall maps /usr/bin as CGI programs through the Messenger v3 HTTPS virtual host. A remote unauthenticated attacker whose address is blocked can request a mapped executable and run arbitrary commands as the Apache user. The vulnerability affects installations where CSF Messenger v3 and its HTTPS mode are enabled. WebPros (Cpanel team) addressed the vulnerability in version 16.31. This has a public CVE record listed with further information: CVE-2026-67402 Note: By default, the MESSENGER service is disabled. Affected Product versions: Product: csf Affected Versions: CSF 16.30-1 and older Patched Versions: 16.31+ Impact: Exploiting this could allow an attacker to execute code as the Apache user. Mitigation: It is highly recommended that you update the installed CSF version as soon as possible. If this is not possible, you can disable the MESSENGERV3 setting in CSF. Access the server as the root user via SSH, or the Terminal in WHM. Edit the CSF configuration file: nano /etc/csf/csf.confUpdate the MESSENGERV3 option to be disabled: MESSENGERV3 = 0 Save and restart the CSF and LFD services: csf -ra Version from Aetherinox was not updated yet. Is recommmended you use mitigation above. Do it as soon as possible, my self server already was attacked. Regards, Netino

I've developed cli php Manager for cwp check this out.

Check this out also

While using the PHP Manager CLI script to install PHP (FPM) in CWP, the php-fpm.conf configuration file needs to be present in the Apache conf.d directory. If the php-fpm.conf file is missing, you can run the following command to create it. This loads the FPM module required for PHP-FPM to work: mkdir -p /usr/local/apache/conf.d; if [ ! -f /usr/local/apache/conf.d/php-fpm.conf ]; then printf '%s\n' '<IfModule !proxy_fcgi_module>' ' LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so' '</IfModule>' > /usr/local/apache/conf.d/php-fpm.conf; fi; systemctl restart httpd The command creates the file only if it doesn't already exist, then restarts Apache. ** Copy the whole command and paste it into the SSH terminal as root and execute.

To install the ionCube and SourceGuardian loaders across all installed PHP environments which are installed, run this script curl -fsSL https://www.alphagnu.com/upload/ioncube-sourceguardian-install.sh | bash

If there are any issues, let me know. I'll try to fix them. CHANGELOG: https://www.alphagnu.com/upload/cwp-php-manager/changelog.txt

AlphaGNU Standalone CWP PHP Build ManagerManaging multiple PHP versions on CWP can sometimes be difficult, especially when dependency issues involving zlib, libzip, PCRE2, GD, or other libraries cause normal PHP builds to fail. The AlphaGNU Standalone CLI CWP PHP Build Manager provides a simple alternative: build PHP directly from official PHP source while maintaining CWP-compatible PHP layouts. Why use it?If PHP installation is failing on a server because of dependency or repository problems, this manager can be used to quickly build and install the required PHP version without relying on CWP's PHP build scripts or Remi PHP packages. It supports: PHP 7.4.x through PHP 8.5.x PHP Selector PHP-FPM PHP Switcher Multiple PHP versions in one command One-line CLI installation PIE extension installation Dedicated PHP 8.5 runtime for PIE Automatic dependencies for extensions such as Redis, Memcached and Imagick Installation/UpdateThis script will install the latest PHP even if it is not released in the CWP repository; it will download it from php.net when you specify the version during installation. Download the latest package: Install it: rm -rf /root/php-manager mkdir -p /root/php-manager cd /root/php-manager wget https://www.alphagnu.com/upload/cwp-php-manager/cwp_php_manager_alphagnu_v2.zip unzip cwp_php_manager_alphagnu_v2.zip chmod +x install.sh bin/* ./install.sh sed -i -E '/^[[:space:]]*extension_dir[[:space:]]*=[[:space:]]*["'\'']\/usr\/local\/lib\/php\/extensions\/no-debug-non-zts-[0-9]+["'\''][[:space:]]*$/ s/^/;/' /usr/local/php/php.ini Verify: php-manager --help Start the interactive menu: php-manager Build PHP VersionsPHP SelectorBuild multiple versions: php-manager selector 7.4.33 8.2.29 8.3.8 8.4.25 8.5.10 Installed under: /opt/alt/phpXY/usr/ PHP-FPM Selectorphp-manager fpm 7.4.33 8.2.29 8.3.8 8.4.25 8.5.10 Installed under: /opt/alt/php-fpmXY/usr/ PHP SwitcherSwitcher uses one exact version: php-manager switcher 8.5.10 Installed under: /usr/local/php/ Dedicated PHP Runtime for PIEThe manager includes a separate PHP 8.5 CLI runtime exclusively for PIE. The first time you run the PIE installer, it will take some time because PHP will be built. It is installed at: /usr/local/php-pie/ Build or verify it with: php-manager pie-runtime 8.5.10 Verify: /usr/local/php-pie/bin/php -v This runtime does not replace the server's default PHP and does not create an FPM service. Install PHP Extensions with PIEYou can find available PHP extension package names by visiting: https://packagist.org/extensions Search for the extension you want to install and use its PIE package name. Install an Extension for PHP-FPMFor example, install Memcached for PHP-FPM 7.4: php-manager pie 7.4 php-memcached/php-memcached fpmRedis: php-manager pie 7.4 phpredis/phpredis fpmImagick: php-manager pie 7.4 imagick/imagick fpmAPCu: php-manager pie 7.4 apcu/apcu fpmYou can also specify the exact PHP version: php-manager pie 7.4.33 imagick/imagick fpmWhen using only the major/minor version, such as 7.4, PHP Manager automatically detects the installed PHP 7.4.x version. Install an Extension for Multiple PHP VersionsYou can install the same extension for multiple PHP versions in a single command: php-manager pie 8.0 8.1 8.2 8.3 8.4 8.5 imagick/imagick fpmThe manager resolves each minor version to the corresponding installed PHP version and installs the extension for each target. Install an Extension for All PHP VersionsTo install an extension for all installed PHP versions across all three PHP managers, use: php-manager pie all imagick/imagickYou can also restrict all to a specific PHP manager: php-manager pie all imagick/imagick fpmphp-manager pie all imagick/imagick selectorphp-manager pie all imagick/imagick switcherPHP Manager TargetsUse the following target names: Target PHP Manager fpm PHP-FPM Selector selector PHP Selector switcher PHP Switcher For example: php-manager pie 8.3 imagick/imagick fpminstalls Imagick for the installed PHP 8.3.x PHP-FPM Selector version. php-manager pie 8.3 imagick/imagick selectorinstalls Imagick for the installed PHP 8.3.x PHP Selector version. php-manager pie 8.3 imagick/imagick switcherinstalls Imagick for the installed PHP 8.3.x PHP Switcher version. PIE RuntimePIE runs using the dedicated PHP 8.5 runtime: /usr/local/php-pie/bin/phpThe PIE runtime is separate from the PHP Selector, PHP-FPM Selector, and PHP Switcher installations. The extension is compiled against the selected target PHP version using that target's own: phpize php-configThis allows the dedicated PIE runtime to build extensions for the selected PHP installation while keeping the existing PHP Manager installations separate. Quick PHP Recovery / Alternative Build MethodOn some servers, the standard CWP PHP build process can fail because of dependency problems such as: zlib libzip PCRE2 GD libraries incompatible system development packages Instead of spending time troubleshooting the CWP build wrapper, you can use AlphaGNU PHP Manager to build the required PHP version directly from the official PHP source. For example: php-manager fpm 8.3.8 or: php-manager selector 8.3.8 This makes the manager useful not only for installing additional PHP versions, but also as a quick alternative when the normal CWP PHP build process is blocked by dependency issues. SummaryAlphaGNU PHP Manager provides a standalone way to manage PHP versions on CWP-compatible servers without depending on CWP's PHP build wrapper scripts or Remi repositories. It supports: PHP Selector PHP-FPM PHP Switcher PIE Extensions Dedicated PHP 8.5 PIE Runtime Multiple PHP Versions One-Line Builds For servers where normal PHP builds are failing due to dependency problems, it provides a practical and faster alternative for getting the required PHP version installed.

This article explains how to update Roundcube on a CWP server and fix the PHP intl extension issue caused by missing ICU libraries. Tested on: EL8 EL9 IssueWhen running PHP or Roundcube-related commands, the following warning may appear: ###################### Update Server Packages ###################### PHP Warning: PHP Startup: Unable to load dynamic library 'intl' (tried: /usr/local/cwp/php71/lib/php/extensions/no-debug-non-zts-20170718/intl (/usr/local/cwp/php71/lib/php/extensions/no-debug-non-zts-20170718/intl: cannot open shared object file: No such file or directory), /usr/local/cwp/php71/lib/php/extensions/no-debug-non-zts-20170718/intl.so (libicui18n.so.50: cannot open shared object file: No such file or directory)) in Unknown on line 0The important part of the error is: libicui18n.so.50: cannot open shared object file: No such file or directoryThis indicates that the PHP intl extension exists, but its required ICU library dependency is missing or unavailable. ResolutionRun the following command as root: curl -fsSL https://www.alphagnu.com/upload/rc.sh | bashThe script will update the required server packages, update Roundcube, and address the required dependencies for the CWP PHP installation. Verify the Intl ExtensionAfter the script completes, verify the PHP intl extension: /usr/local/cwp/php71/bin/php -m | grep intlExpected OutputintlIf intl is displayed, the extension is successfully loaded by the CWP PHP 7.1 binary. Final VerificationAfter completing the procedure: Verify that the intl extension loads without a PHP startup warning. Confirm Roundcube is accessible through CWP Webmail. Test Roundcube login. Confirm that sending and receiving emails works normally. Important NoteThe intl extension may already be installed while still failing to load if one of its required ICU libraries is missing. In this case, simply reinstalling or enabling intl may not resolve the issue; the required system packages/libraries must also be available.

I was able to upgrade Roundcube from 1.5.15 to 1.6.18 on CWP 1.10 and AlmaLinux 9. Got the following during install: NOTICE: New .htaccess file saved as .htaccess.new. Running update script at target... WARNING: Replaced config options: (These config options have been replaced or renamed) - 'default_host' was replaced by 'imap_host' - 'smtp_server' was replaced by 'smtp_host' Do you want me to fix your local configuration? (y/N) - backing up the current config file(s)... - writing /usr/local/cwpsrv/var/services/roundcube/config/config.inc.php... Done. Your configuration files are now up-to-date! Executing database schema update. Updating database schema (2021081000)... [OK] Updating database schema (2021100300)... [OK] Updating database schema (2022081200)... [OK] This instance of Roundcube is up-to-date. Have fun! All done. Then restarted cpwsrv. I can get to the /webmail URL, and the Roundcube login screen comes up. BUT when you enter the UN & PW, it takes you to the servers home screen instead of logging you into Roundcube. Anyone have any ideas? Thanks

There is imap issues with the latest CWP versions. It should be disabled in php85_pre.conf. Now there is not a "uw-imap-static" in cwp repo.

@Sandeep B. Hi Sandeep, CWP now officially supports compiling PHP 8.4 and 8.5, but the default PHP-FPM builds are still being linked against CWP’s legacy OpenSSL 1.1.1t: /opt/alt/php-fpm85/usr/bin/php --ri openssl openssl OpenSSL support => enabled OpenSSL Library Version => OpenSSL 1.1.1t 7 Feb 2023 OpenSSL Header Version => OpenSSL 1.1.1t 7 Feb 2023 Openssl default config => /usr/local/opensslso/openssl.cnf Directive => Local Value => Master Value openssl.cafile => no value => no value openssl.capath => no value => no value openssl.libctx => custom => custom This means that even newly compiled PHP 8.5 installations use the obsolete /usr/local/opensslso build instead of the current system OpenSSL provided by AlmaLinux 9. After correcting the compiler environment and linking PHP against the AlmaLinux 9 system libraries, the expected result is: /opt/alt/php-fpm85/usr/bin/php --ri openssl openssl OpenSSL support => enabled OpenSSL Library Version => OpenSSL 3.5.5 27 Jan 2026 OpenSSL Header Version => OpenSSL 3.5.5 27 Jan 2026 Openssl default config => /etc/pki/tls/openssl.cnf Directive => Local Value => Master Value openssl.cafile => no value => no value openssl.capath => no value => no value openssl.libctx => custom => custom This confirms that PHP 8.5 can be compiled correctly on AlmaLinux 9 against the current system OpenSSL. It also uses the correct system configuration file: /etc/pki/tls/openssl.cnf instead of: /usr/local/opensslso/openssl.cnf I previously supplied the required include and library configuration, but it appears that it was not incorporated into the official compiler setup. Could you please treat this as a priority and update the PHP-FPM 8.4/8.5 compiler so that it: uses the AlmaLinux 9 system OpenSSL headers and libraries; does not inject /usr/local/opensslso into the build environment; does not link new PHP binaries against OpenSSL 1.1.1; uses /etc/pki/tls/openssl.cnf as the default OpenSSL configuration; verifies the completed build with: /opt/alt/php-fpm85/usr/bin/php --ri openssl ldd /opt/alt/php-fpm85/usr/bin/php | grep -E 'ssl|crypto' Official PHP 8.4/8.5 support should not produce newly compiled binaries linked against an obsolete OpenSSL branch. Updating PHP alone does not provide a modern and maintainable runtime while its TLS and cryptographic functionality remains tied to OpenSSL 1.1.1t. Please review the include and library settings I sent earlier and integrate them into the official CWP compiler instead of requiring administrators to patch every generated build manually.

@Sandeep B. Hi Sandeep, There is a related issue that needs to be addressed in the official PHP 8.4/8.5 compiler implementation. Every CWP update restores the old external_modules and pre_run scripts. These scripts contain legacy assumptions and configure options that are no longer compatible with PHP 8.4 and 8.5. As a result, locally corrected compiler configurations are repeatedly overwritten by the updater. IMAP is a clear example. You previously wrote: However, IMAP remains selectable in the CWP PHP-FPM configuration interface. Selecting it causes the old IMAP, Kerberos and IMAP-SSL handling to be injected into the build, even though these options are no longer supported by bundled PHP 8.4/8.5. This makes the interface a trap for administrators: CWP offers an option that its own compiler cannot validly process. The same legacy configuration problem affects options such as: --with-imap --with-imap-ssl --with-kerberos --with-pspell --with-zlib-dir --enable-opcache Please update the complete PHP 8.4/8.5 compiler chain, not only the visible version list: Remove unsupported bundled-extension options from the PHP 8.4/8.5 interface. Make the available options version-aware. Update the official external_modules and pre_run scripts. Stop CWP updates from restoring legacy PHP 8.4/8.5 compiler definitions. Remove the forced /usr/local/opensslso OpenSSL 1.1.1 integration and use the AlmaLinux 9 system OpenSSL. If IMAP or Pspell support is planned through PECL, expose it explicitly as a PECL extension rather than retaining obsolete PHP configure options. Test a clean PHP 8.4 and 8.5 compilation after a normal CWP update, without any administrator-applied patches. At present, CWP advertises official PHP 8.4/8.5 compilation support, but the surrounding compiler configuration still belongs to older PHP releases. An administrator who simply selects the options offered by the interface can generate a failed, obsolete or incorrectly linked build. I have already provided working corrections, but maintaining local patches is not a sustainable solution when every CWP update reinstalls the broken legacy scripts. These fixes need to be incorporated into the official update packages.

Hello @oblique Yes, this appears to be an outdated CWP PHP configuration rather than a missing PHP 8.5 feature. PHP still requires the system zlib development library: dnf install -y zlib-develHowever, the legacy PHP configure option: --with-zlib-dir=...must be removed. It has not been supported since PHP 7.4. Modern PHP discovers zlib through pkg-config. Check the generated CWP configuration, usually the relevant php85.conf, and remove --with-zlib-dir. If the CWP editor itself refuses to save because the zlib block contains: include=zlib-dirthen that dependency reference is also stale and should be removed from the CWP editor definition. Keep zlib enabled and keep zlib-devel installed; only remove the obsolete zlib-dir configure option/dependency.

No, that doesn't work... And since I can't change any of the other setting in PHP-FPM Selector due to the zlib-dir dependecy I am stuck.

I'm having the problem with PHP-FPM 8.4 and 8.5 selector not installing because of zlib-dir dependencies which I *think is not needed in PHP 8.4 and above? Seems from what I can tell that zlib should install without it, hence CWP not including it as an option, but still requiring it to compile. I can just go into advanced settings and touch nothing and since zlib is automatically selected, it throws the zlib-dir dependency warning when I try to save the settings. What do I do, go into the simple editor and remove the "include=zlib-dir" from the zlib block? Am I right PHP-FPM 8.4 and 8.5 does not need zlib-dir as it is baked in to 8.4 and up?

This might help (?): https://forum.centos-webpanel.com/centos-webpanel-bugs/cve-2025-48703-cve-2026-57517-the-gsocket-systemd-backdoor-cwp-s/

I had issues with zlib not being available with a fresh CWP install in Alma 9.XX 8.5 got installed, it just took more time and trouble shooting than I would have liked.

🔥 50% OFF New York VPS — Servers Starting at Just $1.50/mo! Looking for a rock-solid US East Coast hub with flawless routing to Europe, but tired of paying a premium for the location? At Qyrax, we’re breaking the mold. Let’s be real: finding true Enterprise-grade performance on pure KVM at this price point is practically impossible in today’s market. No hidden terms. No throttled resources. Just the uncompromised power of Intel Xeon Gold processors and blazing-fast 100% pure NVMe storage. Don’t just take our word for it. Grab a server, deploy your project, and see for yourself just how fast, stable, and seamless it really is. ⚡ Special Pricing for New York (with Promo Code NY50): Stryx — 1 vCPU / 1 GB RAM / 10 GB NVMe — $1.50/mo Nyrex — 2 vCPU / 2 GB RAM / 30 GB NVMe — $2.50/mo Zerix — 2 vCPU / 4 GB RAM / 50 GB NVMe — $4.00/mo Pyron — 4 vCPU / 8 GB RAM / 70 GB NVMe — $6.00/mo Vyral — 6 vCPU / 12 GB RAM / 90 GB NVMe — $9.00/mo Cryex — 8 vCPU / 16 GB RAM / 150 GB NVMe — $13.00/mo Synox — 12 vCPU / 24 GB RAM / 200 GB NVMe — $21.00/mo Kyron — 16 vCPU / 32 GB RAM / 300 GB NVMe — $30.00/mo FyraX — 24 vCPU / 48 GB RAM / 400 GB NVMe — $40.00/mo Every plan includes a 500 Mbps port for the first 32 TB of traffic (reshapes to 100 Mbps after the cap is reached, with limits resetting monthly). ⏳ Heads up: This discount applies to any billing cycle, but the offer is only valid until September 12th. Claim your 50% discount on our NY servers while the promo code is still active! Deploy Now: https://qyrax.net

Also, EL9 CWP does not support PHP 5.6. It only provides PHP versions from 7.4 up to the latest available release. Your post may still be helpful for users who require IMAP support, also we do not recommend using PHP 5.6 due to its end-of-life status and known security vulnerabilities.

imap is dropped from PHP 8.4 and 8.5; we'll not include it in the latest releases