[GH-ISSUE #4157] Error 503 - Service temporarily unavailable #2697

Open
opened 2026-02-26 07:36:30 +03:00 by kerem · 8 comments
Owner

Originally created by @a1hoxha on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4157

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
I have configured NPM in the correct way when it comes to port & traffic forwarding. When I use a domain with no traffic, it works well with no issue. When I use a domain with a lot of traffic on it (700-800 clients simultaneously), I get Error 503. I am using the same domain directly without passing to the proxy, and it is working perfectly fine. When I use Proxy and I keep refreshing the website, 1/4 of times works, 3/4 of times gives error 503. I use this to hide the IP of the streaming server.

""I have checked the logs and I am getting:

183#183: *127384 connect() failed (111: Connection r
efused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: 0.0.0.0:8080,
upstream: "xx.xx.xxx.xx:8080", bytes from/to client:0/0, bytes from/to upstre
am:0/0""

Is there any way I can increase the load that it can handle? I want to set it to have no limits on traffic handling. Is there any way to do so?

Nginx Proxy Manager Version

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Screenshots

Operating System

Additional context

Originally created by @a1hoxha on GitHub (Nov 13, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4157 **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** I have configured NPM in the correct way when it comes to port & traffic forwarding. When I use a domain with no traffic, it works well with no issue. When I use a domain with a lot of traffic on it (700-800 clients simultaneously), I get Error 503. I am using the same domain directly without passing to the proxy, and it is working perfectly fine. When I use Proxy and I keep refreshing the website, 1/4 of times works, 3/4 of times gives error 503. I use this to hide the IP of the streaming server. ""I have checked the logs and I am getting: 183#183: *127384 connect() failed (111: Connection r efused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: 0.0.0.0:8080, upstream: "xx.xx.xxx.xx:8080", bytes from/to client:0/0, bytes from/to upstre am:0/0"" Is there any way I can increase the load that it can handle? I want to set it to have no limits on traffic handling. Is there any way to do so? **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
Author
Owner

@mynxg commented on GitHub (Nov 13, 2024):

+1

<!-- gh-comment-id:2474120959 --> @mynxg commented on GitHub (Nov 13, 2024): +1
Author
Owner

@mynxg commented on GitHub (Nov 13, 2024):

image

<!-- gh-comment-id:2474124505 --> @mynxg commented on GitHub (Nov 13, 2024): ![image](https://github.com/user-attachments/assets/a3dc80fa-c6c9-48a5-8cfd-66fd39a0391a)
Author
Owner

@mynxg commented on GitHub (Nov 13, 2024):

image

2024/11/13 16:49:28 [error] 173#173: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 222..., server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "117...:8888", referrer: "http://117...**:8888/login"

<!-- gh-comment-id:2474153905 --> @mynxg commented on GitHub (Nov 13, 2024): > ![image](https://private-user-images.githubusercontent.com/77525803/385849599-a3dc80fa-c6c9-48a5-8cfd-66fd39a0391a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE1MTYxNjMsIm5iZiI6MTczMTUxNTg2MywicGF0aCI6Ii83NzUyNTgwMy8zODU4NDk1OTktYTNkYzgwZmEtYzZjOS00OGE1LThjZmQtNjZmZDM5YTAzOTFhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTEzVDE2Mzc0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFmMmY4OWRlNzkzYzA2Mjk0Mjg2MmI1YWZiN2QxNDgyNTcxZDkxY2Q0YmM4YmNjODMwZTQwMWQ3YWUzNTQ3ODcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.J8slSa2YuZypgvs-S93EjmBjAhHCNcw8P3uUVQKyxzw) 2024/11/13 16:49:28 [error] 173#173: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 222..., server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "117...:8888", referrer: "[http://117.**.**.**:8888/login](http://117.%2A%2A.%2A%2A.%2A%2A:8888/login)"
Author
Owner

@mynxg commented on GitHub (Nov 13, 2024):

image

2024/11/13 16:49:28 [error] 173#173: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 222..., server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "117...:8888", referrer: "http://117...**:8888/login"

View the logs of Docker containers.
[11/13/2024] [4:48:53 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite
[11/13/2024] [4:48:53 PM] [Global ] › ℹ info Creating a new JWT key pair...
[11/13/2024] [4:48:57 PM] [Global ] › ℹ info Wrote JWT key pair to config file: /data/keys.json
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info Current database version: none
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] auth Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] user Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] user_permission Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] proxy_host Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] redirection_host Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] dead_host Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] stream Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] access_list Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] certificate Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] access_list_auth Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] audit_log Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [websockets] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [websockets] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_host] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_host] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] redirection_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] dead_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_scheme] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_scheme] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] redirection_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] dead_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] stream Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [custom_locations] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [custom_locations] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] proxy_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] redirection_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] dead_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [settings] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [settings] setting Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] access_list_client Table created
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] access_list Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client_fix] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client_fix] access_list Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [pass_auth] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [pass_auth] access_list Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_scheme] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_scheme] redirection_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_status_code] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_status_code] redirection_host Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up...
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] stream Table altered
[11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up...
[11/13/2024] [4:48:58 PM] [Setup ] › ℹ info Creating a new user: admin@example.com with password: changeme
[11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Initial admin setup completed
[11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Default settings added
[11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Logrotate Timer initialized
[11/13/2024] [4:48:59 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
[11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Logrotate completed.
[11/13/2024] [4:48:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[11/13/2024] [4:48:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json

An error is reported when it reaches this point.

<!-- gh-comment-id:2474206588 --> @mynxg commented on GitHub (Nov 13, 2024): > > ![image](https://private-user-images.githubusercontent.com/77525803/385849599-a3dc80fa-c6c9-48a5-8cfd-66fd39a0391a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE1MTYxNjMsIm5iZiI6MTczMTUxNTg2MywicGF0aCI6Ii83NzUyNTgwMy8zODU4NDk1OTktYTNkYzgwZmEtYzZjOS00OGE1LThjZmQtNjZmZDM5YTAzOTFhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDExMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMTEzVDE2Mzc0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFmMmY4OWRlNzkzYzA2Mjk0Mjg2MmI1YWZiN2QxNDgyNTcxZDkxY2Q0YmM4YmNjODMwZTQwMWQ3YWUzNTQ3ODcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.J8slSa2YuZypgvs-S93EjmBjAhHCNcw8P3uUVQKyxzw) > 2024/11/13 16:49:28 [error] 173#173: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 222.**.**.**, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "117.**.**.**:8888", referrer: "http://117.**.**.**:8888/login" View the logs of Docker containers. [11/13/2024] [4:48:53 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [11/13/2024] [4:48:53 PM] [Global ] › ℹ info Creating a new JWT key pair... [11/13/2024] [4:48:57 PM] [Global ] › ℹ info Wrote JWT key pair to config file: /data/keys.json [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info Current database version: none [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] auth Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] user Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] user_permission Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] proxy_host Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] redirection_host Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] dead_host Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] stream Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] access_list Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] certificate Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] access_list_auth Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [initial-schema] audit_log Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [websockets] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [websockets] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_host] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] redirection_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [http2_support] dead_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_scheme] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [forward_scheme] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] redirection_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] dead_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [disabled] stream Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [custom_locations] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [custom_locations] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] proxy_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] redirection_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [hsts] dead_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [settings] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [settings] setting Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] access_list_client Table created [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client] access_list Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client_fix] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [access_list_client_fix] access_list Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [pass_auth] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [pass_auth] access_list Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_scheme] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_scheme] redirection_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_status_code] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [redirection_status_code] redirection_host Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] stream Table altered [11/13/2024] [4:48:58 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [11/13/2024] [4:48:58 PM] [Setup ] › ℹ info Creating a new user: admin@example.com with password: changeme [11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Initial admin setup completed [11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Default settings added [11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Logrotate Timer initialized [11/13/2024] [4:48:59 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [11/13/2024] [4:48:59 PM] [Setup ] › ℹ info Logrotate completed. [11/13/2024] [4:48:59 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [11/13/2024] [4:48:59 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json An error is reported when it reaches this point.
Author
Owner

@mynxg commented on GitHub (Nov 14, 2024):

image
Checked the reason: Part of it is an issue with the IP range. It's more appropriate to change it to the way of using environment variables.

<!-- gh-comment-id:2475831675 --> @mynxg commented on GitHub (Nov 14, 2024): ![image](https://github.com/user-attachments/assets/a9260f10-8694-44d8-8991-d0c4ae08f870) Checked the reason: Part of it is an issue with the IP range. It's more appropriate to change it to the way of using environment variables.
Author
Owner

@mynxg commented on GitHub (Nov 14, 2024):

The bug has been reproduced. The reason is that the mapping path in Docker is too long. It can be fixed by shortening the path a bit.

It has been resolved.

#start:docker compose -f docker-compose-nginx-proxy-manager.yml up -d
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80' 
      - '81:81'  
      - '443:443' 
    volumes:
      - "/root/docker-data/npm/data:/data"
      - "/root/docker-data/npm/letsencrypt:/etc/letsencrypt"
<!-- gh-comment-id:2475909361 --> @mynxg commented on GitHub (Nov 14, 2024): The bug has been reproduced. The reason is that the mapping path in Docker is too long. It can be fixed by shortening the path a bit. It has been resolved. ``` #start:docker compose -f docker-compose-nginx-proxy-manager.yml up -d services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - "/root/docker-data/npm/data:/data" - "/root/docker-data/npm/letsencrypt:/etc/letsencrypt" ```
Author
Owner

@WangGuan11 commented on GitHub (May 19, 2025):

该 bug 已复现,原因是 Docker 中的映射路径过长,可以通过稍微缩短路径来解决。

已解决。

#start:docker compose -f docker-compose-nginx-proxy-manager.yml up -d
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80' 
      - '81:81'  
      - '443:443' 
    volumes:
      - "/root/docker-data/npm/data:/data"
      - "/root/docker-data/npm/letsencrypt:/etc/letsencrypt"

good,It's a problem with the mapping path being too long. If it's too short, it'll be fine immediately. Don't worry about any other databases or anything else

<!-- gh-comment-id:2890419295 --> @WangGuan11 commented on GitHub (May 19, 2025): > 该 bug 已复现,原因是 Docker 中的映射路径过长,可以通过稍微缩短路径来解决。 > > 已解决。 > > ``` > #start:docker compose -f docker-compose-nginx-proxy-manager.yml up -d > services: > app: > image: 'jc21/nginx-proxy-manager:latest' > restart: unless-stopped > ports: > - '80:80' > - '81:81' > - '443:443' > volumes: > - "/root/docker-data/npm/data:/data" > - "/root/docker-data/npm/letsencrypt:/etc/letsencrypt" > ``` good,It's a problem with the mapping path being too long. If it's too short, it'll be fine immediately. Don't worry about any other databases or anything else
Author
Owner

@github-actions[bot] commented on GitHub (Nov 19, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3550353977 --> @github-actions[bot] commented on GitHub (Nov 19, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#2697
No description provided.