mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1342] NPM Runs out of memory #1067
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#1067
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 @ghost on GitHub (Aug 22, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1342
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug

I am running Nginx Proxy Manager on one of my proxmox servers. The VM is running Ubuntu server 20.04 and has allocated 8 vcpus and 24gib of ram (was trying to fix the out of memory issue by upping the ram but that didn't help). I am using docker compose to run NPM and that is up to date as well however after an hour of the system running it complete hard crashes my VM and fills up the console with a bunch of errors.
I have tried using different versions of ubuntu server but really with no luck.
Nginx Proxy Manager Version
2.9.7
@chaptergy commented on GitHub (Oct 25, 2021):
Are you sure this is an npm issue? npm is only a frontend to generate nginx configs, so it something is running out of memory, it has to be nginx. What proxess uses up all that memory? I've not yet really heard about any issues similar to this.
@github-actions[bot] commented on GitHub (Mar 5, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 18, 2025):
Issue was closed due to inactivity.