Why does SlickStack use 32 32k value for Nginx fastcgi_buffers
- This topic is empty.
April 2024 only! Join our Discord free of charge.
In the ss-config
we had the default value 32 32k
and couldn’t remember why… well, after uncommenting the FastCGI buffers settings this week to allow users to properly customize the settings, we found out why.
It’s because if you are using a fastcgi_busy_buffers_size
value of 256k
which is recommended then it’s not going to be compatible with 16 16k
There are lots and lots of threads and tutorials recommending 16 16k
to avoid upstream errors in Nginx but these fail to take into account busy buffers eg.
https://stackoverflow.com/questions/19539501/nginx-502-bad-gateway-solved-by-increasing-buffer-why
one of those cases where people are copy and pasting the same (bad) settings in 1000 different tutorials for several years lol
Friends, the time has come for us to ask for your financial support. After 5+ years of (growing) expenses, and taking time away from consulting and services, we must start generating donations in order to continue this level of rapid project development. Please consider donating, so that we can keep SlickStack free and open source. Thank you! 🙏 😍
We champion core values like free speech, transparency, and portability, and welcome anyone else who does too.
Here is a non-exhaustive list of plugins, themes, and other services that we recommend checking out.
Every stack script and server deployment platform is a bit different, so check to see how SlickStack compares.
Subscribe to our free newsletter to receive occassional updates, we respect your privacy and do not sell your information.
Here’s some of the incredible performance features you can expect after launching your SlickStack cloud VPS.
If you are wondering what specific problems SlickStack can help solve, browse some of the solutions below.
In lieu of donations, please show your support by mentioning SlickStack on your blog or write a review. Thank you!