mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1888] Implement configurations to avoid top 10 mistakes #1379
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1379
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @johncadengo on GitHub (Feb 24, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1888
I recently came across this blog post from Nginx: Avoiding the Top 10 NGINX Configuration Mistakes.
There are several here that the default configuration of NPM does not implement. Examples from my understanding:
[3] Not Enabling Keepalive Connections to Upstream Servers
[10] Not Taking Advantage of Upstream Groups
I'm not sure if the others could be addressed or are already addressed, but it seems 3 and 10 are interesting example of how we can update the default configurations to improve performance and avoid "mistakes" (according to Nginx).
@github-actions[bot] commented on GitHub (Feb 23, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 7, 2025):
Issue was closed due to inactivity.