[GH-ISSUE #5085] Management interface not working (The API is not healthy / 502 Bad Gateway) #3101

New issue

Open

opened 2026-02-26 07:37:51 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:37:51 +03:00

Owner

Originally created by @JakobTewes on GitHub (Dec 15, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5085

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
DNS seems not to work inside the docker image without manual configuration.
Using docker-compose. Adding the dns directive fixes the thing.

services:
  nginx-proxy-manager:
    image: jc21/nginx-proxy-manager:latest
    container_name: nginx-proxy-manager
    environment:
      DISABLE_IPV6: 'true'
      SKIP_CERTBOT_OWNERSHIP: 'true'
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /mnt/nfs-1/nginx-proxy-manager/data:/data
      - /mnt/nfs-1/letsencrypt:/etc/letsencrypt
    dns:
      - 192.168.177.1

Nginx Proxy Manager Version
2.13.5 (since at least 2.13.2)

To Reproduce
Steps to reproduce the behavior:

Deploy via docker-compose
Have no dns server specified
Access management web interface
Management web interface not working
Already configured reverse config works

Expected behavior
Web interface works without manual dns specification

Screenshots
n.a.

Operating System
Ubuntu 24.04.3 LTS

Additional context
This issue led me the way https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3305

Originally created by @JakobTewes on GitHub (Dec 15, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5085 **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** DNS seems not to work inside the docker image without manual configuration. Using docker-compose. Adding the dns directive fixes the thing. ``` services: nginx-proxy-manager: image: jc21/nginx-proxy-manager:latest container_name: nginx-proxy-manager environment: DISABLE_IPV6: 'true' SKIP_CERTBOT_OWNERSHIP: 'true' volumes: - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/var/run/docker.sock:ro - /mnt/nfs-1/nginx-proxy-manager/data:/data - /mnt/nfs-1/letsencrypt:/etc/letsencrypt dns: - 192.168.177.1 ``` **Nginx Proxy Manager Version** 2.13.5 (since at least 2.13.2) **To Reproduce** Steps to reproduce the behavior: 1. Deploy via docker-compose 2. Have no dns server specified 3. Access management web interface 4. Management web interface not working 5. Already configured reverse config works **Expected behavior** Web interface works without manual dns specification **Screenshots** n.a. **Operating System** Ubuntu 24.04.3 LTS **Additional context** This issue led me the way https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3305

kerem added the

bug

label

2026-02-26 07:37:51 +03:00

kerem commented

2026-02-26 07:37:52 +03:00

Author

Owner

@zabit82 commented on GitHub (Dec 19, 2025):

I solved this problem using the parameter IP_RANGES_FETCH_ENABLED: 'false'

@zabit82 commented on GitHub (Dec 19, 2025): I solved this problem using the parameter `IP_RANGES_FETCH_ENABLED: 'false'`

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#3101

No description provided.

Rows
Columns