Prerequisites

1. A cPanel account with root access.
2. PHP-FPM enabled on your server.
3. Basic knowledge of how to use the cPanel interface

1. Enabling PHP-FPM in cPanel

Before managing php.ini directives, ensure PHP-FPM is enabled for your domain:

i. For this, First Log in to WHM 

ii. Then, Navigate to MultiPHP Manager and select User Domain settings.

iii. In the domain section, Select your domain and check whether “PHP-FPM” is enabled for the domain, if not then enable it.

2. php.ini File

It is always important to understand the current PHP configuration. You can find the existing php.ini file by creating a PHP info page.

Now, Create a file named phpinfo.php in your web root directory. Here I am using the root directory as: /home/testdomain.com/public_html/

#cd /home/testdomain.com/public_html/
# vim phpinfo.php

Add the following content to the file:

<?php

phpinfo();

?>

After changing the necessary file permissions, Access this file via your web browser (e.g., http://testdomain.com/phpinfo.php).

In the page, Verify that PHP_FPM is active or not.

3. Review and Modify php.ini Directives

You can review the domain’s php.ini directives in cPanel’s MultiPHP INI Editor interface (cPanel » Home » Software » MultiPHP INI Editor).

In WHM, you can review this in (WHM » Home » Software » MultiPHP INI Editor). You can find the system set default php.ini directive there.

For Global Modifications:

First, SSH into your server.

And then look for /var/cpanel/ApachePHPFPM/system_pool_defaults.yaml. If it does not already exist, create it.

To modify the.yaml file, use the following command:

#vim /var/cpanel/ApachePHPFPM/system_pool_defaults.yaml

Add the desired PHP-FPM pools and directives. for example you can set the memory limit of 120 MB by adding the following:

php_admin_value_memory_limit: { name: 'php_admin_value[memory_limit]', value: 120M }

For Modifying specific php.ini directives for a domain, 

Create the file /var/cpanel/userdata/username/testdomain.com.php-fpm.yaml, then edit it with a text editor to add the directives you want to modify.

for example, to disable the passthru and system directives, use:

#vim /var/cpanel/userdata/username/testdomain.com.php-fpm.yaml

_is_present: 1
php_admin_value_disable_functions: { name: 'php_admin_value[disable_functions]', value: passthru,system }

To enable all the directives, using the following:

_is_present: 1
php_admin_value_disable_functions: { name: 'php_admin_value[disable_functions]', value: none }

4. Regenerate the configuration and restart the services

After the modifications has been made, Regenerate the php-fpm configuration: 

#/usr/local/cpanel/scripts/php_fpm_config --rebuild

Restart the apache and php-fpm services for the changes to take effect:

#/usr/local/cpanel/scripts/restartsrv_apache_php_fpm
#/usr/local/cpanel/scripts/restartsrv_httpd

By following these steps, you can effectively manage your PHP settings, ensuring optimised performance.

If you have any questions or need personalized assistance with “How to Manage PHP.ini Directives with PHP FPM on a cPanel Server” , don’t hesitate to reach out Skynats.

The post How to Manage PHP.ini Directives with PHP FPM on a cPanel Server appeared first on Server Management Services | Cloud Management | Skynats.

The backups will be currently kept on a functional server. To move the backups to the backup server’s /backup2 mount, we need to configure the backups.

Let’s look at how to set up the backup configuration:

Setting up Backup Configuration :

Firstly, ensure that the disk is correctly mounted in the backup server ;

#df -h

The server has correctly mounted the drive/backup2.

We can now set up the backup to the /backup2 drive.

To do this, create a new user called “backup_user” with the home directory set to /backup2/. You can use the useradd command with the -m option to create the user and automatically generate the home directory. Here’s how you can do it:

#useradd -m -d /backup2/backup_user backup_user.

Running this command will create the user “backup_user”, with the home directory set to /backup2/backup_user.

Now we can configure additional backup destination in live server’s WHM:

Log in to the WHM dashboard and type Backup Configuration into the search field.

An option for multiple backup destinations should be available in the Backup Configuration interface. Click on Create New Destination.

Enter the below information in the form that appears ;

Backup Destination Type: Select the “custom” type

Destination Name: Enter the name as you wish.

Backup Directory: Enter the path to the backup destination. Here I’m using the directory name as ‘backups’. The backups will be stored in /backup2/backup_user/backups.

Remote Host: Enter the backup server’s ip address. (for me, it’s 10.xxx.xxx.110)

Port: The ssh port that the system uses to communicate with the remote server

Remote account username: Provide the remote user account name. Here i’m using the user ‘backup_user’.

Authentication Type: The authentication type which the system use to connect to remote server. 

Timeout: The number of seconds that the system will wait for a response from the remote server.

Save Configuration: After filling out the necessary details, click on the “Save” or “Add Destination” button to save your configuration.

After saving, cPanel may undergo a verification step to ensure access to the specified backup destination. Upon completion of the validation process, the backup can be enabled.

By following these steps, you will be able to configure that the additional backup destination to a custom drive in cPanel. However, backups will be stored in the directory associated with the user you’ve created, ensuring their proper storage and accessibility.

Our Support Team is available to help if you encounter any issues or errors.

The post Setting Up Additional Backup Destination to a Custom Drive in a cPanel server appeared first on Server Management Services | Cloud Management | Skynats.

Expertise Beyond Boundaries:

Outsourcing server management opens doors to a pool of specialized skills and expertise. Dedicated professionals, equipped with in-depth knowledge of the latest technologies and best practices, ensure that your servers operate seamlessly.

Cost-Efficiency Unleashed:

Beyond the technical prowess, outsourcing often translates to significant cost savings. Instead of bearing the expenses of hiring and training an in-house team, businesses can opt for predictable, fixed costs, mitigating the need for hefty infrastructure investments.

Focus on Core Competencies:

By shifting the responsibility of day-to-day server maintenance and troubleshooting, organizations can redirect their focus towards core competencies and strategic initiatives. This freedom cultivates a more productive environment, fostering innovation and growth.

Vigilant 24/7 Monitoring:

Outsourced server management comes hand-in-hand with round-the-clock monitoring and support. This proactive approach ensures rapid issue detection and resolution, curbing downtime and potential disruptions.

Scalability on Demand:

The flexibility to scale server resources as business needs evolve is a notable advantage of outsourcing. Whether it’s during peak periods or expansions, adjusting server capacities becomes a seamless process.

Fortified Security Measures:

Entrusting servers to specialized teams often means fortifying security measures. These providers are armed with advanced security protocols, reducing the vulnerability to cyber threats and data breaches.

Reliable Redundancy Plans:

Reliable backup and disaster recovery plans are integral parts of outsourced server management. These plans assure data integrity and act as a safety net in the event of system failures.

Compliance and Regulation Adherence:

Outsourcing partners are well-versed in compliance requirements and industry regulations, ensuring server operations align with relevant standards.

Seamless Updates and Maintenance:

Routine updates, patch management, and system maintenance are diligently handled by outsourced teams. This ensures that servers remain current and secure without draining internal resources.

Mitigating Risks, Amplifying Results:

Outsourcing mitigates risks associated with server management, including hardware failures, technical challenges, or internal skill gaps, while enhancing operational efficiency.

Service Excellence with SLAs:

Clear Service Level Agreements (SLAs) with outsourced providers guarantee specific service levels, performance benchmarks, and uptime, ensuring accountability for maintaining agreed-upon standards.

Outsourcing server management isn’t just about delegating tasks; it’s a strategic move that unleashes a myriad of benefits. Leveraging external expertise not only optimizes operational efficiency but also empowers organizations to thrive in a rapidly evolving digital landscape.

The post Benefits of Outsourcing Server Management appeared first on Server Management Services | Cloud Management | Skynats.

The Current Scenario

CentOS 7 is presently the only supported version of CentOS; it will continue to receive security updates and bug fixes from the community until June 2024.

Now, CentOS 7 is in the “Maintenance Support 2” phase, during which only critical and crucial security updates and high-priority bug fixes are issued.

Red Hat Software, the organization that supported the CentOS community project, has announced that it will cease producing stable CentOS versions to match the Red Hat Enterprise Linux (RHEL) release in December 2020. CentOS 8 was the final stable community release of the RHEL , with no minor versions to follow; which reached the end of life on December 31, 2021.  

Barriers Ahead

Normally, you would migrate to CentOS 8 during the available window of time. But, as CentOS 8 has reached its end of life, switching to CentOS 8 is no longer a possibility, and there is no CentOS 9.

The majority of enterprise users and production workloads cannot utilize CentOS Stream outside of a development environment. Due to its rolling nature, it is not an identical replica of the corresponding RHEL release, hence application compatibility can easily be broken. Hence it is recommended to move to a different Linux distribution.

Remember that the fact that CentOS 7 will no longer receive updates after its end-of-life date does not eliminate the emergence of new vulnerabilities. The increased scrutiny of code has led to an increase in vulnerabilities affecting older operating system versions and older software in general.

The Future

The viable replacement for CentOS are:

Rocky Linux: A community-maintained distribution that aims to replace CentOS, led by the original CentOS developer. Rocky Linux 8 will be supported to 2029. Essentially CentOS with a new name, but not fully functional.

AlmaLinux: Maintained by CloudLinux, a firm that also offers the commercial CloudLinux OS. According to their FAQ, CloudLinux will continue to support AlmaLinux until 2029.

Oracle Linux: managed by Oracle, with commercial support available as an option. It is not meant to replace CentOS, but it should function.

Ubuntu: It is from the Debian Linux family and uses additional software packages than CentOS. Ubuntu is not an RPM-based Linux distribution, however.

Elevate Project by Almalinux

The Elevate project is an initiative to support migrations between the major versions of RHEL derivatives. The ELevate project supports only CentOS repositories. It doesn’t support other external repositories. Also, there can be issues while migrating large servers.

cPanel/WHM with Centos 7 

cPanel & WHM version 110 will be the last version that supports CentOS 7. Support for version 110 will end on June 30, 2024. We encourage you to migrate to an AlmaLinux 8 or CloudLinux™ 8 server before June 30, 2024.

Click HERE to read the official cPanel support page.

We need to set up a new AlmaLinux 8 or CloudLinux™ 8 server with cPanel/WHM and migrate the websites to it before June 30, 2024. 

There is a cPanel Elevate project available that provides a script to upgrade an existing cPanel & WHM CentOS 7 server installation to AlmaLinux 8 or Rocky Linux 8. But this is an experimental project and there is no guarantee that the system will be stable after the migration as per the official documentation. Installation of this software could cause significant functionality failures, even for experienced administrators.  Please click HERE to know more about this project. 

It is a best practice to set up a new AlmaLinux 8 or CloudLinux™ 8 server with cPanel/WHM and migrate the websites to it for a stable production environment. Our experienced support team is available to take over the complete setup and migration for any production server.

Alright, then, what CentOS alternative distribution do you want to shift to? Have you already decided? Or Are you confused about selecting an alternative distribution? Regardless of at which stage you are, we, the Skynats team are here to help you.

The post CentOS 7 End of Life appeared first on Server Management Services | Cloud Management | Skynats.

A network issue happens while processing your cPanel login request. Why?

Occasionally, the following error message appears when attempting to access the cPanel account: We might be interested to know if the given network connection is still strong. We will examine some of the potential causes of the error in detail in this article, along with solutions for those causes.

“A network error happened while trying to send your login request. Please try once more. Get in touch with your network service provider if this problem continues.”

We’ll look at a few potential causes of the issue in this article and offer some fixes.

Error: Causes and Solutions

Cause 1: Using a non-SSL connection to access cPanel. Using http://cpanel.yourdomainname as an example

Solution: The servers are configured so that cPanel can only receive SSL-encrypted communications. To resolve this issue and sign into cPanel in this instance, use a different link. For instance, use the URL http://yourdomainname/cpanel to log in to cPanel. The user will be forwarded to the hostname of the server with SSL turned on.

Cause 2: On Linux systems, log in to the cPanel account using the root account.

Solution: Using the “root” username does not allow us to access cPanel. For Web Host Manager, only the “root” username is functional. In this situation, the hostname might be set up with the domain name. Update the hostname to something like “server.mydomain.com” to resolve the issue.

Cause 3: Incorrect server proxies that send requests to https://cpanel.domain> to the cPanel backend. Due to an issue with the server and the most recent version of cPanel, the https backend proxying is not operating as intended.

Solution: In this instance, commenting out the HTTPS rewrite rules in /usr/local/apache/conf/httpd.conf will temporarily solve the issue. Reinstalling the server with the most recent version is a long-lasting solution.

Cause 4: Several unsuccessful cPanel login actions led to Internet IP being blacklisted in the “cPHulk Brute Force Protection.”

Solution: In this instance, the blacklisting needs to be removed. Since the primary server has been blacklisted, we must use a different one. Attempt to log in from one terminal to the other while whitelisting the IP address from “cPHulk Brute Force Protection.” Now that the error is gone, we can log in.

Cause 5: Outdated browser caches

Solution: Using a different browser or clearing the browser’s cache. It helps to lessen the likelihood of using outdated forms. increasing cPanel’s performance as a result.

Are you looking for an answer to another query? Contact our technical support team.

The post Network Error Occurred While cPanel Login Request appeared first on Server Management Services | Cloud Management | Skynats.

On our cPanel server management plan with WordPress website hosted, these type of issues with troubleshooted and get fixed.

Causes Of Missed Scheduled Post Error in WordPress :

The wordpress hosting environment used or some plugins may cause this issue. WordPress uses a technology called cron or WordPress cron to automatically publish the post at the correct time. If your hosting environment or plugins used are affecting the cron jobs, then it will cause WordPress to miss some scheduled tasks to publish the posts.

How To Fix This Issue?

First important thing is to install a Missed Scheduled Post Publisher plugin in your WordPress. There are no settings needed for you to configure for this plugin to work. This plugin checks every 15 minutes on your website to see if any scheduled posts in cron have missed the scheduled time.

If it finds any missed scheduled item there, it will change the status from scheduled to published. This plugin will not create any impact on WordPress site speed.

Troubleshooting Missed Schedule Post Error in WordPress :

1. Check your WordPress time zone settings

You must set your time zone for WordPress first. Sometimes users forget to set the time zone and it will leads to use other different time zone for wordpress and it will create missed schedule error for posts.

You can set your correct time zone in the WordPress dashboard by simply goes to “Settings –> General page” and scroll down the Timezone option and from there you can choose the required timezone for you. Don’t forget to “Save Changes” button to save the settings.

2. Clear the WordPress cache

Sometimes the WordPress caching plugin also causes missed scheduled post issues, so we have to check that the WordPress caching plugin is properly configured to clear the cache for your WordPress sites at regular intervals. If the missed scheduled posts error gets then try to clear your WordPress cache.

3. Increase the WordPress Memory Limit

The WordPress Memory limit issue for your WordPress site will also cause this error. You can increase the memory limit for WordPress to use more server memory by adding the given line in your “wp-config.php” file ;

define('WP_MEMORY_LIMIT','500M');

We are Managing many WordPress websites for our clients which will cover all the server related issues with your WordPress websites. If you are facing any issues with your WordPress sites our technical support team is available at any time.

The post How To Fix Missed Schedule Post Error in WordPress appeared first on Server Management Services | Cloud Management | Skynats.