[GH-ISSUE #1888] Implement configurations to avoid top 10 mistakes #1379

Closed
opened 2026-02-26 07:30:44 +03:00 by kerem · 2 comments
Owner

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).

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](https://www.nginx.com/blog/avoiding-top-10-nginx-configuration-mistakes/#keepalive). 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).
kerem 2026-02-26 07:30:44 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 23, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1960626162 --> @github-actions[bot] commented on GitHub (Feb 23, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 7, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2781853652 --> @github-actions[bot] commented on GitHub (Apr 7, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1379
No description provided.