# Local 2.3.2 not working if changing default settings

**URL:** <https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591>\
**Category:** Support\
**Created:** [August 2, 2018, 11:46am UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591 "2018-08-02T11:46:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![prodev](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/prodev/32/5422_2.png) [@prodev](https://community.localwp.com/u/prodev)\
**Post date:** [August 2, 2018, 11:46am UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/1 "2018-08-02T11:46:04Z")

</div>

```
2018/08/02 11:40:11 [error] 6#6: *1 upstream prematurely closed connection while reading response header from upstream, client: 172.18.0.3, server: test.local, request: "GET /2018/08/02/hello-world/ HTTP/1.1", upstream: "http://192.168.95.100:4000/2018/08/02/hello-world/", host: "test.local", referrer: "http://test.local/2018/08/02/hello-world/"
2018/08/02 11:40:11 [error] 6#6: *3 upstream prematurely closed connection while reading response header from upstream, client: 172.18.0.3, server: test.local, request: "GET /index.php/2018/08/02/hello-world/ HTTP/1.1", upstream: "http://192.168.95.100:4000/index.php/2018/08/02/hello-world/", host: "test.local", referrer: "http://test.local/index.php/2018/08/02/hello-world/"
2018/08/02 11:40:13 [error] 6#6: *5 upstream prematurely closed connection while reading response header from upstream, client: 172.18.0.3, server: test.local, request: "POST /wp-cron.php?doing_wp_cron=1533210013.0562748908996582031250 HTTP/1.1", upstream: "http://192.168.95.100:4000/wp-cron.php?doing_wp_cron=1533210013.0562748908996582031250", host: "test.local", referrer: "http://test.local/wp-cron.php?doing_wp_cron=1533210013.0562748908996582031250"
2018/08/02 11:40:29 [error] 6#6: *7 upstream prematurely closed connection while reading response header from upstream, client: 192.168.95.1, server: test.local, request: "GET / HTTP/1.1", upstream: "http://192.168.95.100:4000/", host: "test.local"
2018/08/02 11:40:29 [error] 6#6: *10 upstream prematurely closed connection while reading response header from upstream, client: 192.168.95.1, server: test.local, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.95.100:4000/favicon.ico", host: "test.local", referrer: "http://test.local/"

```

 ![Request%20Error%202018-08-02%2014-45-13](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/2X/2/28320a7a64029f5cec09e1e5ffd60e0d58492789.png)

---

<div class="post-metadata">

**Author:** ![royrogers](https://avatars.discourse-cdn.com/v4/letter/r/9f8e36/32.png) [@royrogers](https://community.localwp.com/u/royrogers)\
**Post date:** [August 3, 2018, 3:06pm UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/2 "2018-08-03T15:06:23Z")

</div>

HI there,

In case you are using NGINX. There is a BUG on LOCAL 2.3.2 version - nginx/ site.conf file

line 19: include includes/wordpress.conf;

when it should be : include includes/wordpress-multi.conf;

This will fix the 502 Error Request on nginx.

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [August 3, 2018, 7:32pm UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/3 "2018-08-03T19:32:19Z")

</div>

@prodev,

What Environment settings did you select?

* * *

@royrogers,

`wordpress-multi.conf` should only be used if you’re using multisite.

Does changing it to `wordpress-multi.conf` address issues when not running multisite?

---

<div class="post-metadata">

**Author:** ![royrogers](https://avatars.discourse-cdn.com/v4/letter/r/9f8e36/32.png) [@royrogers](https://community.localwp.com/u/royrogers)\
**Post date:** [August 3, 2018, 9:19pm UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/4 "2018-08-03T21:19:32Z")

</div>

Thanks for your reply.

Yes. It address the issues for multisite and if it is a single site should change to:

```
                   includes/wordpress-single.conf;

```

includes/wordpress.conf; --\> it doesn’t work.

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [August 3, 2018, 9:31pm UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/5 "2018-08-03T21:31:44Z")

</div>

Got it, thanks! I replied here: [Version 2.3.2. ERROR 502 on NGINX. WINDOWS 10. BUG FIXED!](https://local.getflywheel.com/community/t/version-2-3-2-error-502-on-nginx-windows-10-bug-fixed/7604/2?u=clay)

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 25, 2020, 6:35pm UTC](https://community.localwp.com/t/local-2-3-2-not-working-if-changing-default-settings/7591/6 "2020-08-25T18:35:03Z")

</div>

Closed on August 25, 2020, 6:35pm UTC


