Local 2.3.2 not working if changing default settings

Support
1 
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
Request%20Error%202018-08-02%2014-45-13866×501 24.4 KB

2

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.

3

@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?

4

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.

5

Got it, thanks! I replied here: Version 2.3.2. ERROR 502 on NGINX. WINDOWS 10. BUG FIXED!