Could not get response

How to Fix Apache Stopped Working After PHP Upgrade


Upgrading PHP is a common practice among website owners and developers to ensure better performance, security, and access to the latest features. However, it is not uncommon to encounter issues after upgrading, such as Apache Stopped Working.

Apache Stopped Working after upgrading
Upgrading PHP using Homebrew

Moreover, Apache is a popular web server that powers millions of websites around the world. However, sometimes issues can arise after upgrading PHP, causing Apache to stop working.

This article will examine the potential causes of this issue and offer troubleshooting tips and effective remedies to assist in restoring your website’s functionality.

Why Apache Stopped Working After PHP Upgrade

Incompatible PHP Version

One possible reason for Apache to stop working after a PHP upgrade is an incompatible PHP version. Different versions of PHP may have different requirements and configurations that can conflict with your Apache server settings.

Also, ensure that you have downloaded and installed the correct PHP version that is compatible with your Apache server. Refer to the official PHP documentation for the recommended PHP version for your Apache version.

Configuration Errors

Another potential cause for Apache to stop working is configuration errors. Sometimes, during the PHP upgrade process, the configuration files may not be updated correctly, leading to conflicts with Apache.

Furthermore, check your Apache configuration files, such as httpd.conf or apache2.conf, for any syntax errors or misconfigurations. Pay close attention to the PHP module settings and make sure they are correctly specified.

Extension Compatibility

Extensions or modules play a crucial role in the functioning of PHP and Apache. Incompatibility between the PHP extension versions and the upgraded PHP version can lead to Apache stopping.

Ensure that all the PHP extensions you are using are compatible and up to date with the PHP version you have upgraded to. Consult the documentation of each extension to verify their compatibility with your PHP version.

Memory Limit

PHP upgrades often come with changes in default memory limits. If your PHP scripts or applications require more memory than the default limit allows, it can cause Apache to stop working.

Increase the memory limit in your PHP configuration file (php.ini) by adjusting the “memory_limit” directive. Be cautious not to set it too high, as it may consume excessive server resources.

Conflict with Other Services

Sometimes, Apache may stop working after a PHP upgrade due to conflicts with other services running on your server. Check for any other software or services, like caching servers or load balancers, that could be causing conflicts with Apache.

Temporarily disable these services and see if Apache starts working again. If it does, you may need to reconfigure or update those services to be compatible with the upgraded PHP version.

How to Fix Apache Stopped Working After PHP Upgrade

If Apache stopped working after a PHP upgrade on macOS, you can follow these steps to troubleshoot and resolve the issue:

Check Apache and PHP Version Compatibility

Ensure that the PHP version you upgraded to is compatible with the version of Apache you have installed. Check the PHP documentation and Apache website for compatibility information.

Verify PHP Installation

Double-check that the new PHP version is installed correctly on your macOS. You can do this by opening Terminal and running the following command:

php -v

This will display the installed PHP version. Make sure it matches the version you intended to upgrade to.

Restart Apache if Apache Stopped Working

After the PHP upgrade, restart Apache to apply the changes. Open Terminal and use the following command:

"sudo apachectl restart" or "sudo apachectl -k restart"

You will need to enter your administrator password when prompted.

Check Apache Configuration

Review the Apache configuration files to ensure they are set up correctly to use the new PHP version. The main Apache configuration file is usually located at “/etc/apache2/httpd.conf” or “/usr/local/etc/httpd”

  • Look for the LoadModule directive for PHP. It should point to the new PHP module.
  • Check for any custom PHP-related configurations that might have been overwritten during the upgrade.

To edit the configuration file, you can use a text editor like Nano or vi:

"sudo nano /etc/apache2/httpd.conf" or "sudo nano /usr/local/etc/httpd/httpd.conf"
apache stopped working
Apache stopped working if the “” file location is still pointing to the old one, make sure the new path is correct.

Lastly, make the necessary changes and save the file. Then restart Apache again using the command mentioned above.

Check PHP Configuration

Verify that PHP’s configuration is compatible with Apache. The PHP configuration file is usually located at /etc/php.ini.

sudo nano /etc/php.ini

Ensure that PHP is configured as an Apache module. Look for the following line:


Remove the semicolon (;) at the beginning of the line if it exists, so it becomes:

Lastly, save the file and restart Apache.

Test with a Simple PHP Script

Create a simple PHP script (e.g., info.php) containing phpinfo();. Save the file in your Apache web server’s document root (usually /Library/WebServer/Documents/).

Then, access the script through your web browser by navigating to http://localhost/info.php.

If PHP is working correctly, you should see a page displaying PHP information. If not, there may be specific error messages to help diagnose the issue.

Check Apache Error Log

If Apache is still not working, check the Apache error log for any error messages. The log file is usually located at /var/log/apache2/error_log. Open the log file with a text editor or view it in Terminal using:

sudo tail -n 50 /var/log/apache2/error_log

This will display the last 50 lines of the error log. Look for any clues about what might be causing the issue.


If you encounter problems with Apache following a PHP upgrade, it can be quite frustrating. However, by taking into account these potential causes and following the troubleshooting guidelines provided, you should be able to pinpoint and solve the issue.

Additionally, it is crucial to conduct comprehensive testing after any upgrades or modifications to ensure that your website functions smoothly.

If the problem persists, it is advisable to consult with a professional or seek assistance from the PHP or Apache communities for further support.

Lastly, consider reaching out to relevant online communities, forums, or official support channels for macOS, Apache, and PHP. Other users may have faced similar problems and discovered effective solutions.

If you come across this error Brew postinstall node Error : “post-install step did not complete successfully”. You may check out this article here :