Recent Posts

1

Updates / Re: CWP Cannot be Installed in Alma 8 - Devel repo Issue

« Last post by Reikor on Today at 08:57:08 PM »

Today with cwp 1.7 i installed on alma linux and modsec was broken for the second line lib64 error in the conf file and because comodo waf cannot be downloaded anymore, so you need to use owasp or not useit at all.

And the second php-fpm cannot compile.
Solution in this post. https://forum.centos-webpanel.com/updates/cannot-install-php-fpm-on-alma-8-9/

2

Updates / Re: CWP Cannot be Installed in Alma 8 - Devel repo Issue

« Last post by Reikor on Today at 08:22:48 PM »

ok 2 days ago was cwp 1.6 with the problem it seems they fixed it on 1.7

3

Updates / Re: Cannot Install PHP-FPM on Alma 8 & 9

« Last post by Reikor on Today at 08:20:54 PM »

onfigure: error: Package requirements (libpng) were not met:
Package 'libpng', required by 'virtual:world', not found
PHP's ./configure uses pkg-config to locate libpng (for the GD extension). pkg-config couldn't find it, so configure aborted and the whole build died.

Root cause: libpng-devel was installed — but only the i686 (32-bit) package. A 32-bit -devel drops its pkg-config file at:


/usr/lib/pkgconfig/libpng.pc      ← 32-bit path
But on a 64-bit box, pkg-config only searches:


/usr/lib64/pkgconfig : /usr/share/pkgconfig   ← note: /usr/lib (32-bit) NOT included
So pkg-config --exists libpng returned false even though the package looked installed. (This is a CWP-on-AL9 quirk — some of its build-dep steps pull .i686 packages.)

The fix — install the x86_64 dev package so the .pc lands in the path pkg-config actually searches:


dnf -y --enablerepo=crb,epel install libpng-devel.x86_64 gd-devel postgresql-devel
Note: on AlmaLinux 9 the -devel repo is crb (CodeReady Builder), which replaced AL8's powertools. After this, /usr/lib64/pkgconfig/libpng.pc exists and pkg-config --exists libpng → OK (1.6.37), so the GD/libpng configure step passes and PHP compiles.

4

Updates / Re: 1.07 update

« Last post by Reikor on Today at 08:17:55 PM »

The second line about the lib64 was erased but then ther eis another problem with the comodo waf, because they are no longer available to download it breaks because there are no rules, so you need to use owasp or  die.

I manage to move an old comodowaf from another server.

It seems ther eis no more comod waf rulz is it?

5

CentOS-WebPanel Bugs / BUG: Subdomain creation not possible

« Last post by Painkiller88 on Today at 06:34:44 PM »

Since the update 1.4 it is no longer possible to create new subdomains or subdomains for addon domains.


I am now on CWPpro Version 1.7 and it is still not possible.

No matter what path i enter, no matter what name i give the subdomain

6

Updates / Re: Migration experience: AlmaLinux 8 to AlmaLinux 9 with CWP 1.7

« Last post by Starburst on Today at 03:52:26 PM »

Cool.
Thanks for the info.

7

Updates / Re: 1.07 update

« Last post by Starburst on Today at 03:51:38 PM »

mod sec still breaks apache, it doesnt work.

Did you fix that bug in the 2nd line?

What error is it giving?

8

Updates / Re: CWP Cannot be Installed in Alma 8 - Devel repo Issue

« Last post by Starburst on Today at 03:49:24 PM »

What does php have to do with modsec?

The problem is the complete panel is fuckt up!

I dont care modsec anymore, the poblema is no PHP version is working anda cannot update it. Installer is fuckt up.

You had asked above:

With AL8 modsec is not working.

So I was answering that part.

php_switch_v2 is working in 1.7

PHP-FPM is also working.

9

Updates / Migration experience: AlmaLinux 8 to AlmaLinux 9 with CWP 1.7

« Last post by NAZA on Today at 12:28:09 PM »

[size=150]Successful migration between two CWP 1.7 servers[/size]

Summary

I would like to share a recent experience migrating a hosting account between two servers running Control Web Panel (CWP).

The source server runs AlmaLinux 8.1 and the destination server runs AlmaLinux 9.8. Both servers run CWP 1.7.

The migration was performed using the native CWP-to-CWP migration procedure provided by the panel.

Background

The source server originally ran CentOS 7 and was later upgraded to AlmaLinux 8.1. That process was difficult and involved many problems. Each script failure was analyzed, patched, and tested until the migration was finally completed.

During the first two account migration attempts between these servers, CWP reported that the operation had completed successfully. However, manual work was still required to finish the transfers.

For the third attempt, the decision was made to use only the native CWP migration procedure and carefully verify the result afterwards.

Environment

• Source server: AlmaLinux 8.1.
• Destination server: AlmaLinux 9.8.
• CWP on both servers: version 1.7.
• CWP on both package: cwpsrv 1.24.0-2.
• Services involved: Apache, Nginx, Postfix, Dovecot, DNS, and FTP.

Migration result

CWP successfully completed the main migration stages:

• Account creation.
• Home directory transfer.
• Migration of the account structure.
• Creation of domains and subdomains.
• Creation of email accounts.
• Restoration of the associated configuration.

The account contained a static website. A comparison between the source and destination servers confirmed that the public files were present, and rsync was not required to complete the transfer.

The minor differences detected were related to CWP metadata and internal state files, not to the website content.

Database

The migration included the internal database associated with the account, managed by CWP as part of the common account structure.

No manual database work was required.

Email

The account contained eight mailboxes.

All mailboxes were created successfully on the destination server. The mailboxes were empty, except for one mailbox containing a single message. That message was also preserved during the migration.

Afterwards, the appropriate certificates had to be installed so that CWP could generate the correct mail server name for secure IMAP, POP3, and SMTP connections.

Post-migration verification

The following components were checked:

• Account files.
• Domains and subdomains.
• DNS zones.
• Apache and Nginx virtual hosts.
• Apache and Nginx configuration syntax.
• Email accounts and mailbox structure.
• TLS certificates for the mail services.

Conclusion

After two previous attempts that required manual work, the third attempt was successful using the native CWP procedure.

It was not necessary to:

• Transfer files manually with rsync.
• Modify internal CWP scripts.
• Rebuild virtual hosts manually.
• Create email accounts manually.
• Restore the account structure manually.

The manual intervention was limited to verifying the result and installing the mail certificates.

This experience shows that CWP 1.7 can successfully perform a CWP-to-CWP migration between AlmaLinux 8.1 and AlmaLinux 9.8, provided that the result is verified after restoration instead of relying solely on the “All files were copied” message.

After all the work performed on the source server since its former CentOS 7 installation, and after seeing the result of this migration, both VPSs finally provide a renewed sense of stability.

Third time lucky.

Question for the community

Has anyone else performed CWP-to-CWP migrations between AlmaLinux 8 and AlmaLinux 9 using CWP 1.7? Have you noticed differences between previous versions and the current migration procedure?

10

Updates / Re: 1.07 update

« Last post by Reikor on Today at 12:01:17 PM »

mod sec still breaks apache, it doesnt work.