php files downloading instead of running cpanel

PHP FILES DOWNLOADING INSTEAD OF RUNNING CPANEL FULL

Once you understand how PHP-FPM works, you may want to try enabling it for at least some sites and see if it helps at all.Disclosure: I may receive affiliate compensation for some of the links below at no cost to you if you decide to purchase a paid plan. On cPanel, we recommend defaulting to suPHP, LSAPI or FCGI. What you should use depends on your server's resources and the types of PHP sites you need to serve. Not compatible with mod_ruid2 or mpm_itk (but it shouldn't need them).

PHP FILES DOWNLOADING INSTEAD OF RUNNING CPANEL FULL

You don't get full benefits without purchasing a third-party commercial product.Less memory use than most other handlers.Designed to perform as well or better than PHP-FPM under certain circumstance.This handler requires CloudLiunx or LSWS for the maximum benefits. Using this handler, the system will run PHP scripts as the user that owns the domain or subdomain. This handler implements the LiteSpeed Web Server (LSWS) SAPI. PHP Opcode caching has no performance improvement and only wastes memory.cPanel configures suPHP so that it blocks accessing or executing any files or directories with permissions higher than 755 for security.cPanel their copy of suPHP with the latest security fixes. On cPanel servers, it is also configured to disallow execution of files with unsafe permissions. This handler was specifically designed to serve PHP scripts as the owner of the domain or subdomain that is executing the PHP script. htaccess file and some directives can only be changed on a global level. Cannot put PHP configuration changes in an.Can be somewhat more complicated to manage.This handler can use more memory than any other handler listed here, but that depends on the number of sites using PHP-FPM and the configuration of the FPM pool.Allows for some additional level of flexibility per pool.Each FPM pool can have independent settings. Using this handler, the system will run PHP scripts as the user that owns the domain or subdomain. It is an improved way of implementing FastCGI processing of PHP. This handler uses more memory than most of the others.įPM stands for FastCGI Process Manager.There are some differences between mod_fastcgi and mod_fcgid, but none that are relevant to the scope of this article. htaccess file.įastCGI is a variation of the CGI protocol that provides a number of benefits over the older CGI handler. Using this module, the system will run PHP scripts as the user that owns the domain or subdomain. Doesn't work well with PHP opcode caching.

Scripts run as the domain or subdomain user, not as the Apache user.

For example, on a cPanel server, if the script creates a file or directory, that file will be owned by the user 'nobody' which can cause problems when the account owner goes to backup or remove them.

Scripts run as the Apache user rather than the owner of the domain or subdomain.

Only works with a single version of PHP on cPanel servers (you'll need to use other handers for other versions of PHP if you offer them).

Works with mod_ruid2 or mpm_itk modules.

PHP scripts parsed by mod_php run as the same user that Apache itself does (rather than the user account that hosts the PHP files. This module allows Apache itself to directly parse and display PHP files. In broad terms, how does each PHP handler work and what are the pros and cons of working with each of them?Įach module provides a different method of parsing PHP. (unless LiteSpeed Web Server is installed)

Php files downloading instead of running cpanel