How To Fix MacOS ERR_EMPTY_RESPONSE

While installing few php scripts on my local MacOS Monterey I started getting ERR_EMPTY_RESPONSE error in Chrome browser.

First I encountered this issue while installing Typo3 CMS. I tried installing phpMyAdmin and got the same error.

ERR_EMPTY_RESPONSE on MacOS Google Chrome
ERR_EMPTY_RESPONSE on MacOS Google Chrome

Digging down further and after some tweaking with apache config files and php.ini files I found out that the problem is with Google Chrome and not with MacOS in particular. There may have been some Apache and/or php.ini config settings which fixed this error in other browsers but I’m not sure what is the exact fix.

The Solution

I’m not sure what exactly caused this problem but other folks have been saying it’s cache.

Try cleaning Google Chrome cache.

Restart Mac.

Try in other browsers.

Digging down further it seems that there is something wrong with configuration file.

Checking the apache access log file shows following error

127.0.0.1 – – [04/Nov/2022:22:05:48 +0000] “GET /wp/wp-admin HTTP/1.1” 301 237

Apache error log shows this

[Fri Nov 04 22:08:12.569415 2022] [core:notice] [pid 139] AH00052: child pid 71636 exit signal Segmentation fault (11)

2 comments

  1. Hello, I’m getting exactly same error in Chrome browser on my MacBook Pro. It works on safari browser. I’ve cleaned Cache, restarted macbook but still getting same error. It is frustrating. How to fix it?

    1. There is no single definite solution for this problem. There is something wrong with configuration somewhere. You have to try different solutions and see which one works out for you. The root of the problem lies with Apple when they stopped php support on latest macOS, so blame them for all the mess.

Leave a comment

Your email address will not be published. Required fields are marked *