// Tutorial //

How To Upgrade to PHP 7 on CentOS 7

Published on January 14, 2016
Default avatar
By Brennen Bearnes
Developer and author at DigitalOcean.
How To Upgrade to PHP 7 on CentOS 7


PHP 7, which was released on December 3, 2015, promises substantial speed improvements over previous versions of the language, along with new features like scalar type hinting. This guide explains how to quickly upgrade an Apache or Nginx web server running PHP 5.x (any release) to PHP 7, using community-provided packages.

Warning: As with most major-version language releases, it’s best to wait a little while before switching to PHP 7 in production. In the meanwhile, it’s a good time to test your applications for compatibility with the new release, perform benchmarks, and familiarize yourself with new language features.

If you have installed phpMyAdmin for database management, it is strongly recommended that you wait for official CentOS PHP 7 packages before upgrading, as phpMyAdmin packages do not yet support the upgrade. If you’re running any other services or applications with active users, it is safest to first test this process in a staging environment.


This guide assumes that you are running PHP 5.x on CentOS 7, using either mod_php in conjunction with Apache, or PHP-FPM in conjunction with Nginx. It also assumes that you have a non-root user configured with sudo privileges for administrative tasks.

The PHP 5 installation process is documented in these guides:

Subscribing to the IUS Community Project Repository

Since PHP 7.x is not yet packaged in official repositories for the major distributions, we’ll have to rely on a third-party source. Several repositories offer PHP 7 RPM files. We’ll use the IUS repository.

IUS offers an installation script for subscribing to their repository and importing associated GPG keys. Make sure you’re in your home directory, and retrieve the script using curl:

  1. cd ~
  2. curl 'https://setup.ius.io/' -o setup-ius.sh

Run the script:

  1. sudo bash setup-ius.sh

Upgrading mod_php with Apache

This section describes the upgrade process for a system using Apache as the web server and mod_php to execute PHP code. If, instead, you are running Nginx and PHP-FPM, skip ahead to the next section.

Begin by removing existing PHP packages. Press y and hit Enter to continue when prompted.

  1. sudo yum remove php-cli mod_php php-common

Install the new PHP 7 packages from IUS. Again, press y and Enter when prompted.

  1. sudo yum install mod_php70u php70u-cli php70u-mysqlnd

Finally, restart Apache to load the new version of mod_php:

  1. sudo apachectl restart

You can check on the status of Apache, which is managed by the httpd systemd unit, using systemctl:

  1. systemctl status httpd

Upgrading PHP-FPM with Nginx

This section describes the upgrade process for a system using Nginx as the web server and PHP-FPM to execute PHP code. If you have already upgraded an Apache-based system, skip ahead to the PHP Testing section.

Begin by removing existing PHP packages. Press y and hit Enter to continue when prompted.

  1. sudo yum remove php-fpm php-cli php-common

Install the new PHP 7 packages from IUS. Again, press y and Enter when prompted.

  1. sudo yum install php70u-fpm-nginx php70u-cli php70u-mysqlnd

Once the installation is finished, you’ll need to make a few configuration changes for both PHP-FPM and Nginx. As configured, PHP-FPM listens for connections on a local TCP socket, while Nginx expects a Unix domain socket, which maps to a path on the filesystem.

PHP-FPM can handle multiple pools of child processes. As configured, it provides a single pool called www, which is defined in /etc/php-fpm.d/www.conf. Open this file with nano (or your preferred text editor):

  1. sudo nano /etc/php-fpm.d/www.conf

Look for the block containing listen =, which tells PHP-FPM to listen on the loopback address at port 9000. Comment this line with a semicolon, and uncomment listen = /run/php-fpm/www.sock a few lines below.

; The address on which to accept FastCGI requests.
; Valid syntaxes are:
;   'ip.add.re.ss:port'    - to listen on a TCP socket to a specific IPv4 address on
;                            a specific port;
;   '[ip:6:addr:ess]:port' - to listen on a TCP socket to a specific IPv6 address on
;                            a specific port;
;   'port'                 - to listen on a TCP socket to all addresses
;                            (IPv6 and IPv4-mapped) on a specific port;
;   '/path/to/unix/socket' - to listen on a unix socket.
; Note: This value is mandatory.
;listen =
; WARNING: If you switch to a unix socket, you have to grant your webserver user
;          access to that socket by setting listen.acl_users to the webserver user.
listen = /run/php-fpm/www.sock

Next, look for the block containing listen.acl_users values, and uncomment listen.acl_users = nginx:

; When POSIX Access Control Lists are supported you can set them using
; these options, value is a comma separated list of user/group names.
; When set, listen.owner and listen.group are ignored
;listen.acl_users = apache,nginx
;listen.acl_users = apache
listen.acl_users = nginx
;listen.acl_groups =

Exit and save the file. In nano, you can accomplish this by pressing Ctrl-X to exit, y to confirm, and Enter to confirm the filename to overwrite.

Next, make sure that Nginx is using the correct socket path to handle PHP files. Start by opening /etc/nginx/conf.d/default.conf:

  1. sudo nano /etc/nginx/conf.d/php-fpm.conf

php-fpm.conf defines an upstream, which can be referenced by other Nginx configuration directives. Inside of the upstream block, use a # to comment out server;, and uncomment server unix:/run/php-fpm/www.sock;:

# PHP-FPM FastCGI server
# network or unix domain socket configuration

upstream php-fpm {
        server unix:/run/php-fpm/www.sock;

Exit and save the file, then open /etc/nginx/conf.d/default.conf:

  1. sudo nano /etc/nginx/conf.d/default.conf

Look for a block beginning with location ~ \.php$ {. Within this block, look for the fastcgi_pass directive. Comment out or delete this line, and replace it with fastcgi_pass php-fpm, which will reference the upstream defined in php-fpm.conf:

  location ~ \.php$ {
      try_files $uri =404;
      fastcgi_split_path_info ^(.+\.php)(/.+)$;
      # fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;
      fastcgi_pass php-fpm;
      fastcgi_index index.php;
      fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
      include fastcgi_params;

Exit and save the file, then restart PHP-FPM and Nginx so that the new configuration directives take effect:

  1. sudo systemctl restart php-fpm
  2. sudo systemctl restart nginx

You can check on the status of each service using systemctl:

  1. systemctl status php-fpm
  2. systemctl status nginx

Testing PHP

With a web server configured and the new packages installed, we should be able to verify that PHP is up and running. Begin by checking the installed version of PHP at the command line:

  1. php -v
PHP 7.0.1 (cli) (built: Dec 18 2015 16:35:26) ( NTS )
Copyright (c) 1997-2015 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2015 Zend Technologies

You can also create a test file in the web server’s document root. Although its location depends on your server configuration, the document root is typically set to one of these directories:

  • /var/www/html
  • /var/www/
  • /usr/share/nginx/html

Using nano, open a new file called info.php in the document root. By default, on Apache, this would be:

  1. sudo nano /var/www/html/info.php

On Nginx, you might instead use:

  1. sudo nano /usr/share/nginx/html/info.php

Paste the following code:


Exit the editor, saving info.php. Now, load the following address in your browser:


You should see the PHP 7 information page, which lists the running version and configuration. Once you’ve double-checked this, it’s safest to delete info.php:

  1. sudo rm /var/www/html/info.php

You now have a working PHP 7 installation. From here, you may want to check out Erika Heidi’s Getting Ready for PHP 7 blog post, and look over the official migration guide.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.

Sign up
About the authors
Default avatar
Developer and author at DigitalOcean.

Still looking for an answer?

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These instructions don’t work any more, Executing the yum install command yields the following error.

No package mod_php70u available.
No package php70u-cli available.
No package php70u-mysqlnd available.

php70 is no longer available. must be php71 or php72.

Hi Can you explain what the difference is between PHP70, PHP70u and PHP70w extensions.

Also is the IUS repository still the best to use?


Great doc already.

It might be useful to explain how to list the current modules you have installed for PHP.

yum list installed | grep -i php

This way you can remember which modules to installed after upgrading.

This is probably OK for core php with Apache type users. For Nginx and php-fpm, it’s useless.

Doesn’t work, buddy. Update this tutorial, because this comes up first in DO search for these words, and is dangerous.

No package php70u-fpm-nginx available.
No package php70u-cli available.
No package php70u-mysqlnd available.
Error: Nothing to do

This comment has been deleted

First and foremost thanks for this great info. Not new to IT, but new to building out my own LAMP and Wordpress stack.

So I installed LAMP based off this article https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-centos-7

Then trying to upgrade to latest version of PHP from this article. I figured out my way around the errors from “yum install mod_php70u php70u-cli php70u-mysqlnd” - Just specified 7.2 rather than 7.0.

Everything seems to install ok and checking version from command line look fine.

[root@centos1 ~]# php -v PHP 7.2.14 (cli) (built: Jan 11 2019 10:01:17) ( NTS ) Copyright © 1997-2018 The PHP Group Zend Engine v3.2.0, Copyright © 1998-2018 Zend Technologies

However when I tested php using the info.php test initially the version screen still showed the PHP version 5 web page that I got when installing LAMP. I rebooted, thinking that would help out, but now when i browse to the info.php file it just renders the text in the info.php file.

Looking for help Thanks!

I am trying to upgrade the PHP version on this server from 5.6.19 to the latest PHP 7.2. But these instructions point to “php72”, which makes me wonder if 5.6.19 will be seamlessly replaced.

If I remove 5,6.19, I run the risk of totally deleting old settings. I find there are important settings in three places:

There are important settings in a few places:

  1. /etc/php-fpm.d/www.conf (my file: https://pastebin.com/phyvsVH3 )
  2. /etc/php.ini (my file: https://pastebin.com/UC5HaZWt )
  3. /etc/php-fpm.conf (my file: https://pastebin.com/AAMev0hK )
  4. /etc/nginx/common.conf (my file: https://pastebin.com/kGgceLf0 )
  5. /etc/nginx/fastcgi.conf (my file: https://pastebin.com/YXAQ1yyj )

And of course the Nginx.conf (the main Ngnix config file) has calls to PHP-FPM accordingly. They include the #4 file above, common.conf, which in turn includes the fastcgi.conf.

Instructions on external websites, such as this one– https://www.cyberciti.biz/faq/how-to-install-php-7-2-on-centos-7-rhel-7/ –Do not take into account Nginx and PHP-FPM specifics especially in terms of old PHP 5.6.19 already existing.

All these instructions anyway speak of “php72”, which I am afraid will change all the paths, and I’ll have to update all paths to new php links everywhere.

Could you please advise how best to do this so I seamless upgrade the old PHP with the latest, with all the usual paths as above working? Otherwise we need to

a. Remove 5.6.19 b. Install 7.2, and all additional modules (which will introduce the “php72” in the paths) c. Make sure all paths everywhere are new everywhere…

Any way to make this simpler?

Hi, after upgrading to php7, site is ok its downloading php files. can u help?

Digital Ocean has got many simple and useful tutorials, i just love them. Thanks!