# Curl: (52) Empty reply from server

**URL:** <https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276>\
**Category:** Questions\
**Created:** [April 12, 2019, 2:50am UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276 "2019-04-12T02:50:18Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bitcoder](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/bitcoder/32/900_2.png) [@bitcoder](https://discuss.konghq.com/u/bitcoder)\
**Post date:** [April 12, 2019, 2:50am UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/1 "2019-04-12T02:50:18Z")

</div>

I followed the instructions to set up and start kong on my macOS. It seems work fine. I got no error message. However I ‘got curl: (52) Empty reply from server’ with curl -i [http://localhost:8001/](http://localhost:8001/) command.

---

<div class="post-metadata">

**Author:** ![kayaman](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/kayaman/32/867_2.png) [@kayaman](https://discuss.konghq.com/u/kayaman)\
**Post date:** [April 12, 2019, 5:19am UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/2 "2019-04-12T05:19:21Z")

</div>

Which installation method you used?

---

<div class="post-metadata">

**Author:** ![bitcoder](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/bitcoder/32/900_2.png) [@bitcoder](https://discuss.konghq.com/u/bitcoder)\
**Post date:** [April 12, 2019, 2:33pm UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/3 "2019-04-12T14:33:41Z")

</div>

brew install kong (I use postgresSQL, not using Cassandra)

---

<div class="post-metadata">

**Author:** ![kayaman](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/kayaman/32/867_2.png) [@kayaman](https://discuss.konghq.com/u/kayaman)\
**Post date:** [April 12, 2019, 2:38pm UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/4 "2019-04-12T14:38:13Z")

</div>

`kong migrations bootstrap` ran successfully?

---

<div class="post-metadata">

**Author:** ![Joseph\_Bruni](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/joseph_bruni/32/835_2.png) [@Joseph\_Bruni](https://discuss.konghq.com/u/Joseph_Bruni)\
**Post date:** [April 12, 2019, 5:24pm UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/5 "2019-04-12T17:24:54Z")

</div>

This is related to a recent patch of PCRE in 8.4.3 on macos.

> <https://github.com/Kong/kong/issues/4471>

---

<div class="post-metadata">

**Author:** ![Tony\_Murphy](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/tony_murphy/32/914_2.png) [@Tony\_Murphy](https://discuss.konghq.com/u/Tony_Murphy)\
**Post date:** [April 15, 2019, 6:14pm UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/6 "2019-04-15T18:14:33Z")

</div>

i had similar problems

brew uninstall luarocks  
brew uninstall openresty  
brew install kong

and rebooted mac a few times - eventually got it to work.

run with kong start -vv

---

<div class="post-metadata">

**Author:** ![Joseph\_Bruni](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/joseph_bruni/32/835_2.png) [@Joseph\_Bruni](https://discuss.konghq.com/u/Joseph_Bruni)\
**Post date:** [April 15, 2019, 11:35pm UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/7 "2019-04-15T23:35:55Z")

</div>

Over the weekend, there was a fix to the way Openresty uses PCRE to workaround this problem. When you did the uninstall//reinstall cycle, you must have picked up the newer version of Openresty.

---

<div class="post-metadata">

**Author:** ![kayaman](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/kayaman/32/867_2.png) [@kayaman](https://discuss.konghq.com/u/kayaman)\
**Post date:** [April 16, 2019, 2:01am UTC](https://discuss.konghq.com/t/curl-52-empty-reply-from-server/3276/8 "2019-04-16T02:01:48Z")

</div>

It doesn’t look like a bug. It’s the expected response message from a fresh install. Have you set up any route yet?