[GH-ISSUE #2794] CPU Cores @ 100% for nginx worker past 2.9.19 #1919

Closed
opened 2026-02-26 07:33:15 +03:00 by kerem · 7 comments
Owner

Originally created by @gadgetusaf on GitHub (Apr 2, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2794

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • No
  • Have you searched for similar issues (both open and closed)?
    • Yes

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

Originally created by @gadgetusaf on GitHub (Apr 2, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2794 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - No - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- Upgrading past 2.9.19 CPU cores get pegged at 100% --> **Nginx Proxy Manager Version** <!-- After 2.9.19 --> **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** <!-- Cores not to peg --> **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Ubuntu 22.04 as the Docker host--> **Additional context** <!-- When I upgrade from 2.9.19 to any newer version all cores in the docker host become 100% consumed with the nginx worker process, I am able to revert back to 2.9.19 and usage is back to normal -->
kerem 2026-02-26 07:33:15 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@theraw commented on GitHub (Apr 3, 2023):

do you see any type of error on your logs?

<!-- gh-comment-id:1493672813 --> @theraw commented on GitHub (Apr 3, 2023): do you see any type of error on your logs?
Author
Owner

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

<!-- gh-comment-id:1494972425 --> @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.
Author
Owner

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

<!-- gh-comment-id:1551282891 --> @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.
Author
Owner

@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

<!-- gh-comment-id:1551306757 --> @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
Author
Owner

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

<!-- gh-comment-id:1562650516 --> @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.
Author
Owner

@javito1081 commented on GitHub (May 2, 2025):

did ya guys fi

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

    • Yes
  • Are you sure you're not using someone else's docker image?

    • No
  • Have you searched for similar issues (both open and closed)?

    • Yes

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

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

<!-- gh-comment-id:2846101753 --> @javito1081 commented on GitHub (May 2, 2025): did ya guys fi > **Checklist** > > * Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? > > * Yes > * Are you sure you're not using someone else's docker image? > > * No > * Have you searched for similar issues (both open and closed)? > > * Yes > > **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** 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
Author
Owner

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

<!-- gh-comment-id:3243123925 --> @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.
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#1919
No description provided.