Home Web Hosting

Web Hosting

Web Hosting
Dennis Nind
By Dennis Nind
• 85 articles

How to change your PHP Version and PHP Settings

At Brixly, we strive to provide you with the flexibility and control you need to optimize your website's performance. One way we do this is by allowing you to change your PHP version and settings directly from your cPanel account. This guide will walk you through the process. Changing the PHP Version Brixly's servers support multiple versions of PHP. To change the PHP version used for your account, follow these steps: 1. Log in to your cPanel account. 2. Open the PHP Selector. You can find this in the Software section of your cPanel home page, labeled as "Select PHP Version". 3. cPanel will display the current PHP version. To change the PHP version, select the version you want to use from the "Current PHP Version" list box, then click "Set as current". The new PHP version will take effect immediately. Adjusting PHP Settings and Extensions In addition to changing the PHP version, you can also modify various PHP settings directly from cPanel. This includes enabling and disabling PHP extensions, as well as adjusting configuration directives such as 'allow_url_fopen', 'error_log', and many more. To change your PHP settings, follow these steps: 1. Log in to your cPanel account. 2. Open the PHP Selector, located in the Software section of your cPanel home page. 3. On the Extensions tab, select which extensions you want to enable for the current PHP version. To enable an extension, select the checkbox next to the extension name. To disable an extension, clear the checkbox. 4. To reset the extension list to the default configuration, click "Reset to default" in the top right corner. 5. To change settings for the current PHP version, click the "Options" tab near the top of the page. 6. Click the value next to the setting you want to modify. Depending on the type of setting, a list box may appear with predefined settings that you can choose, or a text box may appear so you can type the value. 7. Changes are saved automatically and take effect immediately. By following these steps, you can easily customize your PHP settings to suit your specific needs, all without the need to configure and maintain custom php.ini files.

Last updated on Jun 12, 2025

PHP 500 Errors and How to Resolve Them

PHP 500 errors, also known as "Internal Server Errors," can be a common occurrence when working with web applications. These errors are typically not server-related issues but are usually caused by issues within the code of the application. This guide will help you understand these errors better and provide you with solutions on how to resolve them. Understanding PHP 500 Errors A PHP 500 error is a generic server-side error that indicates an internal server error. It doesn't provide specific details about what exactly went wrong, making it a bit challenging to diagnose and fix. However, these errors often occur due to issues with the PHP code or server configuration. If the error is intermittent, it's likely that the application is hitting memory limits. On the other hand, if the error is consistent, it's usually an indication of a problem within the application's code. How to Resolve Intermittent PHP 500 Errors Increase the PHP Memory Limit If your PHP 500 errors are intermittent, it's likely that your application is hitting its memory limits. Here's how to increase the PHP memory limit: 1. Log in to your cPanel account. 2. Navigate to the "Select PHP Version" under the Software section. 3. Click on "Switch to PHP Options". 4. Find the 'memory_limit' option and increase it to a higher value, such as 256M or 512M. 5. Click 'Save' to apply the changes. Remember, increasing the memory limit should be done cautiously, as setting it too high can exhaust your server resources. Persistent PHP 500 Errors - Diagnose the Error If the PHP 500 error is not intermittent, it's usually due to a problem within the application's code. To diagnose the error, you can check the error_log file within your account. This file contains a record of all errors encountered by the application and can provide valuable insights into what's causing the PHP 500 error. To access the error_log file: 1. Log in to your cPanel account. 2. Navigate to the File Manager. 3. Locate and open the error_log file. This file is typically located in the public_html directory. Enable WordPress Debug Mode If your application is a WordPress site, you can enable the WordPress WP_DEBUG mode to view the errors. WP_DEBUG is a PHP constant that can help diagnose WordPress-specific issues. To enable WP_DEBUG: 1. Access your WordPress files (you can do this via FTP or through cPanel's File Manager). 2. Open the wp-config.php file. 3. Locate the line that says /* That's all, stop editing! Happy blogging. */. 4. Just before that line, add the following code: define( 'WP_DEBUG', true );. 5. Save and close the file. Now, when you visit your site, any errors will be displayed on the page, which can help you diagnose the issue. Display Errors on the Page In some cases, you might want to display errors directly on the page for debugging purposes. You can do this by modifying your .htaccess file: 1. Access your .htaccess file (this is usually located in the public_html directory). 2. Add the following lines to the file: php_flag display_errors On php_value error_reporting E_ALL 1. Save and close the file. Now, any PHP errors will be displayed directly on your web pages. Contact Support If you've tried the above solutions and are still experiencing PHP 500 errors, it might be time to contact our support team. Our experts can help diagnose and resolve the issue, ensuring your website runs smoothly and efficiently. Please note, that resolving PHP issues is beyond scope of our support, and should be handled by a PHP Developer. However, our team will do our best to assist guide in the resolution of solving such issues, where possible. 

Last updated on Jun 12, 2025

I have received an email about LVE / Resource Usage

CloudLinux improves the stability of a server by limiting each client in an isolated, secure environment called a Lightweight Virtual Environment (LVE), a kernel technology developed by CloudLinux. In shared hosting, the most common reason for downtime is a single account slowing down other accounts on the server. If one customer is using an unfair amount of resources (e.g. due to being under a DDoS attack, poorly written script, etc.), the server would become slow or go down completely, affecting all other customers on the server. With CloudLinux, we are able to isolate the impact to the offending tenant only, while all other sites remain unaffected. CloudLinux improves the general stability and performance of the server by imposing limits on the number of resources that can be consumed by a single user. When an account hits the LVE limits allocated to it, a snapshot is generated allowing you to see which processes are responsible for those limits being hit and can be reviewed from the 'Resource Usage' section of cPanel.  Also, we now send alerts when an account hits the LVE limits, so that you can be informed if an account has performance issues, code issues or potential malware or if the account simply requires more resources via an upgrade. I have received an alert! what do I need to do? The first step is to review the 'Resource Usage' screen in cPanel, and see if you can trace what processes were responsible for the high usage at the time.  From there, the solution would depend on the root cause but is typically an issue at application level such as poorly written PHP scripts, outdated or poor quality plugins, larger numbers of plugins or even potentially malware. As a hosting provider we are responsible for the hosting infrastructure, as opposed to the applications that run within the hosting platform so we are unable to diagnose PHP related issues or problems via support - therefore it may be best in some cases, to reach out to a developer for further assistance. If the account resource usage is genuine requirement, and is just a 'resource heavy' site then the best course of action would be to upgrade the account to a more suitable plan, such as our Premium Hosting. Who will be notified? If you are a shared hosting client, you will be informed by email from noreply@cloudns.io If you are a reseller, you will be informed of the LVE faults for any of the sites directly by email which will come from noreply@cloudns.io This email will outline the number of 'faults' (the number of times the LVE has been hit), along with the accounts affected.  Please note, that for the benefit of white-labelling, we do not at present send notifications to your customers directly.  How often will I be notified?  We will send usage alerts for any accounts hitting their LVE limits every 12 hours.  How many LVE faults need to be reported before I am notified? As some of the LVE restrictions only 'slow down' a site, as opposed to taking a site entirely offline we don't notify for every individual fault. Instead, we send notifications if an account exceeds its limits more than 100 times spanning the 12 hour period. What if I ignore the alerts? If an account is only receiving a small number of LVE faults, and it mainly surrounds CPU usage or IO, the chances are that there would be no implications at all, other than a slowdown of the site during these fault periods.  However, if you have accounts that are exceeding the resource limits 'excessively', we reserve the right to suspend an account to prevent further resource consumption.  We will suspend an account if it receives more than 5000 LVE faults in the space of 60 minutes. The reason for this is that 'SIGKILL' is a kernel process that is called at the point of an LVE fault occurring (which is what triggers the 503 error). This process itself can have negative impacts on the performance and stability of the server overall when called simultaneously over short periods of time.

Last updated on Jun 12, 2025

How do I update the SOA record of the DNS zones under my reseller account?

The SOA record (or the 'start of authority' record) stores information about a domain names administrative contact. The SOA record also contains some additional information, such as the duration of time that the server should wait before domain refreshes (TTL).  All DNS zones need an SOA record in order to conform to IETF standards. SOA records are also important for zone transfers. Example of an SOA record: 33d61391d16393d08f5ce53d7d0a556d45b7fea0cf4a285640ad8b1b923c780732381070a00cfb54?t=3501bc571490323d6a5d80494a49dd05 The 'RNAME' value here represents the administrator's email address, which can be confusing because it is missing the ‘@’ sign, but in an SOA record, admin.example.com is the equivalent of admin@example.com. How do I customise the SOA record? The SOA record is generated based on the email address of your reseller account. You can confirm which email address is in use, by going to WHM -> List Accounts, and checking the 'Email' field against the reseller account.  The correct method to change this for future DNS zones would be to update the email address to a contact email address you are happy to show within your domains DNS zones. In most cases, this will be something similar to 'admin@yourdomain.com'. It is possible, however, to have your own email address differ, from the one displayed on the SOA. To do so, go to WHM -> Edit Zone Templates From here, you will have 3 options, each of which will need to have the same update.  Please ensure you follow these steps exactly; otherwise, you risk invalidating the DNS zones of your clients, which will prevent them from loading. To change the SOA record, you would need to replace the following... @ %nsttl%    IN SOA %nameserver%. %rpemail%. ( With the following... @ %nsttl% IN SOA %nameserver%. admin.yourdomain.tld. ( IMPORTANT: Note the trailing '.', and the fact that the @ has been replaced with the '.'. This is required for the SOA to be considered valid!

Last updated on Jun 12, 2025

How to generate a full cPanel backup of your account

This guide will walk you through the process of generating a comprehensive backup of your website using cPanel on Brixly. Note: We take automated backups of all accounts either daily, or hourly (depending on the selected plan). These backups can be managed through the JetBackup interface in cPanel.  Step 1: Accessing Your cPanel Start by logging into your cPanel account from your Brixly client area. Step 2: Locating the Backup Wizard Once you're in your cPanel dashboard, navigate to the 'Files' section. Here, you'll find the 'Backup Wizard' option. Click on it to proceed. Step 3: Initiating the Backup Process In the Backup Wizard, click on the 'Backup' button to start the backup process. Step 4: Choosing Full Backup Next, choose the 'Full Backup' option. This will ensure that all aspects of your website are included in the backup. Step 5: Selecting the Backup Destination The following screen will present you with multiple destinations for your backup. For the purpose of this guide, we'll choose to create the backup within your account. This allows you to easily download it later via FTP or File Manager. Select 'Home Directory' from the dropdown menu. You also have the option to enter an email address. If provided, a notification will be sent to this address once the backup is complete. After filling in the necessary details, click on 'Generate Backup'. Step 6: Downloading the Backup After receiving the notification that your backup is complete, go back to your cPanel and select 'File Manager'. Click on the 'Home' icon using the folder tree on the left. Finally, right-click on the backup file and select 'Download'. And there you have it! You've successfully created and downloaded a full backup of your website. Note: It's a good practice to back up your website regularly. This ensures that you have a recent version to restore from in case of any unforeseen issues.

Last updated on Jun 12, 2025

How to setup a NodeJS application on cPanel

Node.js is a popular open-source runtime environment that allows you to create server-side applications. It is based on the V8 JavaScript engine and uses asynchronous I/O to handle requests efficiently. cPanel is a popular web hosting control panel that makes it easy to manage your website. It includes several features that make it easy to set up and deploy Node.js applications.  This guide will show you how to create a Node.js application in cPanel. Prerequisites Before you can start, you will need the following: - A web hosting account with cPanel - A Node.js application Step 1: Create a New Application Log in to your cPanel account and click on the Software tab. Then, click on the Node.js App button. On the next page, enter a name for your application and select a directory to store it in. Then, click on the Create button. Step 2: Install NPM Packages Once your application has been created, you will need to install any NPM packages that your application requires. To do this, click on the Edit button next to your application. On the next page, click on the Run NPM Install button. This will install any NPM packages that are listed in your application's package.json file. Step 3: Create a package.json File If your application does not already have a package.json file, you will need to create one. To do this, go to the Files section of cPanel and click on the File Manager button. In the File Manager, navigate to the directory where your application is stored. Then, right-click and select New File. In the text editor that opens, type the following and save the file as package.json: { "name": "my-application", "version": "1.0.0", "description": "My Node.js application", "main": "index.js" } Step 4: Start Your Application Once you have installed any NPM packages and created a package.json file, you can start your application. To do this, click on the Start button next to your application. Your application will now be running and accessible through your web browser. Conclusion In this guide, we have shown you how to set up a Node.js application in cPanel. We hope this guide has been helpful. If you have any questions, please feel free to contact us.

Last updated on Jun 12, 2025

How to Improve a Slow WordPress or WooCommerce Dashboard

If you're experiencing a sluggish WooCommerce admin panel, it's time to take action. A slow admin panel can be a major hindrance to your productivity and overall user experience. This guide will provide you with a range of strategies to speed up your WooCommerce backend/dashboard. Misconceptions often arise when users experience a sluggish WooCommerce admin panel. It is important to understand that the perceived slowness is not necessarily a result of a slow server or hosting environment. In fact, more often, the issue may lie within the application itself. To address this concern and improve productivity and user experience, this guide offers various strategies to optimize and speed up your WooCommerce backend/dashboard. By implementing these strategies, you can overcome performance challenges and enhance the overall efficiency of your WooCommerce admin panel. Disable High CPU Plugins Start by deactivating plugins one by one and testing your admin speed after each deactivation. Some plugins can slow down the admin by increasing CPU usage or adding CSS/JS to the frontend. Use tools like Query Monitor to identify your slowest plugins and consider replacing them with more lightweight alternatives. Manage Your Cache Plugin’s Preloading and Cache Clearing Cache plugins can automatically clear the entire cache when certain actions are triggered. This can put a strain on your server and slow down both your admin and frontend. Consider disabling automatic cache clearing and setting up a cron job to clear the cache once per day instead. Enable Redis Redis is an efficient object cache that can significantly improve database performance. We have an article on how to enable this. Enable OPcache OPcache can enhance PHP performance and CPU utilization, speeding up your admin. In cPanel, you can find it in the PHP Extensions menu. Remove WooCommerce Bloat Disable WooCommerce features you're not using to reduce bloat. The Disable WooCommerce Bloat plugin can help with this, allowing you to disable various features and dashboard items. Deep Clean Your Database Use a plugin like WP-Optimize to deep clean your database. This plugin allows you to delete tables left behind by old plugins and take database backups. Clear WooCommerce Customer Sessions and Transients Clearing customer sessions and transients can help if your wp-options table is growing too quickly due to ineffective cron jobs or bots creating sessions. Disable WP-Cron WP-Cron runs on every page load and schedules automated tasks. Instead of running it on every page load, you can schedule it to run every 90 minutes or so. Limit Heartbeat, Autosaves, and Post Revisions The Heartbeat API can generate a request every 15-60 seconds, which can slow down your admin. Consider disabling it in the frontend and backend, and limiting it in the post editor. Protect Your WP-Login Page Moving your wp-login page can help protect your admin and stop spam bots from hitting your default login page. Cache the WordPress Admin Some plugins, like LiteSpeed Cache, allow you to cache the wp-admin. However, this may result in you seeing expired data, so proceed with caution. Upgrade to PHP 8 Upgrading to PHP 8 can improve the speed of your admin. Check your PHP version in the WooCommerce server environment and upgrade in your hosting account. Increase Memory Limit Increasing your memory limit can also speed up your admin. WooCommerce recommends 256MB, but you can increase it to as high as 1GB on our hosting plans.  Remove Your Page Builder Page builders can slow down your admin and your website due to the extra CSS/JS they add. Consider removing your page builder and opting for a lightweight theme instead. Enable Argo Smart Routing Cloudflare's Argo Smart Routing can speed up dynamic requests on both your admin and frontend. It can load assets 30% faster on average. Use Diagnostic Tools to Find Bottlenecks Use plugins like Query Monitor, WP Hosting Benchmark, and WP Healthcheck to diagnose or speed up your slow WooCommerce admin. These tools can help you identify slow queries, view CPU/memory utilization, and check your WordPress/PHP/mySQL version, server, etc. Utilize PHP X-Ray PHP X-Ray is a powerful tool that can help you identify performance issues in your PHP code. It provides detailed insights into how your code is running, allowing you to pinpoint bottlenecks and optimize your application. We have a guide on how to use the X-Ray plugin here. Remember, a slow WooCommerce admin is often related to a specific plugin (or plugin setting), high CPU usage, a bloated database, or inadequate hosting infrastructure. Implementing these strategies can help speed up your admin and improve your overall user experience.

Last updated on Jun 12, 2025

Deceptive Site Ahead - How to Request Google to Review a Compromised Site

If Google suspects your website contains malware or misleading content, or is being used for phishing attacks, it may blacklist your site. Visitors to your site will then see a 'Deceptive Site Ahead' warning, indicating that the site they are about to visit could pose a security risk. If your site is displaying this warning, you need to address the security threats and then notify Google to review your site and remove the warning. This guide will walk you through the process of requesting Google to review your site and remove the 'Deceptive Site Ahead' warning. Steps to Request Google to Review a Compromised Site: 1. Sign in to your Google Search Console account using your administrator credentials. 2. On the Dashboard, navigate to the 'Security issues' tab in the left sidebar. 3. Scroll down and check the box that says 'I have fixed these issues', then click on the 'Request a Review' button. You will need to provide detailed information about the steps you've taken to resolve the security issues on your site. The review process may take a few days, and during this time, the 'Deceptive Site Ahead' warning will continue to appear on your site. Remember, it's **crucial **to fully address all security threats on your site before requesting a review from Google. We would also recommend reviewing the following articles... https://support.brixly.uk/en/knowledgebase/article/malware-scanner-how-to-scan-your-sites-for-malware https://support.brixly.uk/en/knowledgebase/article/steps-to-cleaning-malware-from-your-website

Last updated on Jun 12, 2025

How to Optimise Your WordPress Database

As your WordPress site grows, your database also expands. This growth includes previous versions of posts and pages, user accounts, and other 'transient' data. Over time, this extra data can slow down your site. Regularly cleaning your database can help maintain optimal performance. The LiteSpeed Database Optimizer, part of the LiteSpeed cache plugin, is an excellent tool for this task. Steps to Optimize Your WordPress Database Before you begin, ensure you have a backup of your site. While database optimization is generally safe, it's always good to have a backup in case something goes wrong. 1. Access the Database Optimizer: In your WordPress dashboard, go to LiteSpeed Cache > Manage. Then click the DB Optimizer tab. 2. Understand the Optimization Options: Some buttons have blue check-marks, indicating that the area has already been cleaned. Red crosses indicate areas that need optimization. 3. Clean All: This button cleans up everything at once, except for Optimize Tables and Clean CSS/JS Optimizer. 4. Post Revisions: This option removes all old post revisions from the database, leaving only the currently-published version of each post. 5. Auto Drafts: WordPress automatically saves drafts when you edit a post. This option removes these automatic drafts. 6. Trashed Posts and Comments: These options permanently delete any posts, pages, or comments that have been placed in the Trash. 7. Spam Comments: This option permanently erases comments that have been marked as spam. 8. Trackbacks & Pingbacks: This option clears trackbacks and pingbacks from the database. 9. Expired Transients: This option clears all of the expired transients from the database. 10. All Transients: This option clears all of the transients in the database, whether expired or not. 11. Optimize Tables: This button optimizes the database tables. This function is not included in a Clean All. 12. Clean CSS/JS Optimizer: If you use the Minification and/or Combination functions for CSS and/or Javascript, you can clean up the related data with this button. This function is not included in a Clean All. Remember, if you're unsure about something, don't hesitate to contact the the Brixly support team. We're here to help!

Last updated on Jun 12, 2025

Steps to Cleaning Malware from Your Website

Malware infections can be complex and challenging to resolve. In some cases, it may be best to seek advice from a developer to resolve the issue and prevent future occurrences. This guide will walk you through the basic steps to clean malware from your website. Basic Steps for Cleaning Malware 1. Remove Infected Files: If the files are required, replace them with clean copies. You can obtain these from any available JetBackups. We strongly recommend maintaining your own independent off-site backups too. 2. Update Passwords: Update all passwords, including cPanel and website admin logins. 3. Update CMS and Plugins: Ensure any Content Management System (CMS) you are using, including any plugins, are up to date. It's often better to completely remove and replace any plugins/extensions with a freshly downloaded clean version. 4. Use the Highest Version of PHP Possible: You can change the version of PHP you're using within cPanel. These basic steps apply whether you have a static site, or are using a CMS like WordPress, Drupal, Joomla, or Magento. Dealing with Sophisticated Attacks More sophisticated attacks can damage your site's database. In these cases, your options would be to either have the database cleaned or restore the database from a backup. If your site is running any kind of e-commerce system or collects data from users that gets stored in the database, any data collected between the time of any backup and when you decide to restore the database will be lost. In these cases, you may decide that having your site and database professionally cleaned is a better option. WordPress Specific Malware Cleaning 1. Update WordPress to the latest version. 2. Change all passwords, including cPanel and database. 3. Check WordPress for any additional users that might have been created. 4. Change all WordPress user passwords. 5. Change your WordPress access hashes in wp-config.php. You can obtain new salts from wordpress.org. 6. Update all plugins (remove and replace with fresh copies from the source or WordPress repository). 7. Update all themes (and remove any unused ones). 8. Review the site for evidence of any malicious files. External Assistance / Cleaning Services for WordPress If you are not confident cleaning your site yourself, there are services available that will not only clean your site but also offer continued protection via a WordPress Application Firewall (WAF). Both Wordfence and Sucuri offer free and paid versions of their WAF plugins. They also both offer site cleaning services. Remember, if you're unsure about something, don't hesitate to reach out to the Brixly support team. We're here to help!

Last updated on Jun 12, 2025

Using FileZilla to Upload Files via SFTP(SSH) or FTPS(SSL/TLS)

FileZilla is a popular open-source File Transfer Protocol (FTP) client that you can use to upload or download files from your web hosting server. This guide will show you how to set up FileZilla for SFTP (SSH connections) and FTPS (Explicit SSL/TLS) connections. Downloading and Installing FileZilla First, you'll need to download and install FileZilla. Visit the FileZilla project website and download the appropriate version for your system. Setting Up FTPS (SSL/TLS) 1. Open FileZilla and select 'Site Manager' from the 'File' menu. 2. Click the 'New Site' button and type in a name for your new site. 3. On the 'General' tab, enter the following details: - Host: Your server's hostname or domain name - Port: 21 - Protocol: FTP - File Transfer Protocol - Encryption: Require explicit FTP over TLS - Logon Type: Normal - User: Your cPanel username - Password: Your cPanel password 1. Click the 'Transfer Settings' tab. 2. Select the 'Passive' transfer mode and limit the number of simultaneous connections to 10. 3. Click 'OK' to save your settings. You'll see an 'Unknown certificate' prompt the first time you connect. Check that the 'Common Name' matches the server you are connecting to, then click 'OK' to confirm. Setting Up SFTP (SSH FTP) 1. Open FileZilla and select 'Site Manager' from the 'File' menu. 2. Click the 'New Site' button and type in a name for your new site. 3. On the 'General' tab, enter the following details: - Host: Your server's hostname or domain name - Port: 22 - Protocol: SFTP - Logon Type: Normal - User: Your cPanel username - Password: Your cPanel password 1. Click the 'Advanced' tab. 2. Set the 'Default local directory' to where you keep the website files for this project. 3. Set the 'Default remote directory' to /home//public_html/ (replace  with your cPanel username). 4. Click the 'Transfer Settings' tab. 5. Select the 'Passive' transfer mode and limit the number of simultaneous connections to 10. 6. Click 'OK' to save your settings. Remember, if you're unsure about something, don't hesitate to reach out to our Brixly support team. We're here to help!

Last updated on Jun 12, 2025

Where Should I Upload My Website Files?

Understanding where to upload your website files is crucial for your website to function correctly. This guide will help you understand where to place your files in cPanel. The Short Answer The short answer to this question is the public_html/ directory. Further Detail Every cPanel account has what is called a home directory. This is the directory that you would normally see when you connect via FTP, SFTP, or SSH using your account's primary cPanel user details. A brand new cPanel account home directory looks a little like this: .bash_logout .bash_profile .bashrc .contactemail .cpanel/ etc/ .htpasswds/ mail/ public_ftp/ public_html/ tmp/ www@ Depending on your software, you may not see the files and directories that begin with a dot (e.g., .htpasswds). In any case, never delete or modify any of these files or directories unless you know exactly what you are doing. Your website files should be uploaded into the public_html/ directory. For example, if your domain was mywebsite.com, then a file located at public_html/mypicture.jpg would be served to the internet as http://mywebsite.com/mypicture.jpg. The www item is nothing more than a shortcut to the public_html/ directory - you can treat it as the same thing if you find that easier. What about the Other Files and Directories? All of the other files and directories are required to ensure your web hosting and email accounts function correctly. Therefore, if you are new to cPanel, stick purely to the public_html/ directory and you won't break your hosting account. Remember, if you're unsure about something, don't hesitate to reach out to our Brixly support team. We're here to help!

Last updated on Jun 12, 2025

What File and Directory Permissions Should I Use for My Web Files?

Understanding the correct permissions for your hosting files and directories is crucial for the security and functionality of your website. This guide will help you set the right permissions for your files and directories in cPanel. Files Files should always be uploaded and set to chmod 644. However, there are a few important exceptions: - PHP files containing sensitive information: For example, configuration files containing database usernames and passwords (like WordPress's wp-config.php). For security reasons, these files should be chmod 600. In fact, it's a good practice to set all PHP web scripts to chmod 600. These files don't need the execute bit set because they are interpreted by PHP. - Scripts run from the shell command line or crontab using the required shebang (PHP, Perl, or Python): These files should be chmod 700 because they are executed directly by your Linux user account. - Scripts run from the cgi-bin or other directory as a CGI script using the required shebang: These should also be chmod 700 because they are executed directly by your Linux user account. - .htaccess file: These files can be chmod 644, but a more secure solution is to set them chmod 444 (effectively read-only). This offers more protection against some simple file injection attacks. When you upload files using cPanel File Manager, those files will be set to chmod 644 automatically. Unless your FTP software has been specially configured to set uploaded files to different permissions, then newly uploaded files will also be set to chmod 644 automatically. Directories Directories should always be uploaded and set to chmod 755. When you upload files using cPanel File Manager, directories will be set to chmod 755 automatically. Unless your FTP software has been specially configured to upload directories with different permissions, then newly created directories will also be set to chmod 755 automatically. What if the Installation Notes for My PHP Web Application Say Otherwise? Software developers often prioritize making their software work over the security of your website. You might be told that directories should be chmod 777 or even that files need to be chmod 755, but if you are talking about a PHP-based website, then PHP files will operate just fine chmod 600 or chmod 644. This is because LiteSpeed serves PHP files via the suEXEC CGI. PHP files are served under your cPanel username's security context. And because your username owns your web files, you only have to grant Read and Write permissions to the owner (thus, chmod 600). If in doubt, and you want your site to be as secure as possible, please log a support ticket via your Brixly Client Area. We're here to help!

Last updated on Jun 12, 2025

How to Create and Manage MySQL Databases in cPanel

MySQL databases are essential for many web applications, including content management systems and ecommerce platforms. Here's how you can create and manage MySQL databases in cPanel: Step 1: Log in to cPanel First, log in to your cPanel account. This is typically done by adding /cpanel to the end of your domain name in your web browser (e.g., www.yourdomain.com/cpanel). Step 2: Access MySQL Databases Once you're logged in, look for the 'Databases' section on your cPanel home screen and click on 'MySQL Databases'. Step 3: Create a New Database On the MySQL Databases page, you'll see a form under the 'Create New Database' heading. Enter a name for your new database and click 'Create Database'. You'll see a confirmation message when the database has been created successfully. Step 4: Create a Database User Scroll down to the 'MySQL Users' section and find the 'Add New User' form. Enter a username and password for the new user. You can use the 'Password Generator' button to generate a strong password. Click 'Create User' to create the new user. Step 5: Add User to the Database Now, you need to give your new user permission to access your new database. Scroll down to the 'Add User To Database' section. Select the user and the database from the dropdown menus and click 'Add'. Step 6: Set Database Privileges You'll now see a list of privileges. If you want the user to have full access to the database, check the box next to 'ALL PRIVILEGES'. Otherwise, select the individual privileges as needed. Click 'Make Changes' to save your selections. Step 7: Manage Your Databases You can manage your databases at any time from the MySQL Databases page. Here, you can check a database, repair a database, or delete a database. You can also modify user privileges or delete users from databases. Remember, managing databases is a powerful action, so always be careful when deleting or modifying databases or users. If you're unsure about something, don't hesitate to reach out to our support team. We're here to help!

Last updated on Jun 12, 2025

How to Manage Files in cPanel

Managing your website's files is a crucial part of maintaining your online presence. cPanel's File Manager provides an easy-to-use interface that allows you to handle these tasks directly from your web browser. Here's a step-by-step guide on how to use it: Step 1: Log in to cPanel First, log in to your cPanel account. This is typically done by adding /cpanel to the end of your domain name in your web browser (e.g., www.yourdomain.com/cpanel). Step 2: Access the File Manager Once you're logged in, look for the 'Files' section on your cPanel home screen and click on 'File Manager'. Step 3: Navigate Through Your Files The File Manager will open in a new tab. On the left side, you'll see a directory tree that represents the file structure of your account. You can click on any folder in the tree to view its contents in the main panel on the right. Step 4: Create, Upload, and Delete Files - To create a new file or folder, click on the '+File' or '+Folder' button at the top-left corner of the page, enter the name of the file or folder, and click 'Create'. - To upload a file, click on the 'Upload' button at the top of the page, then select the file from your computer. The file will be uploaded to the currently selected directory. - To delete a file or folder, select it by clicking on its name, then click the 'Delete' button at the top of the page. Confirm the deletion in the popup that appears. Step 5: Edit Files To edit a file, select it by clicking on its name, then click the 'Edit' button at the top of the page. Make your changes in the text editor that appears, then click 'Save Changes' at the top-right corner of the page. Step 6: Move and Copy Files To move or copy a file, select it, then click the 'Move' or 'Copy' button at the top of the page. In the popup that appears, enter the file path where you want to move or copy the file, then click 'Move File(s)' or 'Copy File(s)'. Step 7: Compress and Extract Files To compress files into a .zip archive, select them, then click the 'Compress' button at the top of the page. Choose 'Zip Archive', enter a name for the archive, and click 'Compress File(s)'. To extract a .zip archive, select it, then click the 'Extract' button at the top of the page. Remember, the File Manager is a powerful tool, so always be careful when deleting or modifying files. If you're unsure about something, don't hesitate to reach out to our support team. We're here to help!

Last updated on Jun 12, 2025

How to Create Email Accounts in cPanel

Creating an email account through cPanel is a straightforward process. This guide will walk you through the steps to create a new email account. Step 1: Log in to cPanel First, you'll need to log in to your cPanel account. This is typically done by adding /cpanel to the end of your domain name in your web browser (e.g., www.yourdomain.com/cpanel). Step 2: Navigate to Email Accounts Once logged in, look for the 'Email' section on your cPanel home screen and click on 'Email Accounts'. Step 3: Create a New Email Account On the 'Email Accounts' page, click on the 'Create' button. Step 4: Enter the New Email Information You'll now see the 'Create An Email Account' form. Here, you'll need to: - Domain: If you have multiple domains, select the domain you want to associate with this email account from the dropdown menu. - Username: Enter the username for the email account. This will be the part of the email before the '@' symbol. - Password: Enter a strong password for the email account. You can also use the 'Generate' button to create a strong password automatically. - Storage Space: Specify the amount of storage space for the email account. You can choose 'Unlimited' if you don't want to limit the storage space. Step 5: Create the Account Once you've filled out the form, click the 'Create' button at the bottom of the page. You should see a confirmation message that the email account has been created successfully. And that's it! You've successfully created a new email account in cPanel. You can now log in to this email account via webmail or set it up in your preferred email client.

Last updated on Jun 12, 2025

WordPress - My site is showing a maintenance page. How do I disable it?

As part of its automatic update system, WordPress has a built-in maintenance mode that it activates whenever you update your software, themes, or plugins from the WordPress dashboard. You can see a message addressing this in the WordPress update interface whenever you run an update: 27daebd366acb28be06ccfb6f5771dd7ee4faae2c238904ebb4ace23f1dcbc4f4d3a95547cb91779?t=bf850c5ede3758afe00fd1fa6b8a034f  Most of the time, the handoff from “maintenance mode” to “working site” takes just a few seconds, and you never even know your site was in maintenance mode. But sometimes, things do go wrong. Some potential causes are: - You accidentally close your browser tab in the middle of an automatic update - You’re trying to automatically update a considerable number of plugins/themes at once - There’s a compatibility problem that causes a glitch As a result, you persistently see this message when you try to visit your site: Briefly unavailable for scheduled maintenance. Check back in a minute. How to Fix WordPress Stuck In Maintenance Mode When WordPress puts itself into maintenance mode, it creates a file named “.maintenance” in the root folder of your WordPress site. This is the same folder that contains the following: - wp-admin folder - wp-config.php To fix the WordPress stuck-in maintenance mode problem, you’ll need to connect to your server via FTP and delete that file. Once you’ve connected to your site via FTP, find the “.maintenance” file in your root folder and delete it. 2d148d7b46bd42095406b1bbe73823961ed1b0535b9c2f4e940f0439a2382a3578ddca34b5360f5d?t=00fa6a839f47a4ab4519342ad7f0931d Once you delete that file, your site should function as expected. It is also recommended that you clear the cache on your WordPress site.  Assuming the failure wasn’t due to a compatibility issue, you should rerun the upgrade to ensure your site runs the latest version.

Last updated on Jun 12, 2025

Litespeed Cache - Presets for WordPress

Introducing LSCache Presets for WordPress: the easiest way to optimize your WordPress site using the Litespeed Cache plugin. Litespeed Cache Presets are a pre-tuned set of options, which can be used for optimizing any WordPress site using Litespeed Cache. You can configure your ideal level of optimization with just a few clicks! How to use a LiteSpeed Cache preset LSCache Presets for WordPress In the WordPress Dashboard, you can find Presets under the LiteSpeed Cache menu. If you don’t see it, make sure you’re using v5.3 or higher of the plugin. To use a preset, press the appropriate Apply Preset button on the Standard Presets tab, and answer OK when prompted to continue. Your old settings will be backed up, and the new preset settings will be applied. Be sure to test your site and make sure everything is working as expected. This is especially important if you’ve chosen one of the more aggressive presets. If the settings in the preset causes a problem for your site, you can revert back to your previous settings via the History section at the bottom of the tab. How to revert back The History section appears on the Standard Presets tab if you have previously applied a preset. Every time you apply a preset, a new entry is added to the history, along with a link that will allow you to revert back to the previous settings. Simply click the link, and everything will return to the way it once was. How to choose a preset Presets are listed in order of risk and skill level. If you are new to caching, and you prefer to “set it and forget it” then stick with Essentials or Basic. On the other hand, if you are a seasoned pro, or you’re an adventurous tinkerer, you might want to try one of the presets at the end of the list. Here is a basic overview of the official LiteSpeed preset collection. (You can take a look at our presets documentation, if you’d like the full details for each preset.) Essentials This preset enables caching, sets a higher default TTL (time to live) , and enables browser cache. These are easy, low-risk ways to improve your site’s loading time. Essentials will never break your site’s formatting, and will not require any tweaking whatsoever. Even if (or, maybe, especially if) you have no experience with caching, you can apply this preset with confidence. Basic Basic enables everything that Essentials does, but it adds image optimization to speed up image loading time, and mobile cache to allow you to cache a mobile version of your website that may be different from the desktop version. This preset is appropriate for enthusiastic beginners who want to ease into a basic level of optimization. You shouldn’t have to make any adjustments to your settings in order to make this work. Image optimization is a QUIC.cloud service, so you will need a domain key in order to make this work. If you don’t have one, the plugin will prompt you and show you how to get one. The domain key and the image optimization service are both free. Advanced Here’s where things start to get more complicated. Advanced enables everything in Basic, and then adds a large number of page optimization features. While this plugin potentially requires some maintenance from you, it has the potential to greatly improve your site’s page speed score. Page optimization features sometimes highlight incompatibilities among CSS or Javascript used on your site. The incompatible files need to be excluded from optimization. If you enable this preset, you should be comfortable setting up CSS or JS exclusions via the plugin admin. A domain key is required. Aggressive Added to the Advanced features are CSS and JS Combine, Critical CSS, Unique CSS and more. CCSS and UCSS are both QUIC.cloud services which may incur fees, and domain key is required. These features are excellent for page speed scores, and they really speed up your site. But they also have considerable potential to require intervention. Only use this preset if you are comfortable looking for conflicts and excluding files from optimization. Extreme As you might expect from a preset called Extreme, this one enables the maximum level of optimization possible. Page speed sites love sites with all of these optimizations. As with previous presets, a domain key is required, as is some expertise. These settings are likely to introduce CSS or JS conflicts, especially if you have a lot of plugins or a complicated theme. Frequently Asked Questions I am new to Litespeed Cache, which preset should I apply? We suggest trying the Advanced preset because it takes a balanced approach to optimization and speed. You shouldn’t need to manually tweak many settings, but if you do experience difficulty, you can always revert to your previous settings, or try the Basic preset. Can I modify Litespeed Cache settings after setting up this preset? Yes, it is absolutely possible to edit any options after applying a preset. Presets are just an easy way to get started. They give you a good base optimization to start with, but many complex websites will need more fine-tuning to achieve their best possible page score or user experience. If I don’t like a preset I’ve applied, can I undo it? Yes! Please see How to revert back above. Conclusion These Standard Presets, which were developed by our LiteSpeed team, provide a simple way to apply preconfigured optimization settings for every comfort level. But this is just a start! Eventually, we hope to include Presets that have been submitted by members of our community to cover a wide variety of site styles and needs. In the meantime, give our Standard Presets a try, and let us know what you think!

Last updated on Jun 12, 2025

WordPress Multisite Subdomains

When using WordPress Multisites with Subdomains, you need to ensure the subdomain is added to cPanel/DirectAdmin to be used. cPanel You can do this on cPanel via: cPanel -> Domains -> Create a new domain Here you will enter the name for the subdomain and also the document root; this should share the same Document root as the WordPress Multisite: d3c160e0fdb40d058818911901e2d33a5219c3e7c20a5b024c6d27f7b862e312fea1447c5e635222?t=14a43ca6def17b3450adf767fa648c97 This will usually be the public_html directory, but if your WordPress Multisite is based on an addon domain will be located on a different path. If you've already created the subdomain and need to update the document root from the Domains screen, instead click manage next to the subdomain: b3c5bb00f7b8edbbd20abe7ba4dc9c20a99abda54e90165d3c3a0ce0b59b4cf2b18005ecf42dee27?t=81712bc689d015c583837c7802650d63From here, set a new document root and hit update: e133528683f4b2d2243a78eced6d93288e147ff9100d9e107f6377632e91a16b2c6e6231b67534c4?t=e78ee259d73a20f796b54a7679a4492d DirectAdmin On DirectAdmin the process is similar, add a subdomain via: **DirectAdmin (User Level) -> Subdomain Management -> Add Subdomain ** b28cb2012f6a1134ba878b1f0c5f9b7135d98b30b39a3103fcf78d8ea013945697cdb1d9f757dd87?t=4587b4cee5b8ee3f361edc49a6859e06 On DirectAdmin, we need to set the Document Root after creating the subdomain, by default DirectAdmin will set this to be: /domains/yourdomain/public_html/subdomain As such once the subdomain is created click the pencil button next to Docroot: Then set the public_html and private_html to custom and to use the same Document root as the WordPress Multisite: a3d330d0636cf34573f38a403ef8a4b1eb4bdf2d0fbc75df9813dfe85b5d5faf722fc592e0d51415?t=9ab2f22ec98c2ebf2a4ef1843ad18059 Hit save and wait a few minutes as DirectAdmin build the new document root configuration; you should now be able to visit and use the new document root.

Last updated on Jun 12, 2025

How to view enable and view errors on a WordPress installation (WP_DEBUG)

When adding custom code such as PHP or JavaScript, there are times when you may need to find any possible errors in your code. When enabled, WordPress debug will log any errors detected on your site. This can be key to finding the source of an issue or just learning more details about any possible errors on your site. Enabling debug in WordPress To enable debugging on your site, please follow the steps below. 1) Locating the wp-config.php file By default, WordPress debug will be disabled. To enable it, you’ll need to access your site files through either FTP or cPanel. 2) Editing the wp-config.php file Once your site files are open, you’ll need to open wp-config.php for editing. This will be located in the root folder of your site. Open wp-config file to enable debugging in WordPress The wp-config file contains site-specific configuration settings, such as database information and, potentially, settings added by your hosting provider. For debugging, you’ll need to find this line of code (will generally be near bottom of file): 3) Adding your debug code Copy and paste this code snippet over the line of code mentioned in Step 2. // Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true ); This code will need to be to inserted **before *the comment / That’s all, stop editing! Happy blogging. */ in the wp-config,php file. enable debugging inside the wp-config.php file This will enable debugging and, importantly, prevent any logged data from displaying on your site. Instead, a debug log will be saved to your site files. 4) Replicating the issue After saving these changes to wp-config.php, you’ll need to return to your site and replicate the issue you saw earlier. This will ensure that it gets recorded in the new error log. 5) Viewing the debug log Then, you can return to your site files and open /wp-content/debug.log. The contents of an error log can vary a lot depending on the cause and number of issues, but now you should be able to see extra details, such as a file path to the source of a code error, to help you better track down the issue. ('WP_DEBUG',false); Accessing the website at this point, would show you errors / debug output so that you can diagnose the problem with your site.

Last updated on Jun 12, 2025

How do I install a wildcard SSL Certificate via LetsEncrypt?

Our automatic SSL installation process (powered by AutoSSL) will automatically install Sectigo SSL certificates. Sectigo SSL certificates offer optimal coverage, completely automatically and free of charge. In addition, they also do not 'rate limit' requests, making it an ideal solution for us as shared hosting providers. LetsEncrypt however, also offers you additional functionality, such as the ability to support wildcard coverage, and also supports redirection tracing which can be simpler for some sites hosted behind Cloudflare, or other CDNs / proxy services. Also, Sectigo does restrict certain regions from issuance entirely, as outlined above. If your use-case/scenario requires a LetsEncrypt SSL certificate (such as the need to cover wildcards), then we now provide you with the ability to install a free LetsEncrypt SSL certificate from within cPanel... cPanel -> Let's Encrypt™ SSL The interface is split into two sections. The first section will list all of your domains that have “Let’s Encrypt™” certificates issued, their expiry, and options to remove, reinstall and view them: The second section will list all of the domains configured in your account that are eligible to have a certificate issued. Please note, redirected domains are unable to have a certificate issued. user-guide-issue.png Prerequisites There are two important prerequisites to be met in order for a certificate to be able to issue: - The domain name(s) you want to be signed must be pointing to this cPanel server already - The Let’s Encrypt™ CA must be able to visit http://your-domain/.well-known/acme-challenge/xxx successfully. These directories/files will be created automatically, but you should take care that you do not have any .htaccess rules that prevent access. Most users will fulfil these requirements automatically. Issuing Process First, click the + Issue button to the right of the domain you wish to issue a certificate for. Please note, any you will be able to select any extra domains to include on the certificate in the next screen. user-guide-confirm.png Ensure that all of the domains you wish to include in this certificate are selected as included and click ‘Issue’. The process may take anywhere from 10 to 45 seconds, so do not navigate away from the page. At completion, the keys and certificates should be installed on the server, with a success message: user-guide-installed.png Certificate renewal is automatic in the background.

Last updated on Jun 12, 2025

JetBackup - How to create 'Snapshot Backups'

Backups are taken of all accounts on our shared and reseller services daily. However, we do understand there are certain scenarios where you may wish to take a backup prior to making significant changes. In those cases, we would always recommend using a plugin, or script to generate a backup immediately before making those changes, storing the backup off-site.  However, we do also offer the ability for you to perform 'snapshot backups' via the JetBackup 5 interface in cPanel. This is an incremental backup, taken manually via the control panel which you can later use as disaster recovery, following your updates / changes. For any individual cPanel account, you are able to take a maximum of 1 snapshot which will be stored for 2 days. After which, the backup will automatically be deleted. If any further snapshots are taken, please note the first will be removed.  The snapshot feature may not be available if your account exceeds 5GB in size or has a large volume on inodes (at this point, you would be required to use a plugin or script to generate on-demand backups).  To take a snapshot backup of your account go to JetBackup 5 via cPanel, then select 'Accounts'... a787fe3ab1efc02d403a60387b857f6c2f65bb623d4568e79aa00d28ff7406cb86be3ed8f6ca396a?t=3f3f09625f81542fdcba33abb69ce8e3 From here, select an account and choose the option 'Create Backup on Demand' Once selected, you will be asked to confirm that you would like to proceed... 9fb138cb077cd94b37fe3a721aa2a9199ef5cfcafbe7b9f3fd3ff8a3f12a0026f9f9acf19afc82aa?t=d158e4789f2a10e0d99f54cd2a7e6dbc You can then monitor whether or not that backup has been completed, via the 'Queue' interface... 464989922f5b20d90d62abf5310fdb3c638177efbfee262dca9284d3d4472b523b87080292a1fce4?t=e6bf0d0e20ea98895f3bb96d65785d90

Last updated on Jun 12, 2025

What are 'mixed content' errors and how do I resolve them?

What are 'Mixed Content' Errors? 'Mixed Content' errors occur when a secure HTTPS webpage is trying to load resources, such as images, videos, stylesheets or scripts, over an insecure HTTP connection. This can pose a security risk as the insecure content can be manipulated by attackers, leading to compromised user data or altered webpage behavior. How to View 'Mixed Content' Errors To view 'Mixed Content' errors, you need to access the browser's console. Here's how to do it in popular browsers: - Google Chrome: Right-click anywhere on the webpage, select 'Inspect', and then click on the 'Console' tab. - Firefox: Right-click on the webpage, select 'Inspect Element', and then click on the 'Console' tab. - Safari: First, enable the Develop menu in Safari's Advanced preferences. Then, right-click on the webpage, select 'Inspect Element', and click on the 'Console' tab. In the console, 'Mixed Content' errors typically appear as warnings stating that the page is loading mixed content. How to Fix 'Mixed Content' Errors The most effective way to fix 'Mixed Content' errors in WordPress is to update all HTTP content to HTTPS. This can be a tedious task if done manually, especially for larger websites. That's why we recommend using the 'Search and Replace' plugin for WordPress. This plugin allows you to directly replace all instances of HTTP URLs with their HTTPS counterparts in your database. Here's a step-by-step guide: 1. Install and activate the 'Search and Replace' plugin in your WordPress dashboard. 2. Navigate to 'Tools' > 'Search & Replace' in your dashboard. 3. In the 'Search for' field, enter your website's URL starting with 'http://'. 4. In the 'Replace with' field, enter your website's URL starting with 'https://'. 5. Click on the 'Do Search & Replace' button. Remember to back up your database before using the plugin, as the changes made are irreversible. By ensuring all content is loaded over a secure HTTPS connection, you can eliminate 'Mixed Content' errors, improving your website's security and user trust.

Last updated on Jun 12, 2025

Understanding and Resolving the 503 Error: Resource Limit Reached

A 503 error is a server-side response code that indicates the server is temporarily unable to handle the request. This can occur for a variety of reasons, but in the context of a web hosting environment, it often suggests that the account is hitting its LVE (Lightweight Virtual Environment) limits, also known as "Resource Limits Reached". What are LVE Limits? LVE limits are designed to provide stability on the server by restricting each individual cPanel account to a set of resource limits, similar to how a Virtual Private Server (VPS) works. Each individual account typically has 1 CPU, 1GB RAM, and 30 Entry Processes, unless otherwise stated on your package. Only if the account hits its LVE limits would it display a 503 error, which is referred to as a 'fault'. How to Resolve a 503 Error The LVE limits are fairly high for a shared account, but they can be scaled if required by upgrading an account to the Elastic Cloud service. However, before considering an upgrade, it's recommended to review the plugins the site uses and check for any abnormal traffic. Here are a few things to check: Review Your Plugins Disable any unnecessary plugins. Ideally, temporarily disable them all, wait a couple of minutes, then re-enable them to see if that resolves the issue. Enable Caching Try to enable caching on the site. We highly recommend Bolt-Cache, which was developed in-house and is available from cPanel -> Bolt-Cache. This can significantly reduce resource usage. Check Your Cron Jobs Cron Jobs that run heavy processes too frequently can cause an account to max out its LVE limits. Review Backup Processes Backup plugins or scripts can cause an account to max out its LVE limits due to the disk/memory-intensive processes required to generate the backups. Monitor MySQL Processes Processes that consume large MySQL throughput can also cause issues. Check for Attacks It's also possible the account is under some kind of attack. You can check your LVE usage via the cPanel -> CPU and concurrent connections screen in cPanel. By analyzing the Snapshots as described in the document, you will be able to see the processes running at the time of hitting your limit. Considering an Upgrade If you've followed all the steps above and your account is still hitting its resource limits, it may be that your site is simply outgrowing its current hosting plan. This is especially likely if the resource limits are being reached due to genuine traffic and usage, rather than due to issues like unnecessary plugins or attacks. At Brixly, we offer a wide range of hosting plans designed to cater to all kinds of requirements. If your site is growing and needs more resources to deliver a smooth and fast experience to its users, it might be time to consider an upgrade. Our sales team is always ready to discuss your needs and help you choose the best plan for your site. Whether you need more CPU power, RAM, or Entry Processes, we can provide a plan that offers the resources you need. Remember, upgrading your hosting plan is a normal part of the website growth process. As your site attracts more visitors and offers more features, it will naturally require more resources. Upgrading your plan is a positive step that shows your site is successful and growing. So, if you're consistently hitting your resource limits and believe it's time for an upgrade, don't hesitate to reach out to our sales team. We're here to help you make the right decision for your site's future. Need More Help? If the above steps don't resolve the issue, we at Brixly would be more than happy to investigate this further for you. If you've spent some time reviewing the above and still can't resolve the issue, please don't hesitate to get in touch.

Last updated on Jun 12, 2025

How to create a WordPress Staging Site with Softaculous

Staging environments are crucial for website development and maintenance. They provide a safe space where you can test changes and updates without affecting your live website. This guide will walk you through how to create and manage a WordPress staging site using Softaculous, a one-click application installer available in cPanel. Understanding Staging A staging environment is a clone of your live website. It allows you to preview changes, test updates, install plugins, and more before applying these modifications to your live site. This practice helps prevent downtime and unexpected errors on your live website. Creating a Staging Site with Softaculous Softaculous simplifies the process of setting up a staging site. You can create a staging copy of your live website with just a click. Here's how: 1. Log in to your cPanel account. 2. Click on the Softaculous icon or link to open the Softaculous Enduser Panel. 3. Go to the Installations page. 4. Choose the installation for which you want to create a staging copy. 5. Click on the "Create Staging" icon. 6. Fill in the staging installation details. You can set up the staging site in a subdirectory or a subdomain. We recommend using a separate subdomain, such as 'staging.yourdomain.com' for your staging site. Remember to create the subdomain through the cPanel interface first. 7. Click on the "Create Staging" button. Making Changes in the Staging Environment Once your staging site is set up, you can log in to the WordPress admin panel using the same credentials as your live site. Here, you can make any changes you need, such as: - Installing or updating plugins - Installing themes - Updating WordPress Core - Adding or editing pages Pushing Changes to the Live Site After you've made changes in the staging environment and are satisfied with them, you can push these changes to your live website. Here's how: 1. Choose the staging installation you want to push to live. 2. Click on the "Push To Live" icon. 3. Decide how you want to merge the changes. You can choose to update just the files, the full database, only the database structure, or only the data from the database tables. 4. Click the "Push to Live" button. Softaculous will then push the changes to your live website.  We would always encourage making Snapshot Backups of your website before pushing changes to live using JetBackup, or creating a full cPanel backup to download to your local machine Conclusion The staging feature in Softaculous is a powerful tool that can save you time and hassle when managing your WordPress site. It allows you to test changes safely before applying them to your live site, reducing the risk of errors and downtime.

Last updated on Jun 12, 2025

How to Configure WordPress to use SMTP for Sending Emails

Sending emails from WordPress is a crucial function that powers everything from admin notifications to password resets. By default, WordPress uses the PHP mail function to send emails. However, this method is not always reliable and can result in your emails landing in the spam folder. To improve email deliverability, you can configure WordPress to use Simple Mail Transfer Protocol (SMTP) instead. Why Use SMTP Instead of PHP Mail? SMTP is a protocol used for sending emails. Unlike PHP Mail, which is a function in PHP, SMTP is a dedicated protocol designed for delivering emails reliably. When you use SMTP, your emails are less likely to end up in the spam folder. This is because SMTP uses proper authentication, which increases the credibility of your emails. Configuring WordPress to Use SMTP To configure WordPress to use SMTP, you'll need to use a WordPress plugin that allows SMTP configuration. There are many such plugins available, but for the purpose of this guide, we'll use the WP Mail SMTP plugin. 1. Log in to your WordPress admin dashboard. 2. Navigate to Plugins > Add New. 3. Search for "WP Mail SMTP" and install the plugin. 4. After the plugin is installed, activate it. 5. Navigate to WP Mail SMTP in your WordPress dashboard. 6. In the settings, you'll need to enter your SMTP details. These can be found in your cPanel under Email Accounts > Connect Devices. The settings are as follows: - SMTP Host: mail.yourdomain.com (replace 'yourdomain' with your actual domain name) - SMTP Port: 587 - Encryption: TLS - Auto TLS: On - Authentication: On - SMTP Username: Your email address - SMTP Password: The password to access the email address 1. Click "Save Settings" to save your changes. Now, WordPress will use SMTP to send emails, which should improve email deliverability. Using an External Email Service If you're using an external email service, you'll need to obtain the SMTP server and credentials from your provider. However, some providers may require an API key or have other requirements. If this is the case, you can still relay messages from our servers via SMTP without affecting inbound mail. To do this, create an email account in your control panel with us and use your server's hostname as the SMTP server. By configuring WordPress to use SMTP, you can improve the reliability of your email delivery and ensure that your emails reach their intended recipients. If you encounter any issues during this process, our support team is here to help.

Last updated on Jun 12, 2025

Forcing HTTPS:// Redirection for Your Website

There are several methods to force HTTPS:// on your website, depending on your setup and preferences. Here are three commonly used approaches: Using a WordPress Plugin (Really Simple SSL): - In your WordPress Dashboard, go to the Plugins section. - Click on "Add New" and search for the "Really Simple SSL" plugin. - Install and activate the plugin. - After activation, the plugin will automatically detect your SSL certificate and configure your site to use HTTPS://. - Additionally, ensure that your 'Site URL' in Settings -> General also begins with 'HTTPS://' for proper configuration. Using cPanel: - Log in to your cPanel account. - Navigate to the 'Domains' section. - Select the desired domain and locate the option to force HTTPS://. - Enable the HTTPS:// redirection for your domain. - Save the changes, and your site will now redirect all HTTP traffic to HTTPS://. Using the .htaccess file: - Locate the .htaccess file in the root folder of your website. - Open the file and add the following code at the beginning (above any existing rules): RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.com/$1 [R,L] Replace 'www.example.com' with your actual domain name. - Save the changes to the .htaccess file. - This code will redirect all web traffic to the HTTPS:// version of your site. - To force HTTPS:// for a specific domain or folder, use the following code: RewriteEngine On RewriteCond %{HTTP_HOST} ^example\.com [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.com/$1 [R,L] Replace 'example.com' with the domain name you want to force to HTTPS://. Replace 'www.example.com' with your actual domain name. If you want to force SSL on a specific folder, use this code: RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteCond %{REQUEST_URI} folder RewriteRule ^(.*)$ https://www.example.com/folder/$1 [R,L] Replace 'folder' with the actual folder name you want to force SSL on. Replace 'www.example.com/folder' with your actual domain name and folder. Remember to save the changes to your configuration file after making modifications. With these methods, you can ensure that your website is accessed securely over HTTPS://, providing enhanced security for your visitors.

Last updated on Jun 12, 2025

JetBackup - How to restore your account files or databases

JetBackup5 is our powerful backup and restore tool. It allows us to take daily incremental backups of all sites stored on our servers and provides a simple and intuitive interface to restore your account data.  1. **Let's fire up the JetBackup 5 module from within cPanel **20bbb7bb2e44ee6c8e0d88e0454b741bb3caa63eb66b9f726d7a7a836b8aa694a69a8d79b6746693?t=6ca57d3aa5953b28b5fe87c1b549c7d0 2. **Head over to the Restore & Download menu. ** On the left-hand navigation menu click the highlighted icon. Wait a few seconds and you will be presented with the available backups of your account.  Use the drop-down menu to select the backup you would like to restore from! f4c1d8eb073382a833efa781e18f559b919c62467bb07cb0ab00a1373742ea3fa068f35074653902?t=eb69bed3bb813ce22eb40d0f748dec9eIf you would like to complete a full restore ( including cPanel preferences and Email Accounts ) then click Restore.  If you would like to customise the Restore then follow the next point. 1. **Customize the restore ( Optional ) ** Click "Show Advanced Settings". Wait a few seconds and a table will be presented to you. From here you can choose specifically what you would like to restore. You are able to restore the following options: Panel Config - Your cPanel Settings and Preferences Home Directory - All of your files and folders ( you can choose specific files ) Cron Jobs - The Crons set up to run automatically. Often used by WordPress. DB - Your Databases  DB Users - The users configured to interact with your Databases. If you restore a database you will also need to restore these. Zones - Your DNS settings ( if utilised by our nameservers ) Certificates - Your SSL Certificates ( HTTPS ) Emails - All of your Email Accounts! FTP - Your FTP users. Please note that it is not possible to merge emails from a backup with an email accounts current emails, restoring this will overwrite any emails currently within the email account. 1. The final step Your confirmation screen. Confirm the items you want to restore and click "Restore Selected Items" b6224a470ae1e22f0b9f158b99ad3eb57495e6a2be55ae7b3ea8147864b4e177e709066e0fcf2cdf?t=b5bb8e52d720166b713dd183ed692bdf If you require any assistance in restoring your account or files. Feel free to raise a Support Ticket from the Client Area.

Last updated on Jun 12, 2025

JetBackup - JetBackup UI Showing 500 Error

If you are trying to restore an account using JetBackup and encounter a 500 / Fatal error within the JetBackup interface, don't panic. This issue is commonly encountered during the restoration process and is typically temporary. Why does this happen? The error occurs because the restoration process modifies and restores files critical to the cPanel interface. Specifically, when a full account is restored, the account is first terminated, and then the full account is restored. Your session becomes invalid if you remain logged into the cPanel interface during this process. This is because the account associated with your session has been terminated and is in the process of being restored. As a result, the cPanel UI can create issues, one of which is the 500 / Fatal error. What is the solution? The solution to this issue is simple: patience. Wait until the restore process completes. Once the process is finished, log out of the cPanel interface and then log back in. This will establish a new session that is associated with the restored account, and you should no longer encounter the 500 / Fatal error within the JetBackup interface. Remember, restoring an account is a complex process that involves many moving parts. Temporary errors are to be expected. However, once the process is complete, everything should return to normal. If you continue to experience issues after the restoration process is complete and you've logged back into the cPanel interface, please contact our support team for further assistance.

Last updated on Jun 12, 2025

Understanding Our Internal Auditing and Cleanup Process

In the realm of web hosting, maintaining server efficiency and security is paramount. As part of our commitment to providing top-notch services, we implement an internal auditing and cleanup process to manage disk space and ensure the smooth operation of our servers. This article outlines the types of files automatically removed during this process and explains our fair usage policies. Types of Files Automatically Removed 1. DirectAdmin and cPanel Backups: We remove backups stored in /home//user_backups/ and various cPanel backup files like /home//backup-, /home//cpmove-, and similar patterns in other directories. 2. Temporary Files and Logs: Temporary files such as those in /home//tmp/Cpanel_ and old log files, especially compressed ones (.gz), found in /var/log and other log directories are deleted. 3. Large Files in Root Directory: Files larger than 1GB, particularly those named cpmove*, located in /root are removed. 4. Old and Unused Files in Various Directories: This includes cleaning out /usr/local/src/, /home//.trash/, and backups and caches in directories like /home//backupbuddy_backups/, /home//com_akeeba/backup/*, and several others. 5. Specific File Types Across Home Directories: Files with extensions like .rar, .iso, .xen, .7z, .tar, .mkv, .avi, .pbo, .VOB, and large .zip files are targeted for removal. This also includes various log files and backups named in specific patterns. 6. Junk Mail Cleanup: Emails in folders like .Trash, .Junk, .Spam, etc., older than 30 days are deleted from user mail directories. Fair Usage Policy and Rights to Remove Files While the above list covers the majority of files removed during our cleanup process, it's important to note that this list is not exhaustive. Under our fair usage policies, we reserve the right to remove files that may not be explicitly mentioned in this list but are deemed necessary to ensure the optimal performance and security of our hosting services. This could include files that are unusually large, redundant, or pose a security risk. Conclusion Our internal auditing and cleanup process is a crucial aspect of our hosting service, designed to maintain server health and efficiency. While we strive to be transparent about the types of files we remove, our fair usage policies also play a vital role in guiding these decisions. As a user, understanding these practices helps in managing your hosted content more effectively and ensures a smoother hosting experience.

Last updated on Jun 12, 2025

Resolving 'npm: command not found'

When working with Node.js applications on your Brixly hosting account, you may encounter the 'npm: command not found' error. This typically indicates that the npm (Node Package Manager) is not in the system's PATH, or the correct version of Node.js is not being used. This article will guide you through resolving this error and running npm successfully. Step 1: Verify Node.js Version Before proceeding, ensure that you have selected the correct version of Node.js for your application in the NodeJS interface of cPanel or DirectAdmin. The version of npm you use should match the version of Node.js set up for your application. Step 2: Using the Full Path to npm To run npm commands without encountering the 'command not found' error, you should specify the full path to the npm executable. The typical path for npm on Brixly hosting is as follows: /opt/alt/alt-nodejs18/root/bin/npm Please note that "alt-nodejs18" in the path refers to Node.js version 18. If your application uses a different version, you will need to adjust the path accordingly. For example, if you are using Node.js version 12, the path would be: /opt/alt/alt-nodejs12/root/bin/npm Step 3: Running npm Commands With the full path specified, you can run any npm command as follows: /opt/alt/alt-nodejs18/root/bin/npm [command] Replace "[command]" with the npm command you wish to execute, such as "install" to install packages or "update" to update them. Conclusion: By using the full path to the npm executable, you can avoid the 'npm: command not found' error and manage your Node.js application's packages effectively. Remember to use the version of npm that corresponds with the Node.js version set in your hosting account's NodeJS interface.

Last updated on Jun 12, 2025

How many sites can I add to an individual cPanel account?

The number of sites you can add to an individual cPanel account is in most cases not limited by us, which means you have the freedom to host as many websites as you desire under a single cPanel account. However, it's important to consider the resource allocation for the account to ensure optimal performance. Each cPanel account on our Infinity or Infinity+ plans comes with substantial resources, including 2 CPU cores and 2GB RAM. Should you find that your websites require additional resources beyond what is available on the Infinity or Infinity+ plans, you have a couple of options. You can upgrade to one of our Premium Hosting plans, which are designed to accommodate sites with higher resource needs. Alternatively, if you are managing a reseller plan and need more resources for a specific account, you can take advantage of our 'Resource Boost+' option. This feature allows you to double the CPU and memory limits for any individual account at an additional monthly cost. For resellers who are managing multiple domains, there is also the flexibility to distribute domains across multiple cPanel accounts. This can help manage resource usage more effectively and ensure that each site has access to the resources it needs. In summary, while there is no set limit to the number of sites you can host on an individual cPanel account, the actual number of sites that can be hosted effectively will depend on their resource usage. Our 'Resource Boost+' option and the ability to upgrade to a Premium Hosting plan provide scalable solutions to support the growth of your websites. Additionally, resellers have the option to split domains into multiple cPanel accounts to optimize resource distribution. How Websites Use Resources, such as RAM and CPU When hosting websites, understanding how resources like RAM (Random Access Memory) and CPU (Central Processing Unit) are utilized is crucial for maintaining optimal performance and stability. Each website hosted on a server consumes a portion of these resources to function. **RAM Usage in Websites: ** RAM is used by websites to store data temporarily that is frequently accessed by the server's CPU. This can include content from your databases, session information, and the files that make up your website. When a visitor accesses your site, the server retrieves data from the RAM to quickly display your pages. The more visitors your site has at any given time, or the more complex your site is (such as an e-commerce site with a large inventory), the more RAM it will require. CPU Usage in Websites: The CPU performs the calculations and executes the commands needed to run the website's scripts and applications. Every time a page is loaded or a script is executed, the CPU is at work. Sites with heavy traffic or complex computational tasks (like dynamic content generation or data processing) will use more CPU power. Resource Limits and Website Performance: Each hosting account has allocated limits for RAM and CPU usage to ensure that all users on a shared server have fair access to the server's resources. For example, an Infinity+ account comes with 2 CPU cores and 2GB RAM. If a website uses 50% of its CPU limit, it's effectively using one full CPU core. Similarly, if it's using 50% of its RAM allocation, it's using 1GB of RAM. Examples of Resource Usage Impact: Consider a scenario where you have multiple websites under one hosting account. If one of your sites experiences a surge in traffic, it may start to consume more CPU and RAM. If the site's resource usage grows to the point where it's using the majority of the account's allocated resources, it could impact the performance of your other sites on the same account. They may load more slowly or, in extreme cases, become unresponsive. To prevent this, it's important to monitor your resource usage regularly. You can do this through the 'CPU and Concurrent Connection' screen in cPanel. If you consistently hit your resource limits, it may be time to consider upgrading your plan or adding a 'Resource Boost' to your account, which can double the available CPU and RAM for an individual account, ensuring that all your sites continue to perform well. Note, however, that the option to Boost+ an account is only available for our Reseller Hosting plans, whereas any standard hosting plan such as our Infinity, or Infinity+ plans would require an upgrade to one of our Premium Hosting plans.  By understanding and managing your resource usage, you can ensure that your websites remain fast, reliable, and capable of growing alongside your business.

Last updated on Jun 12, 2025

Understanding PHP Memory Limits in Shared Hosting Environments

Introduction: In shared hosting environments, such as those provided by Brixly, the 'Select PHP Version' screen often displays a default PHP memory_limit value that is lower than the maximum available. This article explains the rationale behind setting a lower default memory_limit, the implications of increasing it, and the limitations faced by resellers in adjusting this default value. Why a Lower Default PHP Memory Limit is Recommended:  The PHP memory_limit setting controls the maximum amount of memory that a script is allowed to allocate. It acts as a safeguard, preventing any single script from consuming all available server resources, which could lead to server instability and poor performance for other users on the same server. By default, Brixly sets a conservative memory_limit to ensure that all users on a shared server have access to the necessary resources and to maintain overall server health. This conservative limit is sufficient for the majority of websites and applications under typical usage scenarios. Scaling PHP Memory Limit:  It is recommended to increase the PHP memory_limit only when necessary, such as when a site is consistently hitting its memory limit, which could be indicated by errors in the site's logs or slow performance. Incremental adjustments allow for careful monitoring of the impact on server resources. For example, a WordPress site with a default memory_limit of 128M may function well under normal conditions. However, during a traffic surge or when running a resource-intensive plugin, the site may require an increase to 256M to handle the additional load without errors. Reseller Limitations and Shared Hosting Stability:  **Resellers do not have the capability to set the default PHP memory_limit across their hosting accounts. This limitation is in place to prevent the inadvertent allocation of excessive memory to individual accounts, which could compromise server performance and stability. In a shared hosting environment, if multiple users were to increase their memory_limit to the maximum of 1GB, the cumulative effect could exhaust server resources, leading to slow performance, increased load times, and even server crashes. This would negatively impact all users on the server. Whilst this is absolutely fine for sites that require it, setting it across the entire server can, and would have a negative impact to others, including your own clients.   Understanding PHP Threads and Memory Allocation in LVE / CloudLinux Environments: **PHP Threads and Execution: ** PHP threads refer to individual units of execution running within the web server. Each time a PHP script is executed, it runs in a single thread within the server's process. In a shared hosting environment, multiple PHP threads may be running simultaneously, each serving different requests from various users. **PHP Memory_Limit vs. LVE RAM Limit: ** The PHP memory_limit is a specific setting within the PHP configuration that dictates the maximum amount of memory a PHP script can consume during its execution. This limit is set to prevent a single PHP script from using too much memory, which could potentially affect the performance of other scripts running on the server. On the other hand, the RAM (Memory) limit included as part of CloudLinux's LVE settings is a broader restriction that applies to all processes running under a specific user account. This includes not just PHP scripts, but also other applications and processes initiated by the user. The LVE RAM limit ensures that each user on a shared server can only consume a certain amount of the server's total memory, thus preventing any single account from monopolizing the server's resources. For example, suppose a user's LVE RAM limit is set to 2GB. In that case, all processes combined under that user's account, including multiple PHP threads, databases, and scheduled tasks, must operate within this 2GB limit. However, each PHP script initiated by the user will also be subject to the PHP memory_limit, which might be set to a lower value, such as 128MB, to further control the memory usage at the script level. By having both PHP memory_limit and LVE RAM limits, Brixly ensures a balanced resource allocation that promotes stability and performance across all hosted accounts. It's important to note that while users can adjust the PHP memory_limit within their cPanel, the LVE RAM limits are predefined by the hosting plan and can only be increased by upgrading to a higher-tier plan. **Conclusion: **The default PHP memory_limit is set to a lower value to ensure a balanced distribution of resources in a shared hosting environment. While Brixly allows users to increase their memory_limit as needed, it is essential to do so judiciously and only when justified by the application's requirements. Resellers should be aware of the potential impact on server stability when modifying PHP settings and adhere to best practices to maintain optimal performance for all users. PHP memory_limit and LVE RAM limits work together to manage memory allocation efficiently in a shared hosting environment. PHP memory_limit controls the memory usage per script, while LVE RAM limits govern the total memory usage per user account, both playing crucial roles in maintaining server stability and performance.

Last updated on Jun 12, 2025

cpGuard - Understanding the Captcha Verification Screen

Introduction:  At Brixly, we prioritize the security of your websites. As part of our shared hosting environment, we have implemented cpGuard's Captcha verification feature to protect against automated threats and bot attacks. This article will explain why you might encounter Captcha prompts and the rationale behind this security measure. Why You See Captcha Prompts:  Captcha verification is a security feature that distinguishes human users from automated systems. On our shared hosting platform, cpGuard selectively activates Captcha protection for certain URLs that are more susceptible to bot traffic and abuse. The Verification Process:  When you or your site visitors navigate to a URL that is under Captcha protection, cpGuard may prompt for Captcha verification. This typically happens when the request comes from an IP address that cpGuard does not recognize as having a known protection status. The Purpose of Captcha Challenges:  The main goal of these Captcha challenges is to prevent unauthorized access and automated attacks, which can compromise the security and performance of your website. By verifying that the user is legitimate, we can maintain a safer environment for all our clients. Minimal User Impact:  We understand that Captcha prompts can be an inconvenience. Therefore, cpGuard is configured to minimize the frequency of these challenges. Once an IP address passes the Captcha verification, it will not be asked to verify again for several days. Centralized Management:  The management of Captcha verifications is handled by the cpGuard cloud, ensuring that the system is always up-to-date and effective against the latest threats. This centralized approach also helps in mitigating the impact of distributed bot attacks on our servers. Conclusion:  The Captcha verification process is a critical component of our security strategy on the shared hosting environment. It helps protect your website from automated threats without placing undue burden on legitimate users. We appreciate your understanding and cooperation in keeping our platform secure. If you have any questions or need further clarification on the Captcha verification process, please do not hesitate to reach out to our support team for assistance.

Last updated on Jun 12, 2025

Softaculous Backups - Why are they disabled?

At Brixly, we strive to provide our clients the best web hosting experience, including using reliable and efficient backup solutions. While Softaculous is a popular software auto-installer that offers a native backup functionality, we have decided not to provide this feature for various reasons. In this knowledge base article, we will explain our decision and discuss the alternative backup solution we offer. Reasons for Disabling Softaculous Backup Functionality 1. Non-incremental backups: Softaculous creates full backups each time it runs a backup process. This means every backup includes all files and databases, even if only a small portion has changed since the previous backup. This approach leads to increased storage consumption and resource overhead. 2. Excessive storage consumption: Softaculous backups are non-incremental and consume a considerable amount of storage space within the hosting accounts. This excessive use of storage can result in a breach of our fair usage policies, which are in place to ensure all clients enjoy a fair share of resources. 3. High resource overhead: Generating non-incremental backups requires significant RAM and CPU resources, affecting overall server performance. As Softaculous creates full backups, the process can strain the server and potentially impact other clients hosted on the same server. 4. Lack of control over schedules and timeframes: With Softaculous backups, we have limited control over the scheduling and timing of backup processes. This can lead to backups being created at inconvenient times, causing additional load on the server during peak hours. Introducing JetBackup: Our Preferred Backup Solution To provide our clients with a reliable and efficient backup solution, we offer JetBackup as part of our hosting services. JetBackup includes free daily backups and comes with several advantages over the Softaculous backup functionality: 1. Incremental backups: JetBackup creates incremental backups, which means only the changes made since the last backup are stored. This approach significantly reduces storage consumption and resource overhead. 2. Efficient resource usage: JetBackup is designed to minimize the impact on server resources, ensuring that RAM and CPU usage remain within acceptable limits during the backup process. 3. Customizable scheduling: JetBackup allows us to schedule backups during off-peak hours, reducing the load on the server and ensuring optimal performance for all clients. 4. Easy restoration: JetBackup offers an easy-to-use interface that enables clients to quickly restore their data from backups with just a few clicks. At Brixly, we prioritize the needs of our clients, and our decision to disable Softaculous backup functionality is based on our commitment to providing the best possible hosting experience. By offering JetBackup as an alternative, we ensure our clients enjoy a reliable, efficient, and easy-to-use backup solution that minimizes the impact on server resources and storage consumption. If you have any questions or need assistance with JetBackup, please don't hesitate to contact our support team.

Last updated on Jun 12, 2025

How to Clone a WordPress website between cPanel accounts using WP Toolkit

Before we can clone a WordPress site we need to make sure that the site we want to clone exists in the WP Toolkit and that the destination exists. Add site to WP Toolkit Navigate to the cPanel account of the site you want to clone and head to WP Toolkit. You will need to select 'Scan' to import any current set-up sites to the WP Toolkit: 9cbbdc5b657d575a43a61e80f945618404b5308f16032e897485e1ff08ecdd970e091d9500d79fec?t=adcf1d30e9a9741a71bb0cad0f7ddbc5 Once completed the WordPress site will show in the WP Toolkit dashboard: 06581617631467335db74072ec0a05410e1b1fa43da1c7595cd563c10629870ba8c7083c14029414?t=5d0ca0f7c69d01fca6ba3f2d9952fac2 Create cPanel account or add domain Either create a new cPanel account or add an addon/subdomain to an existing account to import the site. If you're using one already created, it is important no site already exists on the domain you wish to import this to. Import the site Now that the site is in the WordPress Toolkit and we have a destination created we can begin the import. In WHM navigate to the 'WP Toolkit' plugin, the easiest way is through the search bar on the left-hand side: d12417ba777cedf604709086277c420831bf73f5ba0621695cddb902ef35e657fcaff173ece467d0?t=fdcdde0ca72dc7749885919561123ca4  This will display a list of all WordPress sites owned by your sub-users, find the site you want to clone from the list (the search bar at the top right comes in very handy!) Now you have the site click the 'Clone' button to migrate this to another domain. c382a7f6040dd61cc8d3fe688404922a8f3698998e2ad09f89476439e6f5aff1d70bc520ea660888?t=6f814fdb1357a2d248552c97bb09519e  Select 'Use existing domain' and choose the domain you wish to transfer the site over to: We would recommend leaving the path blank (or it will install in a sub-directory) and the default database name is fine.  Once ready, click Start to begin cloning the site.  There will be a progress bar at the bottom of this window detailing how the transfer is going:0a08a6a74adbc93b91037f96ca3e3158914f34a854850bdaa39f7610a938fc48aa4b335567f5bec1?t=b3f045a7fd4f4af9302f3a778bc65e63  You can close out of this window if you wish as the transfer will continue in the background. This will report once it's successfully cloned:b8a4a1d4b97c23d3b2c7246f7a0ec9913e9538e7fc74c0e2040b007f9f32de17b69338ac43c97c73?t=ba06df95426ec27a06a5f1a64791d61b If you closed the window and wanted to check the process, there's a small pop-up on the bottom right-hand corner that will report the process of the transfer:66215cf6454114dd84d3f04f760f4d44018cfc117035e2073163db1b275c635e6b00cf29fd78d40a?t=006c6a8826289666810cf5ba52ff3c5d  Once it's completed, the site is ready to go from the new domain name.

Last updated on Jun 12, 2025

Enable Object Caching with Redis using LSCache

Please note, that Redis is only available on our cPanel plans The first thing to do is to navigate to Redis in cPanel: f3361001d054710f8a981ceab2176a87fb9b18ab901deecd398e8ef06a2d40327b843abc8d41332c?t=7a9083a03bc7baa8bd63596f9a4b9197 Once within the Redis tool, enable it for your account:Please note that you must use the socket local to your account, which we create on this screen. You cannot use the socket for another account (or the one we show here!). Once enabled, copy the Redis socket path displayed in your cPanel account, as we will need this later! You can always come back to the Redis plugin screen within your cPanel account to see the path to your own Redis socket. Please note that you must use the socket local to your account, which we create on this screen. You cannot use the socket for another account (or the one we show here!). Now we need to enable the Redis extension; this is enabled under cPanel -> Select PHP Version -> Extensions -> Redis. b90d43596909da08e36709a186a4d99f9578bdc66c286b49382c58e3129ce2e21a199104b5668f0a?t=e7642b817c8d3451f2dde2bec551188f Once enabled, we can log in to WordPress and access the LiteSpeed Cache. Under **Cache -> Object, **we can find the settings for enabling Redis: 5b2782ecae834612c21ec6589110bd7a3151ff56176107251aa44d231a9bdda53748f7d1e7e87c10?t=edd162a0885e8eae65954648622bc99d The settings we need to enable here are: - Change Object Cache from Off to On - Switch Method to Redis - Set the Host to be the Redis socket path mentioned in the Redis plugin - Change port to 0 Once done, hit save, and the Object Cache should be ready to go!

Last updated on Jun 12, 2025

How to Create Custom Error Pages in cPanel

Error pages play a crucial role in informing visitors about issues when they try to access your site. Each problem has its own status code. For instance, a 404 error appears when a visitor enters a non-existent URL, and a 401 error shows up for an unauthorized user trying to access a restricted area. While basic error pages are automatically provided by the web server (Apache), you can create custom error pages for any valid HTTP status code starting with 4 or 5 using cPanel. Customizing an Error Page Follow these steps to create a custom error page: 1. If your account manages more than one domain, select the domain for which you want to edit an error page from the 'Managing' menu. 2. Click on the error status code for which you want to edit its error page. If you don't see the desired error status code in the list, click on the 'Show All HTTP Error Status Codes' tab, then select the desired error status code. 3. Enter a message in the text box. This message will be displayed on the error page. 4. To display visitor-specific information on the error page, click the appropriate buttons for the information you want to display. 5. You can enter additional HTML code to further customize your error pages. 6. Click 'Save' to apply the changes. By following these steps, you can create custom error pages that provide more helpful information to your visitors when they encounter an issue. This can improve the user experience and keep visitors on your site even when they encounter a problem.

Last updated on Jun 12, 2025

Installing a Free SSL Certificate via cPanel

Installing an SSL certificate in cPanel is easy! Best of all, it's free with Brixly! Important: Installing a certificate does will not force your browsers to visit the site via https:// Automatic SSL Certificates with AutoSSL The process of installing SSL’s has been simplified, in most cases requiring no interaction on your part. The purpose of AutoSSL is that we will as a provider automatically check for SSL’s which are expiring, and will automatically replace those SSL’s, ensuring your sites remain secure. If you are unable to wait for the SSL process to complete, you are also able to install an SSL certificate manually with just a single click... cPanel -> SSL / TLS Status -> Run AutoSSL Please note: SSL Certificates installed through AutoSSL are powered by Sectigo, which provides you with full 256-bit encryption. Sectigo is suitable for almost all sites domains, however, Sectigo does have certain restrictions and limitations in the types of SSL certificates that can be installed (see below for more information, and for more information on installing a certificate provided by LetsEncrypt as an alternative). Free SSL Certificates are issued for 90 days, however, they are automatically renewed a few days prior to expiry, and take just a few minutes in most cases to be issued (however, in some cases it's possible that SSL issuance may take longer). As such, free SSL certificates provided by Brixly essentially 'do not expire', and are free for the lifetime of the account. Unfortunately, citizens from the countries listed below cannot obtain any Sectigo SSL certificates due to US Export restriction laws: - Afghanistan - Cuba - Eritrea - Guinea - Iran - Liberia - North Korea - North Cyprus - Sudan - Sierra Leone - South Sudan - Syria - Zimbabwe However, if you do require SSL coverage for these domains / TLD's, then you are able to install an SSL certificate via LetsEncrypt, which does not have the same exclusions. LetsEncrypt Certificates As outlined above, Sectigo SSL certificates offer optimal coverage, completely automatically and free of charge. In addition, they also do not 'rate limit' requests, making it an ideal solution for us as shared hosting providers. LetsEncrypt however, also offers you additional functionality, such as the ability to support wildcard coverage, and also supports redirection tracing which can be simpler for some sites hosted behind Cloudflare, or other CDNs / proxy services. Also, Sectigo does restrict certain regions from issuance entirely, as outlined above. If your use-case/scenario requires a LetsEncrypt SSL certificate, then we now provide you the ability to install a free LetsEncrypt SSL certificate from within cPanel... cPanel -> Let's Encrypt™ SSLThe interface is split into two sections. The first section will list all of your domains that have “Let’s Encrypt™” certificates issued, their expiry, and options to remove, reinstall and view them: user-guide-current.png The second section will list all of the domains configured in your account that are eligible to have a certificate issued. Please note, redirected domains are unable to have a certificate issued. user-guide-issue.png Prerequisites There are two important prerequisites to be met in order for a certificate to be able to issue: - The domain name(s) you want to be signed must be pointing to this cPanel server already - The Let’s Encrypt™ CA must be able to visit http://your-domain/.well-known/acme-challenge/xxx successfully. These directories/files will be created automatically, but you should take care that you do not have any .htaccess rules that prevent access. Most users will fulfill these requirements automatically. Issuing Process First, click the + Issue button to the right of the domain you wish to issue a certificate for. Please note, any you will be able to select any extra domains to include on the certificate in the next screen. user-guide-confirm.png Ensure that all of the domains you wish to include in this certificate are selected as included and click ‘Issue’. The process may take anywhere from 10 to 45 seconds, so do not navigate away from the page. At completion, the keys and certificates should be installed on the server, with a success message: user-guide-installed.png Certificate renewal is automatic in the background. Your certificate will be attempted to be renewed every day from the point it is 30 days from expiring. The prerequisites listed above for issuing must still be met during the renewal attempts, or the attempts will fail. Compare LetsEncrypt vs Sectigo Both solutions in their own right, are fantastic. However, each has unique benefits over the other, which is why we now offer both solutions. As outlined above, Sectigo SSL certificates offer optimal coverage, completely automatically and free of charge. In addition, they also do not 'rate limit' requests, making it an ideal solution for us as shared hosting providers. LetsEncrypt however, also offers you additional functionality, such as the ability to support wildcard coverage, and also supports redirection tracing. e56c3a0445db0ca1eadab9123cd075941590af32a69d1e4184ae8153bb34368c22f1d57792479826?t=76b342408b0799d4eff2e2e31d06f32e

Last updated on Jun 12, 2025

Monitoring Disk Usage with cPanel

Keeping track of your disk usage is crucial for maintaining your website's performance and ensuring you don't exceed your hosting plan's storage limit. This guide will show you how to check disk usage using cPanel. Understanding Disk Usage The Disk Usage interface in cPanel provides a summary of your disk space usage. It displays information about: - Files contained in your home directory. - Files existing in hidden subdirectories. - Mailing lists in Mailman. - Files not contained in your home directory (see the 'Other Usage' bar). The bars in the graph represent disk usage figures relative to the largest directory. Accessing File Manager You can click on any of the listed directories to open the appropriate subdirectory in the File Manager interface (cPanel >> Home >> Files >> File Manager). Please note that the File Manager interface does not display disk usage information for individual files contained in your home directory. Understanding Discrepancies There may be some discrepancies between the data displayed in the File Manager interface and the Disk Usage interface: - Most files occupy slightly more disk space than their actual size. For example, a 300-byte file may occupy 4 KB of actual disk space. - The disk space usage information does not indicate how much space the directory itself uses. Typically, directories themselves occupy a negligible amount of disk space. - The system includes MySQL® database size and PostgreSQL® database size in an account’s disk usage calculation. However, the system does not enforce the account’s disk space quota limit if a database’s size causes the account to exceed its limit. - The figures that the Disk Usage interface displays may not reflect recent changes in your account’s disk space. Checking Disk Usage To check your disk usage, log into your cPanel account and navigate to the Disk Usage section. Here, you'll see a graphical representation of your disk usage, broken down by directory. This allows you to see at a glance which directories are using the most space. By regularly monitoring your disk usage, you can ensure that you're making the most of your available storage and maintaining optimal website performance.

Last updated on Jun 12, 2025

Managing Cron Jobs in cPanel

Overview Cron jobs are automated tasks scheduled to run at predefined times or intervals. They are typically executed by the system using a script file, and they can perform a series of simple tasks. It's important to exercise caution when scheduling cron jobs. Running them too frequently can hinder the usage of your LVE limits, and may lead to a breach of our fair usage policies.  Add a cron email The Cron Email feature allows you to receive notifications via email when your cron jobs run. To set up email notifications, follow these steps: 1. Enter the email address where you want to receive the notifications in the Email text box. 2. Click on the "Update Email" button to save the email address. Disable email notifications To disable email notifications for all cron jobs, simply remove the email address. If you want to disable email notifications for a specific cron job, follow these steps: 1. Locate the cron job for which you want to disable email notifications. 2. Find the relevant line in the cron job configuration. 3. Add the following string to that line: [code] >/dev/null 2>&1[/code] 4. Save your changes. Add a cron job To create a new cron job, follow these steps: 1. Choose the desired interval for the cron job by selecting options from the available menus or by manually entering values in the text boxes. - Common Settings: This menu provides commonly used intervals and preconfigures the Minute, Hour, Day, Month, and Weekday fields. If you find the wildcard characters (*) and intervals confusing, this menu can help you understand how to configure the other fields. - **Minute: **Select the number of minutes between each time the cron job runs or specify the minute of each hour when you want it to run. - **Hour: **Select the number of hours between each time the cron job runs or specify the hour of each day when you want it to run. - **Day: **Select the number of days between each time the cron job runs or specify the day of the month when you want it to run. - **Month: **Select the number of months between each time the cron job runs or specify the month of the year when you want it to run. - **Weekday: **Select the days of the week when you want the cron job to run. 1. In the Command text box, enter the command that you want the system to execute. Be sure to specify the absolute path to the command. For example, if you want to run the file public_html/index.php in your home directory, enter the following command: [code] /home/username/public_html/index.php[/code]Note: It is crucial to provide settings for all the required fields, including Minute, Hour, Day, Month, Weekday, and Command. 2. Exercise extreme caution when using the rm command in a cron job. Without the correct options, you risk deleting important data from your home directory. 3. Click the "Add New Cron Job" button to save the cron job. View existing cron jobs The "Current Cron Jobs" table displays all your existing cron jobs. Edit a cron job To make changes to a cron job, follow these steps: 1. Locate the cron job you want to edit and click on the "Edit" button. 2. Modify the settings as desired. 3. Click the "Edit Line" button to save your changes. Delete a cron job To remove a cron job, follow these steps: 1. Click on the "Delete" button next to the cron job you want to delete. 2. Confirm the deletion by clicking "Delete."

Last updated on Jun 12, 2025

How do I convert a cPanel account to an Addon Domain?

If you’re a reseller customer and would like to convert a full-fledged cPanel account to an addon domain, please follow these steps: **Important: There are no native tools that allow us to convert a full cPanel account to an Addon Domain. The work involved in this can in some cases become complex, and therefore is not something we provide as part of our support remit. ** 1. Back up the entire account you wish to convert (using cPanel’s Full Backup feature) and save the backup file locally on your computer. You can utilize cPanel’s partial backup feature to backup files, databases, email filters, etc.  2. If you have email accounts added to this account, make sure to configure them locally in your email application (Outlook, Thunderbird, Apple Mail). 3. Remove the cPanel account via WHM > Account Functions section > Terminate accounts option. 4. Log in to the destination account cPanel control panel, and create an addon domain 5. Create the necessary databases, and then import database backups (MySQL dumps) from the old account. 6. Create email accounts for the new addon domain. 7. Import/migrate email messages you’ve backed up in Step 2 earlier to new email accounts.  8. Restore files and folders you saved in Step 1. Upload the backup archive to the server via FTP or through the File Manager tool from cPanel and then restore it: right-click on the uploaded archive and then select the extract button. 9. Modify the configuration file of your website and populate it with new MySQL credentials, and test the website.

Last updated on Jun 12, 2025

Publishing DMARC Records on Your cPanel Domain

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is an email authentication protocol that uses SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) to detect and prevent email spoofing. This guide will walk you through the process of publishing DMARC records on your cPanel domain. Understanding DMARC DMARC helps protect your domain from phishing attacks and increases the deliverability of your emails. It allows the email receiver to check if the email aligns with what the receiver knows about the sender. If not, DMARC includes guidance on how to handle the "non-aligned" messages. Publishing DMARC Records Follow these steps to publish DMARC records on your cPanel domain: 1. Log in to cPanel: Access your cPanel dashboard by signing in to your cPanel portal. 2. Locate your domain: Navigate to the "Domains" section and click on 'DNS Zone Editor'. Then, click on the 'Manage' button for the domain you wish to configure. 3. Create the record entry: You'll need to create a TXT record with the following details: - Type: TXT - Name/Host: _dmarc.yourdomain.com (replace 'yourdomain.com' with your actual domain name) - TXT Value/Data: This will be the DMARC record value created using your account’s setup wizard or PowerToolbox. - TTL: 1 hour or keep the default value - Alternatively, you can create a DMARC record for your domain for free using the 'powerdmarc' generator. Once you've added the details, click on the 'Add Record' button. 1. Check the published DMARC record: You can verify the published DMARC record via PowerToolbox. Please note that you should replace 'yourdomain.com' with your actual domain name, and your RUA and RUF email addresses with valid, active email addresses. By following these steps, you can publish DMARC records on your cPanel domain, enhancing the security and deliverability of your emails.

Last updated on Jun 12, 2025

Getting Started with cPanel: A Comprehensive Guide

Introduction Welcome to the comprehensive guide on getting started with cPanel. This guide is designed to ensure a smooth experience for you while accessing and using cPanel. Whether you are a reseller or an individual user, this guide will help you understand the basics of cPanel and how to navigate through its extensive features. Accessing cPanel As a reseller, you will receive a single username and password, which will grant you access to both WHM and cPanel. These are accessed through different ports. To log in to cPanel, you can use the server hostname provided in your welcome email, followed by the :2083 port. For example: https://alfa.cloudns.io:2083 The hostname is unbranded to avoid mentioning the Brixly name or brand. The address 'alfa.cloudns.io' is the hostname of the server, while :2083 is the port used to access the cPanel interface. Once you've pointed your domain to the server, you can log in using your own domain like this: https://yourdomain.com:2083 The :2083 specifies the port of the cPanel service. You'll be redirected to the cPanel login interface when you access this specific port. Enter your username and password from your welcome email to log in. Logging in via WHM (WebHost Manager) (Resellers Only) To log in to your cPanel account via WHM, navigate to 'List Accounts' in WHM and select the orange 'cP' logo listed next to the domain. This method doesn't require credentials, making it perfect for logging into clients' cPanel accounts. To log in to WHM from cPanel, access cPanel first, and then click the 'WHM' icon. cPanel Overview The cPanel interface is extensive, with many functions and features. Once logged in, you will see the cPanel home screen, which provides an overview of your hosting account, including disk space usage, bandwidth usage, email accounts, databases, and more. File Manager The File Manager is a powerful tool that allows you to manage your website files directly from the cPanel interface. You can upload, download, edit, delete, and organize your files and folders with ease. You can also create and extract archives, set file permissions, and more. Email Accounts cPanel provides a robust email management system that allows you to create and manage email accounts for your domain. You can create email addresses, forwarders, autoresponders, set mailbox quotas, and more. Databases With cPanel, you can create and manage databases for your website. You can use MySQL or PostgreSQL, create and manage users, import and export data, and more. Domains cPanel also allows you to manage your domain names, including creating subdomains, addon domains, and parked domains. You can also manage domain redirects and DNS records. Backups Backups are an essential aspect of any website management, and at Brixly, we use JetBackup to ensure your data is secure. JetBackup provides a comprehensive backup solution that ensures the safety and security of your data, giving you peace of mind and allowing you to focus on growing your business. Softaculous Softaculous is a popular script installer that allows you to install hundreds of applications, including WordPress, Joomla, Drupal, and more, with just a few clicks. You can also update and remove applications with ease. Security At Brixly, we take security seriously. That's why we've implemented Imunify360, an all-in-one security solution that protects our servers against malware, viruses, andother malicious attacks. Imunify360 is designed to detect and prevent attacks in real-time, giving you peace of mind that your website and data are safe. Conclusion cPanel is a powerful and user-friendly control panel that allows you to manage your website and hosting account with ease. With its many features and tools, you can easily create and manage email accounts, databases, domain names, backups, and more. Explore the cPanel interface to get familiar with its options and features, and don't hesitate to contact our support team if you have any questions or need assistance.

Last updated on Jun 12, 2025

Setting 'date.timezone' Value through PHP Selector in cPanel

Having issues with applying the 'date.timezone' value through the PHP Selector in cPanel? Don't worry, we've got you covered. Follow the steps below to resolve this issue: Step 1: Viewing the Current 'date.timezone' Value First, you need to check the current 'date.timezone' value. To do this, you can use a phpinfo() file. Here's how: 1. Log into your cPanel account. 2. Navigate to the 'File Manager'. 3. In the public_html directory, create a new file and name it 'phpinfo.php'. 4. Edit this file and add the following line of code:  5. Save the changes and close the file. 6. Now, open a new browser tab and navigate to 'yourdomain.com/phpinfo.php'. Replace 'yourdomain.com' with your actual domain name. 7. On this page, you'll see a lot of information about your PHP configuration. Look for the 'date.timezone' value. Step 2: Changing the 'date.timezone' Value If the 'date.timezone' value is empty or incorrect, you can easily change it through the PHP Selector. Here's how: 1. Go back to your cPanel main dashboard. 2. Navigate to 'Software' and then click on 'Select PHP Version'. 3. Click on 'Switch to PHP Options'. 4. Here, you'll see a list of various PHP options. Find 'date.timezone' and click on its current value. 5. In the text box, enter your desired timezone in double quotes. For example, if you want to set it to London time, you would enter: "Europe/London".  6. Click on 'Apply', and then 'Save' to save your changes. The double quotes are important because the slash (/) in the timezone value can break the contents and pass it through incorrectly. Using double quotes fixes this issue. And that's it! You have successfully set the 'date.timezone' value through the PHP Selector in cPanel.

Last updated on Jun 12, 2025

Redis Limits - PHP Fatal error: Uncaught RedisException: OOM command not allowed when used memory > 'maxmemory'

If you're a web hosting customer experiencing a PHP Fatal error message that reads, "Uncaught RedisException: OOM command not allowed when used memory > 'maxmemory'", you're not alone. This error can be a bit confusing, especially when you're not familiar with the underlying technologies. In this article, we'll break down what this error means and why it occurs in the context of Brixly's hosting services. The PHP Fatal Error Explained The PHP Fatal error you're encountering is related to Redis, a popular in-memory data store that provides lightning-fast data retrieval. The error message, "OOM command not allowed when used memory > 'maxmemory'", translates to "Out Of Memory." In simpler terms, it means that the Redis instance running on your hosting account has exceeded its allocated memory limit. Redis and Its Importance Redis is a critical component of modern web applications and websites. It's used for caching data, session management, and more, significantly improving the performance and responsiveness of your website. Redis stores data in RAM, which is incredibly fast but also volatile.  LVE Limits vs. Redis Memory Limits At Brixly, we provide LVE (Lightweight Virtual Environment) limits to each hosting account, which include memory limits. However, it's essential to understand that Redis instances have their own memory limits, defined at the server level. The default memory limit for a Redis instance on our hosting plans is 32MB. The reason for this separation between LVE memory limits and Redis memory limits is the nature of Redis itself. Redis is designed to be highly performant, and it stores data in RAM for faster access. This makes it more persistent than other processes like PHP, which can be easily restarted without significant consequences. Redis, on the other hand, could lose important cached data if it runs out of memory. Why Redis Memory Limits Can't Be Increased on Request You may wonder why we can't increase the Redis memory limit on request. While it might seem like a straightforward solution, it's essential to balance performance and stability. Increasing the Redis memory limit can lead to increased memory usage across the server, potentially affecting the overall stability of all hosted accounts. This is especially important on shared hosting environments where multiple users share the same resources. Therefore, we've set the Redis memory limits conservatively to ensure optimal performance and stability for all our customers. Redis Memory Limits on Premium Hosting Plans If you require more memory for your Redis instance, we offer higher memory limits on our Premium Hosting plans: - Premium Business: 256MB - Premium Enterprise: 512MB - Premium Agency: 1024MB - Premium Reseller: 512MB per cPanel user These higher memory limits allow you to allocate more memory to your Redis instance for increased caching and performance. If a larger Redis instance is required for your website than the above, then the next option would be to consider one of our managed Cloud Servers, or a Dedicated Server for the site.  Conclusion In summary, the PHP Fatal error "OOM command not allowed when used memory > 'maxmemory'" indicates that your Redis instance has exceeded its memory limit. While LVE limits apply to your hosting account, Redis has its own memory limits for stability and performance reasons. These limits are set conservatively but can be increased on our Premium Hosting plans to accommodate your specific needs. If you encounter this error and believe you need a higher Redis memory limit, consider upgrading to one of our Premium Hosting plans or reaching out to our support team for further assistance. We're here to help you optimize your hosting environment for the best possible performance and reliability.

Last updated on Jun 12, 2025

How to create and manage Teams on cPanel

Introduction The 'Manage Team' feature in cPanel allows account owners to create and manage team users, providing them with the ability to assist in managing domains, email accounts, and databases. This feature is especially useful for businesses or individuals who require multiple users to have access to the cPanel account, while still maintaining control and oversight. Prerequisites Before you can use the 'Manage Team' feature, ensure that it is enabled on your account. If it is not visible in your cPanel interface, please contact Brixly support or your hosting provider to enable this for you. Understanding the Manage Team Interface The 'Manage Team' interface in cPanel consists of several key areas: 1. Manage Team Account Quota Status: This section displays the total number of team users you can create, as well as the current number of created team users. A team comprises a maximum of seven team users and the team owner. 2. Create a Team User Interface: This is where you can create a new team user. 3. List of Team Users: Here, you will find a table listing all the team users associated with your account. 4. View Audit Log Interface: This section allows team owners to track team user actions that use the API. Creating a Team User To create a team user: 1. Click on 'Create Team User'. 2. Fill in the necessary information, including basic information, security information, and roles configuration for the account. For a more detailed guide, you can refer to cPanel's Create a Team User documentation. Managing Team Users You can view and manage all team users associated with your account in the 'List of Team Users' section. Here, you can edit user details, suspend or delete team user accounts. Audit Log The Audit Log is a crucial feature for tracking the actions of team users.  For more information, you can refer to cPanel's Audit Log documentation. Conclusion The 'Manage Team' feature in cPanel is a powerful tool for account owners who require multiple users to have access to their cPanel account. By following this guide, you should be able to set up and manage team users effectively, ensuring a smoother and more controlled management experience.

Last updated on Jun 12, 2025

Understanding the Disabled 'Reset Password' Functionality in cPanel Webmail

Introduction:  At Brixly, we prioritize the security and integrity of our clients' accounts and data. We understand the importance of convenient features such as resetting passwords via a secondary email address in Webmail. However, due to security concerns, this functionality has been disabled. This article explains the reasoning behind this decision and our commitment to your account's safety. Background:  We identified a security threat commonly known as 'AnonymousFox,' which exploited vulnerabilities in outdated or compromised WordPress plugins. This exploit allowed attackers to access the file system of the affected accounts. It's important to note that this was not a server-level compromise but was isolated to individual accounts. Our use of CageFS technology ensures that such an exploit cannot spread across accounts. Why is 'Reset Password' via Secondary Email Disabled?  When a user attempts to reset their email password through cPanel, the new password is sent to their email address. If this email account is hosted on the same server, there's a risk that the new password could be intercepted from the mail file by an attacker who has gained unauthorized access through an exploit like 'AnonymousFox.' To mitigate this risk and protect our clients, we have disabled the ability to reset email passwords via secondary email addresses in Webmail. This decision was made to prevent attackers from potentially gaining password-authenticated access to your accounts. Our Commitment to Security:  We understand that this may cause some inconvenience; however, our clients' security is our top priority. We continuously monitor and update our security protocols to ensure the highest level of protection for your data. Alternative Password Reset Methods:  If you need to reset your email password, we recommend doing so through the cPanel interface or by contacting our support team for assistance. We are always here to help you maintain secure and uninterrupted access to your services. Conclusion:  Brixly is dedicated to providing a secure hosting environment. Disabling the 'Reset Password' functionality via secondary email is a precautionary measure to safeguard your accounts against potential exploits. We appreciate your understanding and cooperation in maintaining the security of our hosting platform. For any questions or concerns, please reach out to our support team, who are available to assist you at any time.

Last updated on Jun 12, 2025

Understanding CloudLinux and LVE Limits: Enhancing Server Stability and Performance

In shared hosting environments, it's crucial to maintain server stability and performance. One of the most effective ways to achieve this is through the use of CloudLinux and Lightweight Virtual Environment (LVE) limits. This guide will provide an in-depth understanding of these technologies and how they contribute to a more stable and secure hosting environment. What is CloudLinux? CloudLinux is an operating system designed specifically for shared hosting providers. It improves server stability by isolating each client in a secure environment known as a Lightweight Virtual Environment (LVE). This isolation prevents a single account from monopolizing server resources and slowing down other accounts. For instance, if one customer is using an unfair amount of resources due to a poorly written script or a DDoS attack, the server could become slow or even go down, affecting all other customers on the server. With CloudLinux, the impact is isolated to the offending tenant only, while all other sites remain unaffected. Understanding LVE Limits LVE limits are restrictions on the number of resources that can be consumed by a single user. These limits improve the general stability and performance of the server. When an account reaches its resource limits, it will temporarily stop working until its resource usage returns to normal. Meanwhile, the other tenants on the server will continue to run normally. For example, if an account is hitting CPU or IO limits, the site will begin to slow down. However, if it's hitting 'Entry Processes' (EP) or 'Memory' (PMEM) limits, the site will display a '503 Error'. LVE 'Faults' and 'Snapshots' When an account hits the LVE limits for a particular resource, we record something called a 'fault', along with a 'snapshot'. A fault is a recording of the resource type being hit, along with the time, date, and username. A snapshot is a list of processes running at the time of the LVE fault, allowing users to investigate why those limits are being hit. CageFS: Enhancing Security CloudLinux includes CageFS, a virtualized per-user file system that isolates each customer’s files and running processes. This prevents users from seeing each other and potentially exploiting sensitive information. CageFS offers complete isolation and prevents a large number of attacks, such as privilege escalation and information disclosure attacks. Monitoring Resource Usage You can monitor your account's resource usage at any time. Simply log into cPanel and look at the resource usage stats on the right-hand side. Resource usage is calculated relative to the limits applied to your account only, and not the entire server. For example, if your account allows 2 CPU Cores and 2048 MB RAM, a CPU usage of 50% would mean that your account is currently maxing out 1 CPU Core. Memory usage of 50% would mean that your account is using 1024 MB RAM. You can also check the 'CPU and Concurrent Connections' screen in cPanel for a more detailed overview. By understanding and effectively managing CloudLinux and LVE limits, you can ensure a more stable and secure hosting environment for your website.

Last updated on Jun 12, 2025

Entry Processes / EP – what is an entry process?

An entry process, directly translated means a 'process which enters LVE', or, a process which enters / runs inside your LVE container / account.  Entry processes, as a combined term, equates to the processes which run within the LVE / user account simultaneously.  Your 'Entry Process' limit essentially means that you can run that quantity of simultaneous processes within the account at any given time. Whats important to point out however, is that an Entry Process can take a fraction of a second to complete (or the opposite, where a process hangs for some time). By example, think of a PHP script, which typically take a split second to complete or process. From that point onwards, the process dies, and your 'available' LVE allocation for Entry Processes increases with an additional spare slot. However, if you have a process which runs for a longer period (such as, a longer running PHP process or script, or a cron which takes some time to complete), it will continue to use that Entry Process slot.  As such, its a common misconception that 'Entry Processes' equates to the number of simultaneous visitors, however this isn't the case. The reason for this, as explained above is that a single process may run for a split second, which means you can essentially run more than the EP value as simultaneous visitors (assuming that the Entry Process dies, and the page loads in a reasonable time). If your account exceeds its LVE limits for 'Entry Processes', those additional resources which run 'above' the limit count, will be killed by a kernel process called 'SIGKILL'. The result of this, is a 503 'resource limit reached' error. Our hosting plans come with varying levels of Entry Processes (albeit, slightly higher than many providers). If you are hitting your EP limits, it may be worth checking the  'Resource Usage' section of your control panel or reach out to our support team for assistance.

Last updated on Jun 12, 2025

Installing a WordPress Plugin via FTP

While WordPress's built-in plugin installer is convenient, some situations may require you to install a plugin manually via FTP. This could be the case for premium, large, or custom WordPress plugins. This guide will walk you through the process of installing a WordPress plugin using FTP. Connecting to Your Hosting via FTP First, you'll need to connect to your hosting account using an FTP client. There are many FTP clients available, but some popular ones include FileZilla, Cyberduck, and WinSCP. You'll need your FTP credentials, which are usually provided by your hosting provider. Navigating to Your WordPress Directory Once you've connected to your hosting account via FTP, navigate to the directory containing your WordPress site. This is typically the public_html directory, but it may vary depending on your hosting setup. Uploading the Plugin Next, you'll need to upload your plugin to the /wp-content/plugins directory within your WordPress directory. To do this: 1. Locate the plugin file on your local machine. This file should be a .zip file. 2. Upload the .zip file to the /wp-content/plugins directory. Unzipping the Plugin If your plugin file is zipped, you'll need to unzip it. This can be done via the cPanel File Manager: 1. Log in to your cPanel account. 2. Navigate to the File Manager. 3. Locate the .zip file you just uploaded. 4. Right-click on the .zip file and select 'Extract' to decompress the files. Activating the Plugin After the plugin has been uploaded and unzipped, it should now be visible on the Plugins page within your WordPress Dashboard. To activate the plugin: 1. Log in to your WordPress Dashboard. 2. Navigate to Plugins > Installed Plugins. 3. Locate the plugin you just uploaded. 4. Click 'Activate' to activate the plugin. By following these steps, you can manually install a WordPress plugin via FTP. This method can be particularly useful for installing large plugins that exceed the upload limit of the WordPress Dashboard. If you encounter any issues during this process, our support team is here to help.

Last updated on Jun 12, 2025

Resolving the "Unable to Create Directory" Error in WordPress

In WordPress, the "Unable to create directory" error is a common issue that can occur when you're trying to upload images, update themes or plugins, or install WordPress. This error is typically caused by incorrect file permissions, an incorrect file path, or a misconfigured hosting environment. This guide will walk you through the steps to resolve this error. Check and Correct File Permissions Incorrect file permissions can prevent WordPress from creating directories and writing files. Here's how to check and correct file permissions: 1. Connect to your website using an FTP client or through the File Manager in cPanel. 2. Navigate to the /wp-content/ directory. 3. Right-click on the /uploads/ directory and select 'File Permissions'. 4. Set the numeric value to 755 or 744. 5. Check the box that says 'Recurse into subdirectories' and then select 'Apply to directories only'. 6. Click 'OK' to apply the changes. 7. Repeat the process for all files in the /uploads/ directory, but this time set the numeric value to 644 or 640, and select 'Apply to files only'. Verify the Media Settings An incorrect file path in your WordPress settings can also cause this error. To check this: 1. Log in to your WordPress admin dashboard. 2. Navigate to Settings > Media. 3. In the 'Uploading Files' section, check the 'Store uploads in this folder' option. The default should be 'wp-content/uploads'. If it's different, change it back to the default. 4. Click 'Save Changes'.

Last updated on Jun 12, 2025

Resetting Your WordPress Admin Password: A Comprehensive Guide

At times, you may find yourself locked out of your WordPress admin account. Whether you've forgotten your password or need to change it for security reasons, this guide will walk you through three different methods to reset your WordPress admin password. Method 1: Resetting the Password via Softaculous in cPanel 1. Open your cPanel and navigate to the WordPress Manager by Softaculous. 2. Scroll down to locate the WordPress installation for which you need to change the password. 3. Click the edit icon (a pencil) next to the relevant installation. This will direct you to the installation editing screen. 4. Scroll to the Admin Account section and locate the Admin Password field. Enter a new, secure password that you can remember. 5. Now, return to your site and log in using your newly set password. Method 2: Resetting the Password via FTP If you're comfortable with FTP, you can also reset your password using this method. 1. Access your site using an FTP client or a code editor with FTP capabilities. 2. Navigate to the root directory of your site, then proceed to wp-content/themes. Locate the folder of your currently active theme. 3. In this folder, find the functions.php file. Download it for editing, but remember to create a backup first to prevent any issues. 4. Add the following line of code right after the opening 5. Save the modified file and upload it back to your site, overwriting the old version. 6. Your admin password will now be the one you set in the functions file. Log in to your site to confirm access. 7. Once logged in, remember to remove the line of code you added in the functions.php file. Method 3: Using the Lost Password Link If you have access to the email account associated with your WordPress account but can't remember your password, you can use the 'Lost your password?' link to reset it. 1. Navigate to your WordPress login page, typically located at /wp-admin (e.g., https://domain.com/wp-admin). 2. Click on the 'Lost your password?' link. 3. Enter your username or the email address associated with your WordPress account, then click 'Get New Password'. You'll receive an email with a link to create a new password. 4. Follow the link in the email to reset your password. 5. Log into your site using your new password and your username or email address. And there you have it! You've successfully reset your WordPress admin password. Remember, it's always a good idea to use a strong, unique password to ensure the security of your account.

Last updated on Jun 12, 2025

Enhancing WordPress Performance: Disabling WP-Cron for Faster Load Times

WordPress is a powerful platform, but like any software, it requires regular maintenance to perform optimally. One such maintenance task involves cron jobs, which are scheduled tasks that WordPress uses to perform various functions. However, the default WordPress cron handler, WP-Cron, can sometimes slow down your site. This guide will show you how to disable WP-Cron and use a system cron job instead for improved performance. Understanding Cron Jobs in WordPress Cron jobs are essential to WordPress, allowing tasks to be scheduled at specific times, dates, or intervals. These tasks can include publishing a scheduled post, checking for updates, or activating a backup plugin on a set schedule. WordPress uses a built-in cron handler, WP-Cron, to simulate system cron functionality. However, WP-Cron can potentially slow down your site, especially if it receives high traffic. The Performance Impact of WP-Cron WP-Cron isn't a true cron job; it's a workaround created by WordPress to emulate what a system cron does. WP-Cron doesn't run continuously. Instead, it's triggered on every page load, which can cause problems for high-traffic sites. If a site lacks sufficient PHP workers, a request might come in, WordPress will initiate the cron, but the cron has to wait for the worker, resulting in delays. For low-traffic sites, schedules could be missed because no one has loaded a page. A more efficient approach is to disable WP-Cron and use the system cron instead. This method operates on a pre-defined schedule and is even recommended in the official Plugin handbook. Disabling WP-Cron To disable WP-Cron, insert the following code into your wp-config.php file, just before the line that says "That's all, stop editing! Happy blogging." This action prevents WP-Cron from running on page load, but not when you call it directly via wp-cron.php. define('DISABLE_WP_CRON', true); Scheduling System Cron To schedule a system cron job, follow these steps: 1. Log in to your cPanel account and navigate to the 'Cron Jobs' option in the Advanced section. 2. In the 'Add New Cron Job' section, select a schedule. Your hosting provider likely has a limit on the frequency of cron jobs. Twice per hour is a common setting for shared hosts. 3. Enter the following command, replacing https://domain.com with your domain name. This command might vary slightly based on your hosting configuration. Then click on "Add New Cron Job." wget -q -O - https://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1 Note: The >/dev/null 2>&1 part of the command suppresses email notifications. By following these steps, you can optimize your WordPress site's performance by replacing WP-Cron with a system cron job. Remember, regular maintenance is key to keeping your WordPress site running smoothly.

Last updated on Jun 12, 2025

How do I use Redis Object Caching on my WordPress site if I don't use LSCache?

Litespeed Cache is strongly recommended as an alternative to other caching plugins and has been benchmarked to offer far superior performance due to its native ability to work with our Litespeed Enterprise web servers. However, if you are using any other plugin for caching that doesn't offer native Object Cache support, it's still possible to integrate with Redis using the 'Redis Object Cache' plugin. To install the 'Redis Object Cache' plugin for WordPress, follow these steps: 1. Log in to your WordPress admin dashboard. 2. Navigate to the 'Plugins' section by clicking on 'Plugins' in the left-hand menu. 3. Click on the 'Add New' button at the top of the page. 4. In the search bar, type 'Redis Object Cache' and press Enter. 5. Look for the 'Redis Object Cache' plugin by Till Krüss in the search results. 6. Click the 'Install Now' button next to the plugin. 7. After the installation is complete, click the 'Activate' button to enable the plugin on your WordPress site. Now that the plugin is installed and activated, you'll need to enable the Redis socket via the Redis section of cPanel...  Once within the Redis tool enable it for your account: 8cea05af98a43f0ae14f1ef06fc27e22dd68a930d4ae0d0550f29e5bfe225636de4efc900010fd69?t=863f5880e4b5789faca0c029876d7b87 Once enabled, copy the Redis socket path, as we will need this later! You can always return to this screen if you need to view this again. Now we need to enable the Redis extension; this is enabled under cPanel -> Select PHP Version -> Extensions -> Redis b90d43596909da08e36709a186a4d99f9578bdc66c286b49382c58e3129ce2e21a199104b5668f0a?t=e7642b817c8d3451f2dde2bec551188f Lastly, the plugin doesn't allow you to define a socket path within the interface, so we have to add the following lines to your wp-config.php file, ensuring the path is correct as per the Redis screen in cPanel... define('WP_REDIS_PATH', '/home/brixlymonitoring/tmp/redis.sock'); define('WP_REDIS_SCHEME', 'unix');  Once done, click 'Enable Object Cache' in the Redis WordPress Plugin...0441a58bf5be1493e0228d84826847e474d075a662d3ac1103147eab48a37dfbd9eb6110475cf00e?t=96fb6f4421c200496edc90ce8cb2ab59 If this has been done correctly, you should see something similar to the following...8507db23effb8cb49070e7486fca0a3bec2500a38943bf4c603925933e64eeaa1cfefff4c2512871?t=f4a45d1212a8d25458b81b35acf4f1dc

Last updated on Jun 12, 2025

Litespeed - Prevent LSCache from Auto-Installing

We have automated processes that will enable LSCache in bulk to all WordPress installations on the server to both improve the performance to your site and help with efficiency on the server itself.  LiteSpeed Cache (LSCache) is a built-in, high-performance dynamic content acceleration feature of LiteSpeed server products. LSCache accelerates dynamic content (not just PHP pages), with features very similar to those in Apache mod_cache, using an efficient, highly customizable, native implementation within the LiteSpeed server, which greatly reduces page load time and server load. If you wish to prevent us from being able to install Litespeed Cache / LSCache to your WordPress installation, you can 'flag' your WordPress installation to prevent this automated action from taking place.  Disable LSCache from Auto Installing 1. Login to cPanel, and navigate to 'LiteSpeed Web Cache Manager' 2. Click 'WordPress Cache' 3. Click 'Scan' to scan for WordPress installations 4. Click 'Flag' next to any domains you wish to disable LSCache Disable LSCache where it has already been enabled 1. Login to cPanel, and navigate to 'LiteSpeed Web Cache Manager' 2. Click 'WordPress Cache' 3. Click 'Scan' to scan for WordPress installations 4. Click 'Disable' next to the WordPress installation This adds a .litespeed_flag file to the directory root of your site, which tells LiteSpeed not to install the cache onto your site. For a new cPanel account, you can have this be added automatically by adding the .litespeef_flag file to the Skeleton directory of your reseller account. You can see further details on creating skeleton directories in cPanel below: https://docs.cpanel.net/knowledge-base/accounts/how-to-create-a-skeleton-directory

Last updated on Jun 12, 2025

Execute PHP scripts with no timeout when using Litespeed

Some PHP scripts need to run for long periods of time without interruption. Examples include WordPress modules such as BackupBuddy, ImportBuddy, or any other module that relies on a WordPress built-in cron job. Whenever a PHP application rebuilds MySQL indexes, the process may run for a long time. Generally, allowing a PHP script to run forever is not desirable. Thus there are a number of features (in LiteSpeed Web Server and built into PHP itself) that may prevent a PHP process from running long enough to finish. You may need to set up more than one of the following configurations to ensure your application works correctly. Override LiteSpeed Connection Timeout If a script does not send back anything for a long time, this can trigger a connection timeout, and the server will close the client connection. This is done to prevent poorly written PHP scripts from tying up the server. To get desired functionality from your web applications, though, you may need to prevent the connection from being timed out. (If the noabort environment variable above has been set, the script will continue to run even though the connection has been broken. Your application, though, may require the connection to stay open for correct functionality.) Connection timeout can be prevented by either increasing the global connection timeout setting (via the WebAdmin console) or using LiteSpeed's noconntimeout environment variable. Similar to the noabort environment variable, you can add the noconntimeout environment variable via a rewrite rule or using the SetEnv/SetEnvIf directives. (The rewrite flag is preferred for controlling a single account. The SetEnv/SetEnvIf directives are preferred for rules that will apply to all accounts.) noconntimeout is a LiteSpeed-specific environment variable, so all of the following examples should be placed inside: ... Directive example for wp-cron.php, backupbuddy.php, and importbuddy.php only combined with noabort SetEnvIf Request_URI "(wp-cron|backupbuddy|importbuddy)\.php" noabort noconntimeout Rewrite rule example for all requests RewriteEngine On RewriteRule .* - [E=noconntimeout:1] Rewrite rule example for wp-cron.php, backupbuddy.php, and importbuddy.php only RewriteRule (wp-cron|backupbuddy|importbuddy)\.php - [E=noconntimeout:1] Rewrite rule example combined with noabort RewriteRule (wp-cron|backupbuddy|importbuddy)\.php - [E=noabort:1, E=noconntimeout:1] Turn off Broken Connection Aborting When a user closes a connection (by closing a window, for example), LSWS will abort processing that PHP script by killing the PHP process. This is to avoid wasting system resources and to prevent certain types of DoS attacks. In some cases, though, it is preferable not to abort the PHP script, regardless of whether the connection has been closed. For example, built-in WordPress cron jobs start a background job by sending a request to wp-cron.php, then immediately closing the connection without waiting for a response. In order for the cron job to complete, though, the web server must keep the PHP engine running without interruption. In this case, you need to turn off broken connection aborting. This be done at the server level in LSWS's WebAdmin Console or by using LiteSpeed's noabort environment variable. Aborting for a broken connection can be turned off by using the request-level noabort environment variable. This can be done in a rewrite rule or by using the SetEnv/SetEnvIf directives. noabort is a LiteSpeed-specific environment variable, so all of the following rules should be placed in ... The [E=noabort:1] flag can be added to any rewrite rule. The rewrite rule can be in an Apache .htaccess file or vhost-level configuration file. The rewrite flag should generally be used for a single account only. Rewrite rules and SetEnv should not be used together. We recommend choosing the SetEnv directive over rewrite rules for two reasons: 1. Rewrite rules are sensitive to a position among the other rules. SetEnv can go anywhere in the config file. 2. Rewrite rules cannot be easily inherited. To impact all accounts with one setting, the SetEnvIf directive should be used. Directive example for all requests SetEnv noabort 1 Directive example for wp-cron.php, backupbuddy.php, and importbuddy.php only SetEnvIf Request_URI "(wp-cron|backupbuddy|importbuddy)\.php" noabort Rewrite rule example for all requests RewriteEngine On RewriteRule .* - [E=noabort:1] Rewrite rule example for wp-cron.php, backupbuddy.php, and importbuddy.php only RewriteEngine On RewriteRule (wp-cron|backupbuddy|importbuddy)\.php - [E=noabort:1]

Last updated on Jun 12, 2025

Litespeed - Comparing QUIC.cloud and Cloudflare

As part of our ongoing effort to provide you with the latest in web hosting, here we’ll break down the differences and similarities between QUIC.cloud and Cloudflare, two leading solutions integrated with LiteSpeed. Overview - LiteSpeed Integration: Both Cloudflare and QUIC.cloud enhance the capabilities of a LiteSpeed-powered website. However, their core functionalities and features vary in certain aspects. Using QUIC.cloud and Cloudflare Together - Feasibility: It's technically possible to run both simultaneously. QUIC.cloud handles dynamic HTML pages while Cloudflare can manage static content. - Recommendation: Although possible, it's advisable to keep the architecture simple to minimize potential backend complications. Choose one solution based on your specific needs. Caching Capabilities - QUIC.cloud: - Caches both static files and dynamic HTML pages. - Syncs with the LiteSpeed extension on your backend to determine updated pages and selectively purges them from the cache. - Cloudflare: - Primarily caches static files by default. - Introduced the “APO” feature as a counter to QUIC.cloud’s dynamic caching capabilities. Note: APO comes with a cost for free-tier users. Integration and Features - QUIC.cloud: - Offers deeper integration with sites and boasts of a broader feature set than Cloudflare’s APO. - Facilitates auto-generation of critical CSS for specific pages at no additional cost. - Plans to introduce a "pre-warm" feature, ensuring rapid loading speeds even for first-time site visitors. - Cloudflare: - While offering robust features, its APO doesn’t support functionalities like updating critical CSS. - Has been a major player in the market for years, known for its reliability and expansive CDN. Pricing and Plans - QUIC.cloud: - Offers a significant free tier, especially beneficial for LiteSpeed server users. - Cloudflare: - Although having a free tier, certain advanced features like APO come at an additional cost. In Conclusion The competition between QUIC.cloud and Cloudflare is heating up, with both presenting their unique strengths. Depending on your site's requirements, either could be an optimal choice. Brixly aims to keep you informed, ensuring you make the best decisions for your web hosting needs. Stay tuned to our knowledgebase for more insights and updates.

Last updated on Jun 12, 2025

LiteSpeed Cache vs. WP Rocket: A Comprehensive Comparison for Our Hosting Environment

Introduction:  When it comes to accelerating your WordPress website, choosing the right caching solution is crucial. Two of the most popular caching plugins are LiteSpeed Cache (LSCache) and WP Rocket. In this article, we'll compare these solutions to help you understand why LSCache is often the preferred choice for websites hosted on our LiteSpeed servers. Server-Level vs. PHP-Level Caching:  LiteSpeed Cache operates at the server level, leveraging the built-in caching capabilities of LiteSpeed Web Server. This allows for faster response times as it bypasses PHP and database queries altogether. WP Rocket, on the other hand, is a PHP-level caching plugin, which means it sits on top of the WordPress installation and is not as deeply integrated with the server software. Compatibility and Performance:  Our hosting environment is optimized for LiteSpeed, making LSCache a seamless fit. It is designed to work in tandem with LiteSpeed's server features, ensuring that your website can handle traffic spikes and high loads with ease. While WP Rocket is compatible with various server types, it doesn't offer the same level of integration and performance optimization that you get with LSCache on a LiteSpeed server. Feature Set:  Both LSCache and WP Rocket offer page caching, minification, and lazy loading, among other features. However, LSCache provides additional benefits such as ESI (Edge Side Includes) support, which allows for hole punching on cached pages, and QUIC.cloud CDN integration for enhanced global performance. LSCache's tag-based smart purging also ensures that your cache is always up to date without unnecessary purges. Cost Considerations:  LSCache is a free, open-source plugin available to all WordPress users on LiteSpeed servers. WP Rocket is a premium plugin, which means there's an ongoing cost associated with its use. For budget-conscious site owners, LSCache offers a cost-effective solution without compromising on features or performance. Ease of Use:  Both plugins aim to be user-friendly, but LSCache offers an extra level of convenience for our clients. It integrates directly with cPanel, allowing you to manage cache settings easily within your hosting control panel. This integration simplifies cache management and saves time for website administrators. Conclusion:  While WP Rocket is a well-respected caching plugin in the WordPress community, LSCache holds a distinct advantage for websites hosted on our LiteSpeed servers. With its server-level caching, comprehensive feature set, and seamless integration with our hosting environment, LSCache stands out as the optimal choice for enhancing your website's performance. If you're interested in taking advantage of LiteSpeed Cache on our servers, or if you have any questions about optimizing your website, our support team is here to assist you every step of the way.

Last updated on Jun 12, 2025

PHP Handlers: Why PHP-FPM is Not Enabled on Brixly Accounts

At Brixly, we are committed to providing the best performance and reliability for your web hosting needs. As part of this commitment, we have chosen to use LiteSpeed Enterprise as our web server solution. LiteSpeed is known for its high performance and scalability, which is why it's an integral part of our hosting environment. One common question we receive from our clients is whether they can enable PHP-FPM on their accounts. The answer is no, and here's why: LiteSpeed and mod_lsapi: A Superior Combination Instead of PHP-FPM, our servers utilize the mod_lsapi PHP handler, which is part of the LiteSpeed Web Server environment. Mod_lsapi is renowned for its ability to serve PHP content quickly and efficiently. It is a more lightweight handler compared to PHP-FPM and has been benchmarked to outperform it in various scenarios. Why Not PHP-FPM? PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. However, it's not the only or necessarily the best option for every server environment. In the case of Brixly's hosting setup, LiteSpeed Enterprise with mod_lsapi offers several advantages: 1. **Performance: **Mod_lsapi is specifically designed to work with LiteSpeed, meaning it can communicate more effectively with the web server, leading to faster response times and lower memory usage. 2. Stability: With mod_lsapi, each user's PHP processes are managed individually, which provides better stability and security. This isolation ensures that a single user's resource consumption does not impact the overall server performance. 3. Compatibility: Mod_lsapi is fully compatible with all the features of PHP, including opcode caching and accelerators like LiteSpeed Cache (LSCache). This ensures that your applications run smoothly without any compatibility issues. 4. **Efficiency: **LiteSpeed's caching capabilities are far superior, allowing dynamic content to be served at speeds comparable to static content. This efficiency is not something that PHP-FPM can provide on its own. Conclusion While PHP-FPM is a popular PHP handler, it is not supported on Brixly's hosting environment due to the superior performance and efficiency of LiteSpeed Enterprise with mod_lsapi. Our focus is on providing a hosting solution that is not only fast but also stable and secure. By leveraging LiteSpeed's advanced features, we ensure that your websites perform at their best without the need for PHP-FPM. For more information on how LiteSpeed and mod_lsapi enhance your hosting experience, or if you have any questions about optimizing your website, our support team is here to assist you. Please feel free to reach out to us through our support channels.

Last updated on Jun 12, 2025