Closed dnkmdg closed 1 year ago
trippo
commented
1 year ago I have the same problem... a route gives me a 502 Bad Gateway error...
If I remove a component and put its code directly inside the page content all work fine...
But this configuration don't solve the problem...
proxy_buffer_size 4096k;
proxy_buffers 128 4096k;
proxy_busy_buffers_size 4096k;If I use the same component on other pages works fine!
How can I solve this problem?
trippo
commented
1 year ago I solve with
fastcgi_buffers 128 4k;
fastcgi_buffer_size 12k;
fastcgi_busy_buffers_size 16k;
jessarcher
commented
1 year ago Thanks for sharing your insights! Going to close this one but feel free to continue the discussion :slightly_smiling_face:
FerVillanuevas
commented
9 months ago The proxy solution works fine for me with Octane
proxy_buffer_size 4096k; proxy_buffers 128 4096k; proxy_busy_buffers_size 4096k;
thanks @trippo
rstefanic
commented
6 months ago This was a life safer. Thank you @dnkmdg. I have been banging my head against a wall trying to fix it for a couple of days now. In my case, we weren't getting a 502 error. The response was a blank page with no content and a 200 status response. The HTTP message body was 0 bytes every time.
It wasn't until I added an extra header that I got the 502 error and then stumbled upon this post. I checked the header size that page was returning, and the header was 4.6kb! Our machine running the Inertia application had the default fastcgi_buffer_size of 4k (which is the NGINX default taken the host machine's page size). Bumping it up to 8k is what did the trick for us and everything's working smoothly!
fastcgi_buffer_size 8k;
GDanielRG
commented
3 months ago This was a life safer. Thank you @dnkmdg. I have been banging my head against a wall trying to fix it for a couple of days now. In my case, we weren't getting a 502 error. The response was a blank page with no content and a 200 status response. The HTTP message body was 0 bytes every time.
It wasn't until I added an extra header that I got the 502 error and then stumbled upon this post. I checked the header size that page was returning, and the header was 4.6kb! Our machine running the Inertia application had the default
fastcgi_buffer_sizeof 4k (which is the NGINX default taken the host machine's page size). Bumping it up to 8k is what did the trick for us and everything's working smoothly!fastcgi_buffer_size 8k;
Was having random Nginx errors, the fastest way I found how to replicate it was going to a specific page and just reloading and i would get the nginx error. So its different if inertia loads the page initially with html or just sends the json on subsequent requests. Either way this fixed it and you are a savior for me and 2 of my customers. Thanks!
aigletter
commented
1 month ago It was helpful for me. I needed both options. I used Nginx Proxy Manager and it was solved with fastcgi* directives for nginx of my application and proxy* directives for Nginx Proxy Manager. Thank you all very much!
Opening this issue to aid others running into a somewhat bizarre issue, might also be cause for some documentation.
When applying the
@inertiadirective the yielded result contains both the page template and links for all dynamically fetched modules and styles. Recently we started seeing502 Bad Gatewayerrors when navigating directly to certain routes in our app, but not when arriving at the same routes from programmatic navigation ie. SPA navigation. After some debugging we found that all of the rendered<script>tags caused response header sectionlinksto blow up, thereby causing nginx to fail with a 502.The solution for this is to increase nginx buffers:
A single response could easily look like this, where the "link" section alone is too much for the standard configuration of nginx to handle.