Add "fastcgi.logging = Off" to fpm defaults#1360
Merged
yosifkit merged 1 commit intodocker-library:masterfrom Jan 4, 2023
Merged
Add "fastcgi.logging = Off" to fpm defaults#1360yosifkit merged 1 commit intodocker-library:masterfrom
yosifkit merged 1 commit intodocker-library:masterfrom
Conversation
This should (finally) fix errors between FPM and NGINX.
|
FTR, since I wrote the comment some time passed 😅 and in the meantime this is also running in prod for quite some time with no issues (though I'm sadly still on 7.4 …). |
docker-library-bot
added a commit
to docker-library-bot/official-images
that referenced
this pull request
Jan 5, 2023
Changes: - docker-library/php@258caef: Merge pull request docker-library/php#1360 from infosiftr/fastcgi.logging - docker-library/php@f8c7370: Add "fastcgi.logging = Off" to fpm defaults - docker-library/php@07ddc2e: Update generated README
docker-library-bot
added a commit
to docker-library-bot/official-images
that referenced
this pull request
Jan 5, 2023
Changes: - docker-library/php@58e2e42: Update 8.2-rc - docker-library/php@fdf3f68: Update 8.2 to 8.2.1 - docker-library/php@8ca1f9e: Update 8.1-rc - docker-library/php@a4b05a8: Update 8.1 to 8.1.14 - docker-library/php@258caef: Merge pull request docker-library/php#1360 from infosiftr/fastcgi.logging - docker-library/php@f8c7370: Add "fastcgi.logging = Off" to fpm defaults - docker-library/php@07ddc2e: Update generated README
docker-library-bot
added a commit
to docker-library-bot/official-images
that referenced
this pull request
Jan 5, 2023
Changes: - docker-library/php@55fb151: Update 8.0-rc - docker-library/php@af4fd9a: Update 8.0 to 8.0.27 - docker-library/php@58e2e42: Update 8.2-rc - docker-library/php@fdf3f68: Update 8.2 to 8.2.1 - docker-library/php@8ca1f9e: Update 8.1-rc - docker-library/php@a4b05a8: Update 8.1 to 8.1.14 - docker-library/php@258caef: Merge pull request docker-library/php#1360 from infosiftr/fastcgi.logging - docker-library/php@f8c7370: Add "fastcgi.logging = Off" to fpm defaults - docker-library/php@07ddc2e: Update generated README
Alkarex
added a commit
to Alkarex/rss-bridge
that referenced
this pull request
Jan 4, 2024
Mistake from RSS-Bridge#3500 Wrong file extension: should have been `.ini` and not `.conf` otherwise it has no effect. See docker-library/php#1360 and docker-library/php#878 (comment)
dvikan
pushed a commit
to RSS-Bridge/rss-bridge
that referenced
this pull request
Jan 5, 2024
Mistake from #3500 Wrong file extension: should have been `.ini` and not `.conf` otherwise it has no effect. See docker-library/php#1360 and docker-library/php#878 (comment)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should (finally) fix errors between FPM and NGINX (thanks @mfn! sorry for the enormous delay in actually doing something 🙇).
Closes #878
I don't think we should merge this right away (especially not right before/during folks being off for the holidays), but I think this is probably the correct "final" answer for the NGINX 502 issues.