mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #3587] Nginx Proxy Manager - Memory Usage unclear #2377
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#2377
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 @mpi42 on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3587
Nginx Proxy Manager - Memory Usage unclear
I have an Ngnix Proxy Manager with 100 proxy hosts running on an ubuntu with 32GB Ram. However, the RAM usage is constantly increasing (and running out).
i see differences between top, free -m and docker stats that i can't explain. nothing else is running on the machine except the two containers for nginx proxy manager.
Some of the proxy hosts have chaching enabled, can this contribute to higher ram consumption?
Here are the configs for a proxy host:
in the logs i can't find anything conspicuous so far but i only see the access.logs now
can I start somewhere else here or am I missing something?
many thanks
@kingp0dd commented on GitHub (Mar 2, 2024):
mine is also spiking up when accessing an internal server like streaming from jellyfin.
jellyfin server is proxied through npm like this:
jellyfin.domain.com -> 192.168.0.2
@github-actions[bot] commented on GitHub (Sep 3, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Sep 5, 2025):
Issue was closed due to inactivity.