Tests: Fix 502 Errors on Uncode Theme Tests #972
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Tests against Uncode's theme started returning a 502 bad gateway in nginx, when run by GitHub actions (locally, these tests pass):

Configuring the GitHub action to upload
/var/log/nginx/error.logas an artifact on failure revealed:2025/12/04 04:47:02 [error] 2700#2700: *45 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "POST /post-2-title/?convertkit_login=1 HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "127.0.0.1", referrer: "http://127.0.0.1/post-2-title/?ck-cache-bust=0.11952200%201764823621"This PR resolves by increasing the buffer size in nginx, and includes uploading nginx's
error.logto the GitHub action artifacts, should tests in the future fail.Checklist