Messages

1

Information / Re: Possible CWP Security Issue – Malicious JavaScript Injection

« on: August 27, 2026, 01:03:52 PM »

In response to overseer ... Big Thanks for the advice!..:..

Trying to add to the forum here as well.

The access_log was over 3 gbs in size.
...
Is it safe to delete these two periodically on my own?

My advice:

Code: [Select]

truncate -s0 /usr/local/cwpsrv/logs/access_log
truncate -s0 /usr/local/cwpsrv/logs/error_logThen look at File Management >  Logrotate Manager and add a rotation job for those files.

Added the following conf file into the log rotation tool

/usr/local/cwpsrv/logs/*_log {
    daily
    missingok
    notifempty
    rotate 14
    compress
    delaycompress
    copytruncate
}

This is tested and working. Use/edit  it at your own risk Notice the copytruncate at the end...learned the hard way that was needed, without it the the cwp process seemed to hold the file and continued writing into the copied file, not a good thing., The log rotation cron then did not create the log file. I am guessing that with a service bounce the original log file would be created.

Hope that this helps someone

2

Information / Re: Possible CWP Security Issue – Malicious JavaScript Injection

« on: August 25, 2026, 09:39:18 PM »

Looking for advice here:

When I looked at these two cwp server logfiles:

 /usr/local/cwpsrv/logs/access_log*
/usr/local/cwpsrv/logs/error_log*

The access_log was over 3 gbs in size.

I scanned through these and saw no malicious offenders...I keep th cwp browser open all the time and I could see periodic updates into the file.

Looks like these have grown over the years, and it appears that they are on no log rotation.

Is it safe to delete these two periodically on my own?

3

Information / Re: CWP: What is the future of the project? Is it still the right choice?

« on: August 02, 2026, 10:10:12 PM »

Also crontab selection for users hangs as well.

Easy fix to ssh in and then sudo, but it would be nice to see all the cron entries via the cwp display.

Should be added to the fix list.

Confirming 1.7 just came through.

I am sticking with CWP, trying to help get it back on track over these long summer days.

4

CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404

« on: July 31, 2026, 12:12:11 PM »

Update - CWP installs are now at 1.6 (automatic) and yum updates on new display appear to be working.

5

CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404

« on: July 31, 2026, 01:58:39 AM »

 Still looping when trying to perform the cwp update 60 1.6.

Using update from the admin (2013) display as well as /scripts/update_cwp execution.

Hanging on update server packages in the ssh cli.

Passing on status...

6

CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404

« on: July 29, 2026, 01:07:09 PM »

Any word on the patch implementation timeline.

+1

7

Other / root ssh authorized_keys file has been deleted and password login allowed

« on: July 23, 2026, 08:39:53 PM »

After a 3 week vacation just tried to login as root to my cwppro servers.

In all cases the authorized_keys file in the .ssh file has been deleted breaking the familiar connection.

Also on all servers password login was disabled by me believing this to be a more secure setting.

It looks as though the /etc/sshd/...config files were updated in order to allow password authentication.

I am assuming and really hoping that some cwp_update script made these setting changes..?..

I am reluctant to add the root authorized_keys file back until I know what is going on ?

The original root authorized_keys files for many servers was provided by the server service, now broken.

Pllease help me better understand what might have happened.

Thanks for any info, still reviewing posts for relevant info

8

MySQL / Re: New Development Alma 9 server not able to cleanly upgrade maria database 11.6

« on: June 18, 2026, 03:31:45 AM »

Informational:

The offender here was the package perl-DBD-MySQL

Command:
dnf remove perl-DBD-MySQL

Was followed by:

dnf install  perl-DBD-MySQL

And voila dnf updates and upgrades are now without errors for version 11.8 I hope.

Cpanel-50477 is the case for reference.

Go figure,

Now how to get php-fpm working with the selector

9

MySQL / New Development Alma 9 server not able to cleanly upgrade maria database 11.6

« on: June 17, 2026, 05:31:03 PM »

After new Alma 9 install attempted to upgrade maria to 11.8,

Have gone through the documentation and iterations attempting to cleanly clear this issue.

By placing this line in the /etc/dnf/dnf.conf file I was able to update all the other cwp packages:
exclude=mysql* perl-DBD-MySQL*

Obviously at some point I want to update cleanly (including mysql stuff)

The error:

-----------------------------------------------------
[root@zelinux26 my.cnf.d]# dnf update -y

Error:
 Problem: cannot install both MariaDB-common-11.8.6-1.el9.x86_64 from mariadb and MariaDB-common-11.8.8-1.el9.x86_64 from @System
  - cannot install the best update candidate for package mysql-common-8.0.46-1.el9_8.x86_64
  - cannot install the best update candidate for package MariaDB-common-11.8.8-1.el9.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
------------------------------------------------------

The cwp7pro display instance is operating fine showing version 15.2

What can I do to resolve this dnf update issue..?..

Any help appreciated.