mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #5137] Questions #3125
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#3125
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 @Ferrox12 on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5137
Hi,
is there a page that explains every options available when I create a new record? For example Cache assets, Websockets support...
@piotrfx commented on GitHub (Jan 13, 2026):
Hi there! . Is it answering well enough:
While the official documentation gives a high-level overview, many of these toggles correspond directly to specific Nginx directives. Here is a quick breakdown of what the most common ones do:
Cache Assets: Enables proxy_cache. Nginx will store static files (images, CSS, JS) from your upstream server locally. Use this for static sites to speed up load times, but keep it off for dynamic dashboards.
Websockets Support: This is crucial for modern 'real-time' apps. It adds the Upgrade and Connection headers. If you use apps like Home Assistant, Plex, or any live chat, you’ll likely need this ON.
Block Common Exploits: Adds security rules to filter out common 'bad' traffic like SQL injections or malicious bots. It’s generally recommended to keep this ON.
HSTS Enabled: Tells the browser to force an HTTPS connection for a specified time. It's great for security, but be careful: once a browser sees this, it will refuse to connect via plain HTTP until the timer expires.
HTTP/2 Support: Allows the more efficient binary version of the HTTP protocol. This requires SSL to be enabled and generally improves loading performance.
Since NPM is essentially a UI wrapper for Nginx, a great way to learn more is to check the Nginx Reverse Proxy Documentation. You can also see the exact config NPM generates by clicking the three dots on your Proxy Host and selecting 'View Config'.
P.s: I didn't know the answer, I've asked Gemini, and you can verify ;) on your own next. Please reply if that answers your question :).
@Ferrox12 commented on GitHub (Jan 16, 2026):
#5180