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.
1
Suggestions / Re: :):):) Comodo WAF rules update required :):):)
« on: Today at 03:17:58 AM »
I agree that it is dead. But the problem with Comodo being dead is that it forces most of us who use free rulesets to migrate to the only known free alternative, which is the OWASP rules.
And that certainly can't be done overnight.
And whoever wants to take on this challenge will have to do some digital juggling to get both rulesets working, putting OWASP in a log-only (no blocks) state while collecting logs and statistics to include its whitelists.
It's a medium-term problem, but it's a very serious problem, and must be worked since now.
And that certainly can't be done overnight.
And whoever wants to take on this challenge will have to do some digital juggling to get both rulesets working, putting OWASP in a log-only (no blocks) state while collecting logs and statistics to include its whitelists.
It's a medium-term problem, but it's a very serious problem, and must be worked since now.
2
Information / CentOS CWP vs cPanel comparison
« on: January 10, 2025, 02:00:11 AM »
"CentOS CWP is ranked #1, while cPanel is ranked #2. CentOS CWP holds a 19.2% mindshare in WHCP, compared to cPanel’s 18.9% mindshare."
Mindshare is this presence in the mind. It is occupying a prominent place in the consumer's mind. It is being remembered by him in some way.
I couldn't download the report, but the information is on that site.
https://www.peerspot.com/products/comparisons/centos-cwp_vs_cpanel
Mindshare is this presence in the mind. It is occupying a prominent place in the consumer's mind. It is being remembered by him in some way.
I couldn't download the report, but the information is on that site.
https://www.peerspot.com/products/comparisons/centos-cwp_vs_cpanel
3
CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache
« on: January 03, 2025, 02:16:42 AM »Here are all the screenshots
Apache is running but the connection refused
https://ibb.co/88ZhN3K
https://ibb.co/WpTc2KK
https://ibb.co/1LKGY00
My httpd.conf
https://codepen.io/sohailfarooq356/pen/raBYBwb
Are you using CWPPro..?!
Your domain is not resolving here, and is not registered: thcwebiner.com
As a consequence, your domain does not resolve here, nor panel.thcwebiner.com
Are using really ns1 and ns2.centos-webpanel.com as you nameservers?
Regards,
Netino
4
Information / Re: CWP Support Site Not Working
« on: December 17, 2024, 02:07:14 AM »
The main problem was PHP-FPM as down, so, fortunately, I could workaround by myself.
The problem was solved by cancel three licenses, and changing IPs between other servers.
But thanks for attention.
Regards,
Netino
The problem was solved by cancel three licenses, and changing IPs between other servers.
But thanks for attention.
Regards,
Netino
5
Information / Re: CWP Support Site Not Working
« on: December 10, 2024, 12:27:58 AM »
It's completely unbelievable.
This new link refers to support for panel issues.
The thing is that I'm having problems with the LICENSE to use the CWPPro panel, because my server was no longer indicating the CWPPro license, and I posted a ticket on November 26th, and I still haven't received a response.
In other words, I'm paying for the license, and I can't use it.
This is completely unprofessional.
There comes a time when this type of problem starts to get tiresome.
Regards,
Netino
This new link refers to support for panel issues.
The thing is that I'm having problems with the LICENSE to use the CWPPro panel, because my server was no longer indicating the CWPPro license, and I posted a ticket on November 26th, and I still haven't received a response.
In other words, I'm paying for the license, and I can't use it.
This is completely unprofessional.
There comes a time when this type of problem starts to get tiresome.
Regards,
Netino
6
DNS / Re: Help with rDNS
« on: October 13, 2024, 01:21:49 AM »
This is only possible to set in the authoritative server.
You have access to that?
In a VPS server, normally, this is just configured with you provider.
This is yor case?
Regards,
Netino
You have access to that?
In a VPS server, normally, this is just configured with you provider.
This is yor case?
Regards,
Netino
7
PHP / Re: PHP Switcher version in Almalinux 9
« on: June 08, 2024, 02:05:30 AM »
You have enabled selinux on your server in enforcing mode. The ideal operation for selinux is to enable it in permissive mode, and only after resolving the error messages, then enable it in enforcing mode. It is not possible to install any web server management software with selinux enabled by default in enforcing mode, before operating it. You would have to work so much to solve the problems that it wouldn't be worth it. The best you can do is disable selinux, or only enable it in permissive mode, while you watch potential error messages.
Regards,
Netino
Regards,
Netino
8
PHP / Re: PHP-FPM PHP 8.2 & 8.3 failing to update - CWPpro version: 0.9.8.1178
« on: May 22, 2024, 10:51:00 PM »(...)
But for you, as you will use the CWP web environment, the more easy is to rename the file to /usr/bin/g++.old, and create a new script enabling that environment:
========================================================================
# mv /usr/bin/g++ /usr/bin/g++.old
# echo "scl enable devtoolset-7 'bash'" > /usr/bin/g++
# chmod 755 /usr/bin/g++
========================================================================
(...)
Sorry, this step is incomplete.
The correct, after install the environment, is:
========================================================================
# mv /usr/bin/g++ /usr/bin/g++.old
# echo "scl enable devtoolset-7 'bash'" > /usr/bin/g++
# echo "/opt/rh/devtoolset-7/root/usr/bin/g++" >> /usr/bin/g++
# chmod 755 /usr/bin/g++
========================================================================
We are simply using the newly installed 'g++'.
So, I just forget to invoke it.
9
PHP / Re: PHP-FPM PHP 8.2 & 8.3 failing to update - CWPpro version: 0.9.8.1178
« on: May 21, 2024, 11:33:49 PM »The default installation of PHP-8.2.19 is failing at this point:
"configure: error: *** A compiler with support for C++17 language features is required"
Install the CentOS SCL repository, this is an environment enabled to run the g++ compiler, with C++17 support:
===========================================
yum installcentos-release-scl -y
===========================================
Yes, you are correct, sorry for the typo.
The correct repository installation is:
===========================================
yum install centos-release-scl -y
===========================================
You must to enable as default that environment.
===========================================
scl enable devtoolset-7 'bash'
===========================================
If did'n worked to you, is because that environment was not enabled by the script.
This can be made by several forms.
For the CWP team, is just to put that line right before the the php-fpm82 script installation invokation, in the php build script.
But for you, as you will use the CWP web environment, the more easy is to rename the file to /usr/bin/g++.old, and create a new script enabling that environment:
========================================================================
# mv /usr/bin/g++ /usr/bin/g++.old
# echo "scl enable devtoolset-7 'bash'" > /usr/bin/g++
# chmod 755 /usr/bin/g++
========================================================================
Only now, then, can you try compiling via CWP web environment.
Now, CWP will use it to build environment, when asked the g++ the environment will be enabled.
After you compile it with success, you need to return to the normal configuration:
========================================================================
# mv /usr/bin/g++ /usr/bin/g++.new
# mv /usr/bin/g++.old /usr/bin/g++
========================================================================
10
PHP / Re: PHP-FPM PHP 8.2 & 8.3 failing to update - CWPpro version: 0.9.8.1178
« on: May 20, 2024, 10:21:09 PM »
The default installation of PHP-8.2.19 is failing at this point:
"configure: error: *** A compiler with support for C++17 language features is required"
Install the CentOS SCL repository, this is an environment enabled to run the g++ compiler, with C++17 support:
===========================================
yum installcentos-release-scl -y
===========================================
Install C++ support for GCC version 7:
===========================================
yum install devtoolset-7-gcc-c++ --enablerepo='centos-sclo-rh' -y
===========================================
Just one line in the compiler script solves this problem, changing the environment to this compiler before building PHP version 8.2.19:
===========================================
scl enable devtoolset-7 'bash'
===========================================
After the above command, you can check the g++ version like this:
===========================================
g++ -v
===========================================
...resulting in this:
===========================================
(...)
gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC)
===========================================
(Source: <https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/7/html/user_guide/chap-gcc>)
The script must be run with this environment enabled.
Problem solved.
Regards,
Netino
"configure: error: *** A compiler with support for C++17 language features is required"
Install the CentOS SCL repository, this is an environment enabled to run the g++ compiler, with C++17 support:
===========================================
yum installcentos-release-scl -y
===========================================
Install C++ support for GCC version 7:
===========================================
yum install devtoolset-7-gcc-c++ --enablerepo='centos-sclo-rh' -y
===========================================
Just one line in the compiler script solves this problem, changing the environment to this compiler before building PHP version 8.2.19:
===========================================
scl enable devtoolset-7 'bash'
===========================================
After the above command, you can check the g++ version like this:
===========================================
g++ -v
===========================================
...resulting in this:
===========================================
(...)
gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC)
===========================================
(Source: <https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/7/html/user_guide/chap-gcc>)
The script must be run with this environment enabled.
Problem solved.
Regards,
Netino
11
SSL / Re: New SSL cert broke my server
« on: May 10, 2024, 11:30:26 PM »
Seems your files /etc/pki/tls/certs/hostname.bundle and /etc/pki/tls/private/hostname.key was generated at different moments.
The best an easier step to you, is save your server certificate.
Just save the hostname of your server again, and CWP will generate your server certificate again.
Regards,
Netino
The best an easier step to you, is save your server certificate.
Just save the hostname of your server again, and CWP will generate your server certificate again.
Regards,
Netino
12
Information / Re: Roundcube big security issue.
« on: April 26, 2024, 06:32:48 PM »
Yes, ModSecurity.
I have Como rules installed with ModSecurity, and it is blocking these access.
Regards,
Netino
I have Como rules installed with ModSecurity, and it is blocking these access.
Regards,
Netino
13
Information / Re: Has anyone already migrate to Almalinux8 in a CentoOS7 OpenVZ container?
« on: April 26, 2024, 05:43:32 PM »
I find seems is nearly impossible, quoted from:
https://github.com/plesk/centos2alma/issues/87
https://github.com/plesk/centos2alma/issues/87
Quote
Unfortunately, the news is not optimistic. We have investigated and it appears that there is no way to use Elevate (or any other Leapp-based tool) to convert the OS inside a container. This conclusion is based on two facts:
1. The Leapp upgrade process is based on the Interim System, which upgrades certain packages. It can be described as a temporary OS that replaces CentOS 7 packages with AlmaLinux 8 packages. Leapp does not modify packages inside CentOS 7 itself but rather performs preparations and reboots into an initrd OS that performs the actual transformation.
2. When we describe containers broadly, we can consider them as a form of isolation within your kernel. So it has no own bootloader, kernel or something where you could start temporary OS.
Therefore, there is no way to start the initrd inside a container. This is why the Leapp framework and as a result our current centos2alma tool cannot be used to convert the OS inside any container (e.g., Docker, Virtuozzo, etc).
Regarding vzupgrade, if I understand correctly, it is a tool to upgrade the bare-metal server that hosts virtual machines and containers. We have attempted to use it to convert a Virtuozzo container on our side without success. Additionally, there is the vzdeploy tool that can be used to convert CentOS 7 into VZLinux 7 inside a container. However, it simply reinstalls packages from the VZLinux repository within the container. As far as I can see, it cannot convert your CentOS 7 into VZLinux 8, for example. Therefore, it does not appear to be a solution to your problem.
We are also exploring other options for container owners:
1. As far as I know, Virtuozzo allows you to convert a container into a virtual machine. And a Virtuozzo virtual machine can be converted using any leapp based instrument (including centos2alma), so this seems to be the simplest way to resolve the issue.
2. You could use the Plesk migrator tool to migrate your Plesk from the CentOS 7 container to an AlmaLinux 8 container. Obviously you have to have this AlmaLinux 8 container somewhere.
3. Try converting your container with vzdeploy into VZLinux 7 and inquire with the Virtuozzo developers if there is any way to convert VZLinux 7 to VZLinux 8 inside a container.
I hope this information will be helpful in addressing your situation. Additionally, we will reach out to the Virtuozzo developers to inquire about their perspective on the problem.
14
Information / Has anyone already migrate to Almalinux8 in a CentoOS7 OpenVZ container?
« on: April 26, 2024, 05:07:34 PM »
Has anyone already migrate to Almalinux8 in a CentOS7 OpenVZ container?
I already know is needed to upgrade to Centos8, before to install AlmaLinux8, with the migration tool:
https://wiki.almalinux.org/documentation/migration-guide.html#how-to-migrate
But there are a indication this can be made the upgrade to AlmaLinux in a container, like this post:
https://bugs.almalinux.org/view.php?id=140
But I haven't tried it myself yet.
Has anyone tried this, and did it work?
Regards,
Netino
I already know is needed to upgrade to Centos8, before to install AlmaLinux8, with the migration tool:
https://wiki.almalinux.org/documentation/migration-guide.html#how-to-migrate
But there are a indication this can be made the upgrade to AlmaLinux in a container, like this post:
https://bugs.almalinux.org/view.php?id=140
But I haven't tried it myself yet.
Has anyone tried this, and did it work?
Regards,
Netino
15
CentOS 8 Problems / Re: reboot problem
« on: January 25, 2024, 10:07:54 PM »
The 'shutdown' command is just a symlink to systemctl.
If the system does not answer 'shotdown' command, may be needed to try directly the systemctl command:
If the command does not work, you must need to investigate the logs, with the command:
If you don't undestand the logs, post the related lines here.
Regards,
Netino
If the system does not answer 'shotdown' command, may be needed to try directly the systemctl command:
Code: [Select]
systemctl rebootIf the command does not work, you must need to investigate the logs, with the command:
Code: [Select]
journalctl -xeIf you don't undestand the logs, post the related lines here.
Regards,
Netino
