mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #2794] CPU Cores @ 100% for nginx worker past 2.9.19 #1919
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#1919
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 @gadgetusaf on GitHub (Apr 2, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2794
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Nginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
I upgraded the docker container, each release past 2.9.19 all cores peg to 100 with in a few min.
Expected behavior
Screenshots
Operating System
Additional context
@theraw commented on GitHub (Apr 3, 2023):
do you see any type of error on your logs?
@gadgetusaf commented on GitHub (Apr 3, 2023):
I see noting abnormail in the logs though the system becomes unstable quite quickly as the Nginx worker(s) onper core each consume the cpu.
I am thinking its a bug and I wa working on rebuilding the new container. But I can help test before I decom the server if it is useful.
@gadgetusaf commented on GitHub (May 17, 2023):
I just rebuilt and am facing the same Issue.
Are there any recomendations to get usefull information to troubleshoot.
@gadgetusaf commented on GitHub (May 17, 2023):
proxy_max_temp_file_size 0; client_body_buffer_size 0; client_max_body_size 0; proxy_buffering off; proxy_request_buffering off;This is the custom config on a number of sites I am running
@gadgetusaf commented on GitHub (May 25, 2023):
I uncovered the issues as I thought it was with an advanced config. Once I cleaned up a few issues there I was able to upgrade without issue.
@javito1081 commented on GitHub (May 2, 2025):
did ya guys fi
did ya guys find a fix for this? cause im experiencing this issue for a few days now, and i havent found a fix yet
@Kieranwest commented on GitHub (Sep 1, 2025):
Getting similar issues. At first thought I was getting spammed with bots but with no external rules forwarding I'm still seeing maxed CPU usage.