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.
Pages: [1]
1
Installation / CPU Usage Limited to 50% - CGroups Installed & Setup
« on: April 14, 2022, 05:01:28 AM »
Hi all,
When loading my site using Wordpress + WooCommerce, often I will see php-fpm using high resources - it'll often flog the CPU usage to 50%. Firstly, is this normal? I am using a caching plugin, which has helped now to reduce PHP load, though often I still see CPU usage stuck at 50% until the process is complete, sometimes taking up to 10-20 seconds before the processes finish.
For some reason, I can't seem to allow more CPU usage to help speed-up those processes. Is there a way I can allow my hosting account to use up to 80% CPU, rather than capping it at 50% CPU usage?
Since I'm the sole account under CWP, I can allocate more resources to the cPanel account.
Screenshot of CGroups: https://i.kutit.net/h/UPIBZF.png
The server is an 8 vCore server, so I presume by the CPU monitor capping out at 50%.
I have set the CPU percentage to 750% in CGroups for the account I want to allow 7+ cores, though the main CWPpro Performance monitor.
Am I setting something up incorrectly?
When loading my site using Wordpress + WooCommerce, often I will see php-fpm using high resources - it'll often flog the CPU usage to 50%. Firstly, is this normal? I am using a caching plugin, which has helped now to reduce PHP load, though often I still see CPU usage stuck at 50% until the process is complete, sometimes taking up to 10-20 seconds before the processes finish.
For some reason, I can't seem to allow more CPU usage to help speed-up those processes. Is there a way I can allow my hosting account to use up to 80% CPU, rather than capping it at 50% CPU usage?
Since I'm the sole account under CWP, I can allocate more resources to the cPanel account.
Screenshot of CGroups: https://i.kutit.net/h/UPIBZF.png
The server is an 8 vCore server, so I presume by the CPU monitor capping out at 50%.
I have set the CPU percentage to 750% in CGroups for the account I want to allow 7+ cores, though the main CWPpro Performance monitor.
Am I setting something up incorrectly?
2
Apache / Redirect Domain using CNAME outside of CWP Instance
« on: April 14, 2021, 11:50:09 AM »
Good afternoon all,
I currently have CWP setup with Apache.
I have tried tinkering with the conf.d files (Including the SSL config file), however, I have had no luck.
Essentially, I have a CWP User with domain example.com, with a website setup and working great, no issues.
I want to point another domain, let's say: website.com to example.com using CNAME.
The reason for this is that I have a URL shortening script which allows for custom domains to be linked to the script.
I have tried adjusting/editing the conf.d files for example.com to try and allow website.com (and other domains pointed to example.com). When I point website.com to example.com using CNAME and load website.com in a browser, it shows the "HTTP Test Page" from CWP, and it does NOT show the content on example.com.
I have tried tinkering around, including copying the conf.d configuration as suggested by the developer of the script, however, I feel there is a misconfiguration somewhere with CWP and/or Apache, since it is wanting to handle the domain, website.com, as if it were a new domain pending to be linked to a CWP user account.
The virtual host recommended by the script developer is as it comes below - FYI, I have attempted to configure both conf.d files, including the SSL conf file, to no avail. Not sure where I'm going wrong in this particular instance, or if there are additional files I need to edit in order to allow website.com to CNAME example.com...
(IP Changed for privacy)
I also did the same for the SSL Config file, adding the required SSL certificates.
Unfortunately, as mentioned, when I visit website.com, it takes me to the HTTP Test Page instead of the content hosted on example.com. I DO NOT want to have to add website.com to the CWP user panel, and I don't want to have to manually add the domain into any config files if I don't have to, as I have clients who I want to be able to point their domains to example.com and allow the script to accept/reject traffic according to how their account is setup on the PHP script hosted on example.com.
To clarify, everything works great when visiting example.com. Somewhere within CWP is preventing website.com from using example.com as a CNAME, and it CWP wants to handle it as if it were an add-on domain.
I currently have CWP setup with Apache.
I have tried tinkering with the conf.d files (Including the SSL config file), however, I have had no luck.
Essentially, I have a CWP User with domain example.com, with a website setup and working great, no issues.
I want to point another domain, let's say: website.com to example.com using CNAME.
The reason for this is that I have a URL shortening script which allows for custom domains to be linked to the script.
I have tried adjusting/editing the conf.d files for example.com to try and allow website.com (and other domains pointed to example.com). When I point website.com to example.com using CNAME and load website.com in a browser, it shows the "HTTP Test Page" from CWP, and it does NOT show the content on example.com.
I have tried tinkering around, including copying the conf.d configuration as suggested by the developer of the script, however, I feel there is a misconfiguration somewhere with CWP and/or Apache, since it is wanting to handle the domain, website.com, as if it were a new domain pending to be linked to a CWP user account.
The virtual host recommended by the script developer is as it comes below - FYI, I have attempted to configure both conf.d files, including the SSL conf file, to no avail. Not sure where I'm going wrong in this particular instance, or if there are additional files I need to edit in order to allow website.com to CNAME example.com...
(IP Changed for privacy)
Code: [Select]
<VirtualHost 123.123.123.123:80>
ServerAdmin webmaster@localhost
DocumentRoot /home/kutitnet/public_html
<Directory "/home/examplecom/public_html">
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
CustomLog /usr/local/apache/domlogs/kutit.net.bytes bytes
CustomLog /usr/local/apache/domlogs/kutit.net.log combined
ErrorLog /usr/local/apache/domlogs/kutit.net.error.log
<IfModule mod_dir.c>
DirectoryIndex index.php index.pl index.cgi index.html index.xhtml index.htm
</IfModule>
</VirtualHost>I also did the same for the SSL Config file, adding the required SSL certificates.
Unfortunately, as mentioned, when I visit website.com, it takes me to the HTTP Test Page instead of the content hosted on example.com. I DO NOT want to have to add website.com to the CWP user panel, and I don't want to have to manually add the domain into any config files if I don't have to, as I have clients who I want to be able to point their domains to example.com and allow the script to accept/reject traffic according to how their account is setup on the PHP script hosted on example.com.
To clarify, everything works great when visiting example.com. Somewhere within CWP is preventing website.com from using example.com as a CNAME, and it CWP wants to handle it as if it were an add-on domain.
3
CentOS-WebPanel Bugs / Logging into CWP User Error
« on: May 15, 2020, 11:57:13 AM »
When attempting to login to CWP User cPanel, an error is thrown: "uerror"
I noticed that this has only happened since updating CWP to the latest update that was released today.
(Scroll the image to the right to see the error)
* PS: This is happening both when accessing via "cpanel.domain.tld" as well as the hostname "srv1.domain.tld:2083" - logging into CWP Admin panel works fine. All accounts will not login via CWP user and they're all showing this "uerror". Creating new CWP User accounts also show the same login error, so it's effecting the entire CWP User panel. I had an old tab opened which was logged into CWP User and that's working fine to navigate the account, but as soon as I logged out and tried to log back in, the "uerror" occurs. Have tried on alternative browsers/IP/computers.
I noticed that this has only happened since updating CWP to the latest update that was released today.
(Scroll the image to the right to see the error)
* PS: This is happening both when accessing via "cpanel.domain.tld" as well as the hostname "srv1.domain.tld:2083" - logging into CWP Admin panel works fine. All accounts will not login via CWP user and they're all showing this "uerror". Creating new CWP User accounts also show the same login error, so it's effecting the entire CWP User panel. I had an old tab opened which was logged into CWP User and that's working fine to navigate the account, but as soon as I logged out and tried to log back in, the "uerror" occurs. Have tried on alternative browsers/IP/computers.
4
CentOS-WebPanel Bugs / CWP WebServers Config Editor Invalid Argument
« on: May 08, 2020, 01:33:23 PM »
Hi there,
When visiting the WebServers Config Editor under the WebServer Settings tab, I've noticed that CWP is throwing an error:
Obviously, can't view the PHP file as it's obfuscated... Any advice?
When visiting the WebServers Config Editor under the WebServer Settings tab, I've noticed that CWP is throwing an error:
Code: [Select]
Warning: Invalid argument supplied for foreach() in /usr/local/cwpsrv/htdocs/resources/admin/modules/WebServers_conf_editor.php on line 0Obviously, can't view the PHP file as it's obfuscated... Any advice?
5
Apache / cPanel Account Backup to CWP
« on: May 04, 2020, 09:26:06 AM »
Hey guys, hopefully someone can point me in the right direction here -
I've backed up my cPanel account from my shared, and managed web-hosting.
Everything looks fine, some files didn't transfer accross (such as sub-domain files, but that's no big deal)
I mainly wanted emails to transfer across, which seems fine thus far.
For some reason, the main domain will not load the "public_html", instead, it is showing the CentOS WP landing page.
I've checked all folders within /home/USERNAME, and unfortunately, I can not locate the placeholder index page.
Loading the account folder by navigating to the HOSTNAME URL /~USERNAME (IE: https://srv1.xxx.xyz/~USERNAME/) successfully loads the correct files, within the /home/USERNAME/public_html - so somewhere's gone wrong, as in the domain itself is not correctly pointing to the /home/USERNAME/public_html
Creating a sub-domain on the URL works fine, and I am able to access it, so there's something wrong with the main domain not pointing to the public_html folder. Again, when I access the site using the above link (srv1.xxx.xyz....), it views the content fine - accessing the domain loads the CWP landing page.
I've looked inside the /usr/local/apache/conf.d/vhosts/ files, and I've compared the main domain, to another known-working domain, and they look fine. I'm not sure what other files I should check and cross-reference, as again, the domain is simply not pointing to the correct domain (I assume)
I've backed up my cPanel account from my shared, and managed web-hosting.
Everything looks fine, some files didn't transfer accross (such as sub-domain files, but that's no big deal)
I mainly wanted emails to transfer across, which seems fine thus far.
For some reason, the main domain will not load the "public_html", instead, it is showing the CentOS WP landing page.
I've checked all folders within /home/USERNAME, and unfortunately, I can not locate the placeholder index page.
Loading the account folder by navigating to the HOSTNAME URL /~USERNAME (IE: https://srv1.xxx.xyz/~USERNAME/) successfully loads the correct files, within the /home/USERNAME/public_html - so somewhere's gone wrong, as in the domain itself is not correctly pointing to the /home/USERNAME/public_html
Creating a sub-domain on the URL works fine, and I am able to access it, so there's something wrong with the main domain not pointing to the public_html folder. Again, when I access the site using the above link (srv1.xxx.xyz....), it views the content fine - accessing the domain loads the CWP landing page.
I've looked inside the /usr/local/apache/conf.d/vhosts/ files, and I've compared the main domain, to another known-working domain, and they look fine. I'm not sure what other files I should check and cross-reference, as again, the domain is simply not pointing to the correct domain (I assume)
Pages: [1]
