Show Posts

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.


Messages - braynex

Pages: [1]
1
Mod_Security / Re: mod_security with Comodo WAF locks out everbody
« on: January 16, 2024, 07:33:43 PM »
... Temporary solution is to disable mod_security on the account/domain in question.

No, I just switched to OSWAP rules until fix that. No need to disable mod_security.

Disabled Comodo rule with ID 218500 until fix. OWASP causes other incompatibilities so this way we can continue to use Comodo and no need to disable mod_security.

Added..

SecRuleRemoveById 218500

..to /usr/local/apache/modsecurity-cwaf/custom_user.conf

I am having the same issue as everyone after an update on WooCommere.  This fix my issue =)

2

I sent an error message before, but it hasn't been fixed yet. I've had to manually configure it before. The error I describe here:
https://forum.centos-webpanel.com/index.php?topic=9263.0

Up to today I update to add a new client I discovered a new bug. It is after saving it creates a strange string behind the drive parameters.

Code: [Select]
policy goi_2GB

        group caodat {

        cpu {
            cpu.cfs_quota_us = 500000;
            cpu.cfs_period_us = 100000;
          }

        memory {
             memory.limit_in_bytes = 2G;
             memory.memsw.limit_in_bytes = 2G;
        }

        blkio {
             blkio.throttle.read_bps_device = "8:336Jun53Sep151Jun215Nov151Sep234Jul151Jun151Jul151Jun792Nov4096Nov165Dec 20000000";
             blkio.throttle.write_bps_device = "8:336Jun53Sep151Jun215Nov151Sep234Jul151Jun151Jul151Jun792Nov4096Nov165Dec 20000000";
         }

    }

If I delete the parameters behind. Then everything is working fine.

Code: [Select]
policy goi_2GB

        group caodat {

        cpu {
            cpu.cfs_quota_us = 500000;
            cpu.cfs_period_us = 100000;
          }

        memory {
             memory.limit_in_bytes = 2G;
             memory.memsw.limit_in_bytes = 2G;
        }

        blkio {
             blkio.throttle.read_bps_device = "8:32 20000000";
             blkio.throttle.write_bps_device = "8:32 20000000";
         }

    }

Hopefully development will fix this.

I am having this same issue.  For some reason, whenever I add or change a user's cgroup policy template, it added that extra string (month/day) in the user's cgroup configuration.  It can be manually clean up but it will be a burden when new users signup, we need to edit the user's cgroup configuration manually.

3
Installation / Re: Latest CWP7 Missing tabs
« on: April 27, 2021, 12:42:58 PM »
Hi,

Is there any reason why I don't have "Apache Settings" and Letsencrypt Manager? on the left menu?  Are they deprecated? or do i need to turn something on?

Reason is i'm following this tutorial: https://www.youtube.com/watch?v=Au0aE5ZqqvU

WebServer Settings replaced the Apache Settings
AutoSSL (under WebServer Settings > SSL Certificates) replaced the Let's Encrypt Manager


Quote
which helps me setup the hostname and letsencrypt.

To change the hostname, go to Server Settings > Change Hostname

For the SSL/TLS, go to WebServer Settings > SSL Certificates > AutoSSL.  Make sure you already added the domain and pointed the nameservers to your CWP server before proceeding.

4
Installation / Re: RHEL 8 derivative support
« on: April 26, 2021, 03:42:34 PM »
Greetings,

I was wondering if CWP had been tested on any RHEL 8 derivatives like Oracle or AlmaLinux?

I did manage to install CWP on AlmaLinux (dedicated server) last Friday (23 April 2021) but went back to Centos 7 due to the missing varnish repos.  The varnish installer cannot proceed with a prompt that AlmaLinux is not supported (by packagecloud.io).

I did successfully installed Varnish by adding the repo on CWP > Server Settings > Yum Manager, but CWP still cannot see Varnish.

I did not bother troubleshooting further and rolled back to Centos 7.  Maybe someone here managed to fix the issue.

Or if you don't need varnish then AlmaLinux is ok.

5
Installation / Cgroup and Package Resource Limits
« on: April 26, 2021, 03:33:19 PM »
Dear All,

I need some help regarding the CWP's Cgroup and Package Limit Settings.  Please excuse me if this inquiry seems to look noobs :p

In cPanel shared hosting they have the following resource limits:

- Disk Space Quota
- Bandwidth Quota
- CPU
- Entry Processes
- Physical Memory Usage
- IOPS
- I/O Usage
- Number of Processes


CWP have the following resource limits:

Via Package
- Disk Space Quota
- Bandwidth Quota
- NPROC
- Apache NPROC
- Nofile/Open Files

Via Cgroups
- CPU
- Memory
- Disk I/O


So based on the definition of each item, I matched the cPanel items to the CWP items as follows:
      
---- cPanel -------- CWP ----
Disk Space Quota=Disk Space Quota
Bandwidth Quota=Bandwidth Quota
CPU=CPU
Entry Processes=Apache NPROC
Physical Memory Usage=Memory
IOPS=?
I/O Usage=Disk I/O
Number of Processes=NPROC
?=Nofile/Openfiles

Referring to the table above, the counterpart/equivalent for both IOPS and Nofile/Open Files are missing.

Need your help in identifying those two, thank you. 


Kind regards

Pages: [1]