502 Bad Gateway on WordCamp.org Requests

I’m seeing 502 Bad Gateway errors on certain WordCamp.org requests. For example, requesting 30 posts from the JSON API works fine, but requesting 40 doesn’t.

I’ve also seen it happen when connecting Jetpack to WPCOM, but that’s intermittent and I haven’t noticed a pattern yet.

We have use cases where APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. clients will need 75-100 posts. They could make multiple requests, but that would add additional overhead and slow things down on their end.

The nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. logs say, upstream sent too big header while reading response header from upstream, and it sounds increasing the buffer sizes may be all that’s needed to fix it.

#nginx, #wordcamp-org