get internal server error for /posts about wp-api

[rmccue]

Do you have pretty permalinks enabled? Did you install this as a plugin, or did you use the (not recommended) "As Part of Core" installation?

[heirenton]

I am experiencing same thing. wp-json responds, but /posts does not work. Ubuntu VPS & NGINX with pretty permalinks enabled.

[rednaxus]

plugin, and yes i have pretty permalinks

[afurculita]

@rednaxus maybe try to flush your rewrite rules?

[rmccue]

I thought this was caused by nginx's pathinfo rules, but that appears to break /wp-json.php as well for me. I'm not sure exactly what could be causing this.

[wkw]

We've run into some issues in situations where nginx is proxy for apache, both on our internal dev servers, and at WPEngine.com. It may be related to the quantity of "Link:" headers which are sent. Here's a representative message from the nginx error log:

[error] 9250#0: *88815 upstream sent too big header while reading response header from upstream, client: xx.xx.xx.xx, server: redacted.com, request: "GET /wp-json.php/posts?filter%5Bposts_per_page%5D=-1&type=case_study HTTP/1.1", upstream: "http://10.32.2.20:80/wp-json.php/posts?filter%5Bposts_per_page%5D=-1&type=case_study", host: "-redacted-", referrer: "http://redacted.com/what-we-do/interactive-map/"

We got around this on internal environment with some nginx mods:
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;

But have since removed those when we ran into the issue at wpengine, and couldn't tweak nginx. Instead, we've commented out the line of source code which sends the "Link:" headers (for expediency on the project).

[rmccue]

We changed the API URLs to /wp-json/ which should fix the main issue here.

@wkw That's incredibly strange; I'll look into it. If you can still replicate, please open a new issue. :)