This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
526
CentOS-WebPanel Bugs / Re: Latest CWP Almalinux 9 sept2024 fresh instal = amavis timeout + mariadb Vmem exc
« on: February 04, 2025, 11:10:31 PM »There are certain installation steps that are needed for CWP on AL9.Code: [Select]dnf install spamassassin amavis
Otherwise you'll be chasing your tail.
To fix OpenDKIM on CWP & AL9 see:
https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/dkim-not-working-on-almalinux-9-with-cwp/
Hi,
Please provide a brief explanation for the photo:
https://prnt.sc/CdMFp9O-XWn9
BR
Venty
I guess that didn't translate out of English well.
I means you will be going in circles trying to figure out why that 2 programs don't work.
I'm still confused why you want to remove some of the main programs, as if you have them disabled they won't be running.
Also why your ALmaLinux hasn't updated to 9.5, the screenshot you did still shows 9.4.
And yes, AntiSpam/AntiVirus will show an error messgae, you asked how to disable & remove it from your server.
In your /etc/csf/csf.pignore, you can dd the below:
exe:/usr/libexec/postfix/pickup
exe:/usr/libexec/postfix/qmgr
exe:/usr/libexec/postfix/tlsmgr
exe:/usr/sbin/pdns_server
exe:/usr/sbin/httpd
exe:/usr/bin/bash
exe:/usr/libexec/dovecot/stats
exe:/usr/sbin/nrpe
exe:/usr/bin/redis-server
exe:/usr/bin/freshclam
exe:/usr/local/bin/php-cgi /home/davidrk5/public_html/index.php
exe:/usr/local/bin/php-cgi /home/davidrk5/public_html/ssmw/wp-cron.php
exe:/usr/local/bin/php
exe:/usr/lib/systemd/systemd
exe:/usr/libexec/platform-python3.6
exe:/usr/sbin/mariadbd
exe:/usr/lib/systemd/systemd-resolved
exe:/usr/sbin/rngd
exe:/usr/bin/dbus-broker
exe:/usr/bin/dbus-broker-launch
exe:/usr/sbin/rpcbind
exe:/usr/bin/rpcbind
527
Information / Re: database special characters password
« on: February 04, 2025, 01:34:45 PM »Also, postfix and/or dovecot don't appreciate a password that ends in a period -- it is seen as a terminator signal.
Terminator and period in the same sentence...

I'll be back...
ATH0
528
Problems on other RedHat linux servers / Re: How to permanently disable ClamAV?
« on: February 03, 2025, 05:43:17 PM »529
How to / Re: Anyone have a How TO Guide for setting up & using Cloudflare with CWP?
« on: February 03, 2025, 03:28:15 AM »
Mail servers you can't use Proxy on.
So on your MX record, it would be like
domain.com 10 MX mail.domain.com
mail A 123.123.123.123
Then you can activate proxy on the main domain.com
So on your MX record, it would be like
domain.com 10 MX mail.domain.com
mail A 123.123.123.123
Then you can activate proxy on the main domain.com
530
E-Mail / Re: Process email queue individualy
« on: February 02, 2025, 01:25:15 AM »
You can requeue or delete them individually, or process all / delete all.
Are you trying to check emails before they are going out?
Are you trying to check emails before they are going out?
531
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: February 02, 2025, 12:51:55 AM »
And it works for both CWPfree and CWPpro.
532
Problems on other RedHat linux servers / Re: How to permanently disable ClamAV?
« on: February 02, 2025, 12:50:53 AM »
If the service is not installed, it won't show on the dashboard.
You can try to uninstall it using
Is there some reason you don't want an AV on your server?
You can try to uninstall it using
Code: [Select]
dnf remove clamav* clamdIs there some reason you don't want an AV on your server?
533
Information / Re: database special characters password
« on: February 02, 2025, 12:48:40 AM »
It seems in general, CWP doesn't like special characters.
534
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: February 01, 2025, 08:55:10 AM »
Morning Y'all.
Have 2 new KB Articles on how to update ModSecurity for Apache in CWP under AL8 & AL9 and use the latest OWASP CRS ruleset:
https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/update-modsecurity-running-cwp-and-apache-on-almalinux-8-9/
https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/update-to-owasp-crs-ruleset-running-cwp-and-apache-on-almalinux-8-9/
Any feedback, let me know.
Have 2 new KB Articles on how to update ModSecurity for Apache in CWP under AL8 & AL9 and use the latest OWASP CRS ruleset:
https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/update-modsecurity-running-cwp-and-apache-on-almalinux-8-9/
https://kb.starburstservices.com/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/update-to-owasp-crs-ruleset-running-cwp-and-apache-on-almalinux-8-9/
Any feedback, let me know.
535
Installation / Re: AL 9 server not upgrading to CWP Pro
« on: January 30, 2025, 04:47:59 PM »This is my IP
192.119.111.125
I've run all sort of commands, nothing happens!
I added your IP (192.119.111.125) to our partner account (temporarily).
Run
Code: [Select]
/scripts/update_cwpYou should have CWPpro now.
536
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: January 30, 2025, 04:43:33 PM »
Well looks like I got OWASP ruleset 4.11.0 working OK with ModSecurity on AL9.
Which is good, considering I activated it on a live production server, after I noticed I wasn't logged into my test box on my desk.
I'll be posting a KB article later today.
But yea, when they split the company both halves started offering their own paid 'ruleset'.
The 'new' endpoint doesn't see CWP, only cPanel, DA, and Plesk and installs as a standalone, which doesn't play well with CWP.
Which is good, considering I activated it on a live production server, after I noticed I wasn't logged into my test box on my desk.

I'll be posting a KB article later today.
But yea, when they split the company both halves started offering their own paid 'ruleset'.
The 'new' endpoint doesn't see CWP, only cPanel, DA, and Plesk and installs as a standalone, which doesn't play well with CWP.
537
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: January 28, 2025, 11:36:03 PM »
We use Apache, and not Nginx.
There is more script support for Apache, and the performance benefit of Nginx is negatable.
OWASP old & Comodo both work fine, which is the odd thing.
If Xcitium did kill the free Comodo ruleset, that only leave OWASP of being free for users to choose.
There is more script support for Apache, and the performance benefit of Nginx is negatable.
OWASP old & Comodo both work fine, which is the odd thing.
If Xcitium did kill the free Comodo ruleset, that only leave OWASP of being free for users to choose.
539
Installation / Re: ...server under AL9?
« on: January 28, 2025, 01:57:01 AM »
I've posted the basic setup steps here in the forums a couple times.
Here it is again, or you also have options of people that can get the basic installed for you.
You can't have any services installed before installing CWP.
So if Apache is working 'out of the box', you are installing AlmaLinux 9.4 LAMP.
That won't work.
Reimage with the bare AlmaLinux 9.5
Setup your networking, hostname, timzone.
Then:
Reboot
Configure & Start CSF
UPDATE DEPENDENCIES
To updated MariaDB follow:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/
The one string to re-install MariaDB has been updated, or you'll get an error.
Run this instead:
There are other steps, but everyone customizes their servers differently.
Here it is again, or you also have options of people that can get the basic installed for you.
You can't have any services installed before installing CWP.
So if Apache is working 'out of the box', you are installing AlmaLinux 9.4 LAMP.
That won't work.
Reimage with the bare AlmaLinux 9.5
Setup your networking, hostname, timzone.
Then:
Code: [Select]
dnf install dnf-plugins-coreCode: [Select]
dnf install elrepo-release epel-release -yCode: [Select]
dnf config-manager --set-enabled crbCode: [Select]
dnf --refresh updateCode: [Select]
dnf install nano wget ipset ebtables iptables ipset-service uuid uuid-devel libuuid-devel m4 pcre pcre-devel zlib-devel perl-DBD-MySQL perl-IPC-Cmd perl-Pod-Html perl-Sys-Hostname perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch perl-GDGraph libtool s-nail htop sysstat python3-perf ImageMagick ImageMagick-devel nmap make quota cockpit* -yCode: [Select]
dnf --refresh updateCode: [Select]
dnf install clamav* clamdCode: [Select]
dnf clean allCode: [Select]
cd /usr/local/srcCode: [Select]
wget http://centos-webpanel.com/cwp-el9-latestCode: [Select]
sh cwp-el9-latestCode: [Select]
dnf install spamassassin amavisReboot
Configure & Start CSF
UPDATE DEPENDENCIES
Code: [Select]
dnf install php-cli libsodium libsodium-devel php-sodium php-pecl-zip php-pecl-mailparse php-mbstring php-pear php-devel php-pecl-imagickCode: [Select]
pecl channel-update pecl.php.netTo updated MariaDB follow:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/
The one string to re-install MariaDB has been updated, or you'll get an error.
Run this instead:
Code: [Select]
dnf install MariaDB-server MariaDB-client net-snmp perl-DBD-MySQL --allowerasingThere are other steps, but everyone customizes their servers differently.
540
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: January 28, 2025, 01:39:23 AM »
The defaults are:
I followed the OWASP docs, and changed MODSEC_LOG to MODSEC_LOG = "/usr/local/apache/logs/modsec_audit.log"
When that failed, I added it to the next empty custom entry CUSTOM3_LOG, still no joy.
I've put another paid ticket in to CWP.
They argued the last ticket that didn't solve the problem was closed as being 'resolved'
What's weird is that the OWASP old ruleset works OK, but if you select OWASP latest it breaks everything.
You still see it stop attacks if your view the ModSecurity log.
Just added "/usr/local/cwpsrv/logs/*_log" to CUSTOM3_LOG, which was empty.
Will see if that works.
Also have a virtual meeting with Xcitium (company who bought Comodo) next week, to find out what there plans are for the future of that ruleset.
Because of right now it's dead.
Hopefully this will get resolved.
I'm not sure about anyone else, but this simple thing has turned into a large cluster.
Quote
HTACCESS_LOG = "/usr/local/apache/logs/error_log"
MODSEC_LOG = "/usr/local/apache/logs/error_log"
SSHD_LOG = "/var/log/secure"
SU_LOG = "/var/log/secure"
SUDO_LOG = "/var/log/secure"
FTPD_LOG = "/var/log/messages"
SMTPAUTH_LOG = "/var/log/maillog"
POP3D_LOG = "/var/log/dovecot-info.log"
IMAPD_LOG = "/var/log/dovecot-info.log"
IPTABLES_LOG = "/var/log/messages"
SUHOSIN_LOG = "/var/log/messages"
BIND_LOG = "/var/log/messages"
SYSLOG_LOG = "/var/log/messages"
WEBMIN_LOG = "/var/log/secure"
CWP_LOG = "/var/log/cwp_client_login.log"
CUSTOM1_LOG = "/var/log/cwp_client_login.log"
CUSTOM2_LOG = "/usr/local/apache/domlogs/*.log"
I followed the OWASP docs, and changed MODSEC_LOG to MODSEC_LOG = "/usr/local/apache/logs/modsec_audit.log"
When that failed, I added it to the next empty custom entry CUSTOM3_LOG, still no joy.
I've put another paid ticket in to CWP.
They argued the last ticket that didn't solve the problem was closed as being 'resolved'
What's weird is that the OWASP old ruleset works OK, but if you select OWASP latest it breaks everything.
You still see it stop attacks if your view the ModSecurity log.
Just added "/usr/local/cwpsrv/logs/*_log" to CUSTOM3_LOG, which was empty.
Will see if that works.
Also have a virtual meeting with Xcitium (company who bought Comodo) next week, to find out what there plans are for the future of that ruleset.
Because of right now it's dead.
Hopefully this will get resolved.
I'm not sure about anyone else, but this simple thing has turned into a large cluster.
