Messages

1

Mod_Security / Re: mod_security with Comodo WAF locks out everbody

« on: January 16, 2024, 06:53:30 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

2

Mod_Security / Re: mod_security with Comodo WAF locks out everbody

« on: January 16, 2024, 06:28:59 PM »

"If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off."

That did not seem to help, still getting 403 Forbidden error.

3

Mod_Security / Re: mod_security with Comodo WAF locks out everbody

« on: January 16, 2024, 05:34:40 PM »

I can confirm this, wooCommerce version 8.5.1 conflicts with the latest Comodo WAF rules. As soon as wooCommerce gets updated to this version, site dies. Temporary solution is to disable mod_security on the account/domain in question.

4

PHP Selector / PHP-FPM template for user/domain

« on: October 30, 2022, 01:32:20 PM »

I have created a modified PHP-FPM template. How can I assign it to a specific user/domain?

In Webservers Main Conf I can select it for all users but that is not what I want. As a workaround I have edited the user configuration file directly (such as /opt/alt/php-fpm80/usr/etc/php-fpm.d/users/xxxxx.conf) but it gets overwritten if something is changed on the Webservers Main Conf page.

5

Updates / [SOLVED] Re: Unable to update packages

« on: February 12, 2022, 09:17:53 PM »

Well, epel-release-8-14.el8 release fixed it. Problem solved.

6

DNS / Strange DNS Zone Template applied

« on: February 12, 2022, 09:24:45 AM »

I have created a custom zone template in /usr/local/cwpsrv/htdocs/resources/conf/dns/bind/zones/custom.tpl and activated it as the default template for new accounts. It works fine. However, if I go to DNS Functions -> List DNS Zones and select "Reload Zone" on a domain, CWP creates a new zonefile that is not based on the default.tpl or my custom.tpl. It lacks most of the A records, the SPF record is missing etc. I don't know what it is and how to edit that template?

7

Updates / Re: Unable to update packages

« on: February 12, 2022, 07:45:14 AM »

Thank you for your reply. Tried that with similar result:

Code: [Select]

Error:
 Problem: problem with installed package epel-next-release-8-13.el8.noarch
  - package epel-next-release-8-13.el8.noarch requires epel-release = 8-13.el8, but none of the providers can be installed
  - package epel-next-release-8-11.el8.noarch requires epel-release = 8-11.el8, but none of the providers can be installed
  - cannot install both epel-release-8-14.el8.noarch and epel-release-8-13.el8.noarch
  - cannot install both epel-release-8-14.el8.noarch and epel-release-8-11.el8.noarch
  - conflicting requests
(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)


8

Updates / Unable to update packages

« on: February 11, 2022, 06:13:50 PM »

Packages update fails on Centos Stream 8 because of this:

Error:
 Problem: cannot install both epel-release-8-14.el8.noarch and epel-release-8-13.el8.noarch
  - package epel-next-release-8-14.el8.noarch requires epel-release = 8-14.el8, but none of the providers can be installed
  - cannot install the best update candidate for package epel-release-8-13.el8.noarch
  - cannot install the best update candidate for package epel-next-release-8-13.el8.noarch

Any help?

9

Updates / Re: After update today, nginx/1.20.0 error

« on: December 29, 2021, 11:59:30 AM »

there is one more way to resolve it

Code: [Select]

rm -f /usr/local/cwp/users/suspended/*.bandwidth
/scripts/cwp_api webservers rebuild_all

That worked, thanks.

Is it possible to change the scheduled time for the auto update? Now it is done around 3am and I don't like to wake up in the middle of the night to fix possible errors caused by the update.

10

SSL / Re: Letencrypt Auto renew and dovecot problem

« on: June 06, 2021, 08:51:33 AM »

I'm also having this issue, but with the web server (Nginx&Apache profile). When a domain's Letsencrypt SSL gets renewed, browser keeps showing expired certificate. I have to manually reload or restart the webserver before the renewed cert starts working.