NginxProxyManager / NginxProxyManager/nginx-proxy-manager

1024 worker_connections are not enough

Open
#2,166 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug
Over the past few days, I am increasingly getting dropouts when accessing my proxied services. I have tried restarting the container which does seem to temporarily alleviate the issue but after 40-50 mins I start getting dropouts again. The Error logs are full of entries like:
1024 worker_connections are not enough

The issue only occurs with comms via NPM, If I direct access the services, there are no dropouts.

Nginx Proxy Manager Version
v2.9.18

To Reproduce
Steps to reproduce the behavior:

  1. Spin up container
  2. Have it server a few *Arrr sites + Home assistant etc. Total 8 Proxy hosts + 1 Stream for Torrents

Expected behavior
Is there a way to tune this? Provide more worker connections?

Screenshots
Services are monitored via their domain name/NPM and via local IP. Only the proxied hosts experience drops in comms. Direct monitoring of the hosted services via direct IP shows no drops from the individual hosts.
image

Operating System
Docker running on a Qnap nas via Docker-Compose

Additional context
Compose file:

version: '3.7'
services:
  nginx-proxy-manager:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: npm
    restart: always
    environment:
      - PUID=1002 # set to UID of your user
      - PGID=100  # set to GID of your user
      - TZ=Australia/Sydney #Set TimeZone
    volumes:
      - /share/CACHEDEV1_DATA/SSD/Docker/NginxProxyManager/data:/data # Config Dir
      - /share/CACHEDEV1_DATA/SSD/Docker/NginxProxyManager/etc/.letsencrypt:/etc/letsencrypt # Config Dir
    ports:
      - '80:80' # <Host Port>:<Container Port> Web Service
      - '443:443' # <Host Port>:<Container Port> Web Service
      - '82:81' # <Host Port>:<Container Port> Dashboard
    networks:
      dockerlan-static:
        ipv4_address: 192.168.0.9
    healthcheck:
      test: ["CMD", "/bin/check-health"]
      interval: 10s
      timeout: 3s

networks:
  dockerlan-static:
    external: true

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Docker Compose service and inspect the Nginx configuration inside the jc21/nginx-proxy-manager:latest container, focusing on the worker_connections limit and the reported error logs. Reproduce the dropouts with the listed proxy hosts and stream, then verify that a configuration change prevents the errors without disrupting proxied services.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, nginx
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.