Messages

1

PHP Selector / Re: cant install any php version

« on: May 17, 2023, 11:43:47 AM »

would you like to share the tutorial? Thank You

2

CentOS-WebPanel Bugs / Re: [MAJOR BUG] Disc Quota Reported Wrong

« on: July 09, 2022, 11:55:01 PM »

temporary solution i did:
backup : web file + database (don't use backup feature in root, but manual backup)
remove the hosting package
recreate hosting package
restore website data
done

3

CentOS-WebPanel Bugs / Re: the indicator in the disk usage menu is full, even though it's not

« on: July 09, 2022, 11:41:03 PM »

on the ticket only replies this is a bug 

temporary solution:
backup : web file + database (don't use backup feature in root, but manual backup)
remove the hosting package
recreate hosting package
restore website data

4

CentOS-WebPanel Bugs / htop vs cwp pro performance which one is correct?

« on: June 18, 2022, 09:10:10 AM »

regards,
in cwp pro performance shows red (high load). but on htop (ssh) it's normal, there's no overload

5

CentOS 7 Problems / Re: security center warning error !

« on: June 18, 2022, 02:37:03 AM »

yesterday, because there was no reply in the forum.
 finally got one time support. in one ticket will be fixed in the next version. so this is purely a bug?
but fortunately, it was handled by another support team, and it was finally solved.

and I don't know what the root of the problem is

**G Translate

6

Scripts / unsuspend account via terminal/command line?

« on: June 15, 2022, 08:02:48 AM »

how to unsuspend account via terminal/command line. because I can't enter the web panel/gui

7

CentOS 7 Problems / Re: security center warning error !

« on: May 27, 2022, 05:46:34 PM »

I tried to open the file /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php
but there was a warning:

<?php //0042b
// Copyright CentOS WebPanel, Decoding is FORBIDDEN
// All Rights Reserved. www.centos-webpanel.com
if(!extension_loaded('ionCube Loader')){$__oc=strtolower(substr(php_uname(),0,3$
?>

8

CentOS 7 Problems / security center warning error !

« on: May 25, 2022, 10:31:05 AM »

regards,
on the security center menu I found a warning:
Notice: Undefined variable: [obfuscated] in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php on line 0

Notice: Trying to get property 'clam_path' of non-object in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php on line 0

Warning: file_put_contents(/usr/local/cwp/.conf/clam/.clamusage.json): failed to open stream: No such file or directory in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php on line 0

Warning: First parameter must either be an object or the name of an existing class in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php on line 0

Warning: Creating default object from empty value in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/UserClamTrait.php on line 0

Notice: Undefined property: stdClass::$scan_history in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/ClamEngineTrait.php on line 0

Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/cwpsrv/htdocs/resources/admin/include/modules/security_center/helpers/traits/ClamEngineTrait.php on line 0

how to fix it?

Thank you

9

CentOS 7 Problems / Re: .htaccess: Option All not allowed here

« on: March 06, 2022, 04:12:39 AM »

these codes are created directly by the wordpress plugin "BPS pro".
thank you, now it has been solved, by removing the following code

Code: [Select]

#   BULLETPROOF PRO 16.3.1 SECURE .HTACCESS         

# PHP/PHP.INI HANDLER/CACHE CODE
# Use BPS Custom Code to add php/php.ini Handler and Cache htaccess code and to save it permanently.
# Most Hosts do not have/use/require php/php.ini Handler htaccess code

# TURN OFF YOUR SERVER SIGNATURE
# Suppresses the footer line server version number and ServerName of the serving virtual host
ServerSignature Off

# DO NOT SHOW DIRECTORY LISTING
# Disallow mod_autoindex from displaying a directory listing
# If a 500 Internal Server Error occurs when activating Root BulletProof Mode
# copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
# and paste it into BPS Custom Code and comment out Options -Indexes
# by adding a # sign in front of it.
# Example: #Options -Indexes
Options -Indexes

# DIRECTORY INDEX FORCE INDEX.PHP
# Use index.php as default directory index file. index.html will be ignored.
# If a 500 Internal Server Error occurs when activating Root BulletProof Mode
# copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
# and paste it into BPS Custom Code and comment out DirectoryIndex
# by adding a # sign in front of it.
# Example: #DirectoryIndex index.php index.html /index.php
DirectoryIndex index.php index.html /index.php

10

CentOS 7 Problems / Re: .htaccess: Option All not allowed here

« on: March 04, 2022, 04:56:56 PM »

replace
Options All -Indexes

with
Options -Indexes

hi @studio4host
I've tried this but still error. I have fixed Permissions , I have rebuilt the web server (web server domainconf menu) but there is still 500 Internal Server Error.
the error is the sub domain not the main domain
this is the content

Code: [Select]

#   BULLETPROOF PRO 16.3.1 SECURE .HTACCESS         

# PHP/PHP.INI HANDLER/CACHE CODE
# Use BPS Custom Code to add php/php.ini Handler and Cache htaccess code and to save it permanently.
# Most Hosts do not have/use/require php/php.ini Handler htaccess code

# TURN OFF YOUR SERVER SIGNATURE
# Suppresses the footer line server version number and ServerName of the serving virtual host
ServerSignature Off

# DO NOT SHOW DIRECTORY LISTING
# Disallow mod_autoindex from displaying a directory listing
# If a 500 Internal Server Error occurs when activating Root BulletProof Mode
# copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
# and paste it into BPS Custom Code and comment out Options -Indexes
# by adding a # sign in front of it.
# Example: #Options -Indexes
Options -Indexes

# DIRECTORY INDEX FORCE INDEX.PHP
# Use index.php as default directory index file. index.html will be ignored.
# If a 500 Internal Server Error occurs when activating Root BulletProof Mode
# copy the entire DO NOT SHOW DIRECTORY LISTING and DIRECTORY INDEX sections of code
# and paste it into BPS Custom Code and comment out DirectoryIndex
# by adding a # sign in front of it.
# Example: #DirectoryIndex index.php index.html /index.php
DirectoryIndex index.php index.html /index.php

# BRUTE FORCE LOGIN PAGE PROTECTION
# PLACEHOLDER ONLY
# Use BPS Custom Code to add Brute Force Login protection code and to save it permanently.
# See this link: https://forum.ait-pro.com/forums/topic/protect-login-page-from-brute-force-login-attacks/
# for more information.

# BPS PRO ERROR LOGGING AND TRACKING
# Use BPS Custom Code to modify/edit/change this code and to save it permanently.
# BPS Pro has premade 400 Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not Allowed and
# 410 Gone template logging files that are used to track and log 400, 403, 404, 405 and 410 errors
# that occur on your website. When a hacker attempts to hack your website the hackers IP address,
# Host name, Request Method, Referering link, the file name or requested resource, the user agent
# of the hacker and the query string used in the hack attempt are logged.
# All BPS Pro log files are htaccess protected so that only you can view them.
# The 400.php, 403.php, 404.php, 405.php and 410.php files are located in /wp-content/plugins/bulletproof-security/
# The 400, 403, 405 and 410 Error logging files are already set up and will automatically start logging errors
# after you install BPS Pro and have activated BulletProof Mode for your Root folder.
# If you would like to log 404 errors you will need to copy the logging code in the BPS Pro 404.php file
# to your Theme's 404.php template file. Simple instructions are included in the BPS Pro 404.php file.
# You can open the BPS Pro 404.php file using the WP Plugins Editor or by using the BPS Pro File Manager.
# NOTE: By default WordPress automatically looks in your Theme's folder for a 404.php Theme template file.

ErrorDocument 400 /wp-content/plugins/bulletproof-security/400.php
ErrorDocument 401 default
ErrorDocument 403 /wp-content/plugins/bulletproof-security/403.php
ErrorDocument 404 /404.php
ErrorDocument 405 /wp-content/plugins/bulletproof-security/405.php
ErrorDocument 410 /wp-content/plugins/bulletproof-security/410.php

# DENY ACCESS TO PROTECTED SERVER FILES AND FOLDERS
# Use BPS Custom Code to modify/edit/change this code and to save it permanently.
# Files and folders starting with a dot: .htaccess, .htpasswd, .errordocs, .logs
RedirectMatch 403 \.(htaccess|htpasswd|errordocs|logs)$

# WP-ADMIN/INCLUDES
# Use BPS Custom Code to remove this code permanently.
RewriteEngine On
RewriteBase /
RewriteRule ^wp-admin/includes/ - [F]
RewriteRule !^wp-includes/ - [S=3]
RewriteRule ^wp-includes/[^/]+\.php$ - [F]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F]
RewriteRule ^wp-includes/theme-compat/ - [F]

# WP REWRITE LOOP START
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]

# REQUEST METHODS FILTERED
# If you want to allow HEAD Requests use BPS Custom Code and copy
# this entire REQUEST METHODS FILTERED section of code to this BPS Custom Code
# text box: CUSTOM CODE REQUEST METHODS FILTERED.
# See the CUSTOM CODE REQUEST METHODS FILTERED help text for additional steps.
RewriteCond %{REQUEST_METHOD} ^(TRACE|DELETE|TRACK|DEBUG) [NC]
RewriteRule ^(.*)$ - [F]
RewriteCond %{REQUEST_METHOD} ^(HEAD) [NC]
RewriteRule ^(.*)$ /wp-content/plugins/bulletproof-security/405.php [L]

# PLUGINS/THEMES AND VARIOUS EXPLOIT FILTER SKIP RULES
# To add plugin/theme skip/bypass rules use BPS Custom Code.
# The [S] flag is used to skip following rules. Skip rule [S=12] will skip 12 following RewriteRules.
# The skip rules MUST be in descending consecutive number order: 12, 11, 10, 9...
# If you delete a skip rule, change the other skip rule numbers accordingly.
# Examples: If RewriteRule [S=5] is deleted than change [S=6] to

11

CentOS-WebPanel Bugs / Re: the indicator in the disk usage menu is full, even though it's not

« on: January 17, 2022, 04:50:10 PM »

thank you,
I have sent a ticket

12

CentOS-WebPanel Bugs / Re: the indicator in the disk usage menu is full, even though it's not

« on: January 17, 2022, 04:39:00 PM »

The difference may be due to the space occupied by your emails, which are not inside the user's folder.

Thank You,
There are no emails in this account.

13

CentOS-WebPanel Bugs / the indicator in the disk usage menu is full, even though it's not

« on: January 17, 2022, 01:48:18 PM »

regards,
I found several customer accounts experiencing full quota notifications, but actually the files are still small. and unsynchronized reading of files in the Disk Usage menu

because the quota indicator is full, the website cannot upload files. even though there should still be a lot of disk quotas
**G translate

14

Addons / how to remove/hide Site.pro Website Builder menu

« on: May 31, 2021, 08:28:02 AM »

I want to delete the Site.pro Website Builder menu from cwp panel, how do I do it?

15

CentOS 7 Problems / ssh login problems

« on: February 12, 2021, 10:56:29 PM »

regards,
I'm using cwp pro7 and having ssh login problems.

To be able to log in using ssh, first I have to open the hosting panel (login cwp with root user, with a web browser). then can access or login ssh.

without login (cwp panel with root user, web browser) I can't access ssh. there is a time out comment. or even if I can log in it will take a very long process.

Is there a firewall setting error?

thank you