starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #2149] Fails to honour http/https proxy environment settings when fetching IP Ranges #1542

New issue
Closed
opened 2026-02-26 07:31:29 +03:00 by kerem · 9 comments
kerem commented 2026-02-26 07:31:29 +03:00
Owner
Copy link

Originally created by @nigelm on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2149

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
When running on a firewalled network with internet access via a proxy, the initial startup runs a process to fetch IP ranges of external services:-

[IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[IP Ranges] › ✖  error     connect ETIMEDOUT 143.204.176.42:443

We have https_proxy/HTTP_PROXY/http_proxy/HTTP_PROXY and no_proxy/NO_PROXY environment variables set up - and this allows the Lets Encrypt services to work (with DNS solvers).

However this fetch from Amazon causes the management startup to pause for a good 2 minutes.

Could this fetch be changed to honour the proxy settings.

Nginx Proxy Manager Version

Version: 2.9.18

Originally created by @nigelm on GitHub (Jul 8, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2149 **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** When running on a firewalled network with internet access via a proxy, the initial startup runs a process to fetch IP ranges of external services:- ``` [IP Ranges] › ℹ info Fetching IP Ranges from online services... [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [IP Ranges] › ✖ error connect ETIMEDOUT 143.204.176.42:443 ``` We have `https_proxy`/`HTTP_PROXY`/`http_proxy`/`HTTP_PROXY` and `no_proxy`/`NO_PROXY` environment variables set up - and this allows the Lets Encrypt services to work (with DNS solvers). However this fetch from Amazon causes the management startup to pause for a good 2 minutes. Could this fetch be changed to honour the proxy settings. **Nginx Proxy Manager Version** Version: 2.9.18
kerem 2026-02-26 07:31:29 +03:00
  • closed this issue
  • added the
    stale
    bug
         labels
kerem commented 2026-02-26 07:31:29 +03:00
Author
Owner
Copy link

@vcutrona commented on GitHub (Oct 24, 2022):

same here
We're experiencing exact the same on our firewalled company server.

<!-- gh-comment-id:1288720884 --> @vcutrona commented on GitHub (Oct 24, 2022): same here We're experiencing exact the same on our firewalled company server.
kerem commented 2026-02-26 07:31:29 +03:00
Author
Owner
Copy link

@pf-uvonceumer commented on GitHub (Sep 22, 2023):

same here, I am running the container inside our company network which requires the use of the company proxy to connect to the internet.

<!-- gh-comment-id:1731175510 --> @pf-uvonceumer commented on GitHub (Sep 22, 2023): same here, I am running the container inside our company network which requires the use of the company proxy to connect to the internet.
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 28, 2024):

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

<!-- gh-comment-id:2081287522 --> @github-actions[bot] commented on GitHub (Apr 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@nigelm commented on GitHub (Apr 28, 2024):

I've just checked our installations with the latest release. I am no longer seeing this issue, however I believe this is likely due to a change in our environment (external DNS is no longer directly available) rather than the specific issue having been fixed - and the fetch is still failing, its just failing quickly.

Can @vcutrona or @pf-uvonceumer confirm that this issue still exists?

<!-- gh-comment-id:2081434212 --> @nigelm commented on GitHub (Apr 28, 2024): I've just checked our installations with the latest release. I am no longer seeing this issue, however I believe this is likely due to a change in our environment (external DNS is no longer directly available) rather than the specific issue having been fixed - and the fetch is still failing, its just failing quickly. Can @vcutrona or @pf-uvonceumer confirm that this issue still exists?
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@pf-uvonceumer commented on GitHub (Apr 29, 2024):

Issue still persist.

Proxy settings:

image

Log excerpt:

[4/29/2024] [7:38:43 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[4/29/2024] [7:40:55 AM] [IP Ranges] › ✖  error

Using latest tag:
sha256:6219c2184f19e0f50a77f4bb04066de79a3de795b6a863abaa861d52ff1fe012

<!-- gh-comment-id:2082080865 --> @pf-uvonceumer commented on GitHub (Apr 29, 2024): Issue still persist. Proxy settings: ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/99485641/41bf8823-c7f2-445d-9487-064f7e2f3e47) Log excerpt: ``` [4/29/2024] [7:38:43 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [4/29/2024] [7:40:55 AM] [IP Ranges] › ✖ error ``` Using latest tag: `sha256:6219c2184f19e0f50a77f4bb04066de79a3de795b6a863abaa861d52ff1fe012 `
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@vcutrona commented on GitHub (Jul 16, 2024):

I checked our Docker deployment and I can't find the issue within the log messages.
However, we changed our server environment as well, thus I can't reproduce the issue with our previous setup.

<!-- gh-comment-id:2230384923 --> @vcutrona commented on GitHub (Jul 16, 2024): I checked our Docker deployment and I can't find the issue within the log messages. However, we changed our server environment as well, thus I can't reproduce the issue with our previous setup.
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@pf-uvonceumer commented on GitHub (Jul 16, 2024):

Issue still persists in v2.11.3:

❯ Configuring npm user ...
useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
❯ IPv6 ...
Enabling IPV6 in hosts in: /etc/nginx/conf.d
- /etc/nginx/conf.d/production.conf
- /etc/nginx/conf.d/include/assets.conf
- /etc/nginx/conf.d/include/block-exploits.conf
- /etc/nginx/conf.d/include/ip_ranges.conf
- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- /etc/nginx/conf.d/include/log.conf
- /etc/nginx/conf.d/include/proxy.conf
- /etc/nginx/conf.d/include/ssl-ciphers.conf
- /etc/nginx/conf.d/include/force-ssl.conf
- /etc/nginx/conf.d/include/resolvers.conf
- /etc/nginx/conf.d/default.conf
Enabling IPV6 in hosts in: /data/nginx
- /data/nginx/proxy_host/1.conf
❯ Docker secrets ...
-------------------------------------
 _   _ ____  __  __
| \ | |  _ \|  \/  |
|  \| | |_) | |\/| |
| |\  |  __/| |  | |
|_| \_|_|   |_|  |_|
-------------------------------------
User:  npm PUID:0 ID:0 GROUP:0
Group: npm PGID:0 ID:0
-------------------------------------
❯ Starting nginx ...
❯ Starting backend ...
[7/16/2024] [1:02:13 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[7/16/2024] [1:02:15 PM] [Migrate  ] › ℹ  info      Current database version: none
[7/16/2024] [1:02:15 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[7/16/2024] [1:02:15 PM] [Global   ] › ⬤  debug     CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
[7/16/2024] [1:02:15 PM] [Setup    ] › ℹ  info      Logrotate completed.
[7/16/2024] [1:02:15 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[7/16/2024] [1:02:15 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[7/16/2024] [1:04:26 PM] [IP Ranges] › ✖  error     
[7/16/2024] [1:04:26 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[7/16/2024] [1:04:26 PM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
[7/16/2024] [1:04:26 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[7/16/2024] [1:04:26 PM] [Global   ] › ℹ  info      Backend PID 161 listening on port 3000 ...
[7/16/2024] [1:04:26 PM] [SSL      ] › ℹ  info      Completed SSL cert renew process
<!-- gh-comment-id:2230845308 --> @pf-uvonceumer commented on GitHub (Jul 16, 2024): Issue still persists in `v2.11.3`: ``` ❯ Configuring npm user ... useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range. ❯ Configuring npm group ... ❯ Checking paths ... ❯ Setting ownership ... ❯ Dynamic resolvers ... ❯ IPv6 ... Enabling IPV6 in hosts in: /etc/nginx/conf.d - /etc/nginx/conf.d/production.conf - /etc/nginx/conf.d/include/assets.conf - /etc/nginx/conf.d/include/block-exploits.conf - /etc/nginx/conf.d/include/ip_ranges.conf - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf - /etc/nginx/conf.d/include/log.conf - /etc/nginx/conf.d/include/proxy.conf - /etc/nginx/conf.d/include/ssl-ciphers.conf - /etc/nginx/conf.d/include/force-ssl.conf - /etc/nginx/conf.d/include/resolvers.conf - /etc/nginx/conf.d/default.conf Enabling IPV6 in hosts in: /data/nginx - /data/nginx/proxy_host/1.conf ❯ Docker secrets ... ------------------------------------- _ _ ____ __ __ | \ | | _ \| \/ | | \| | |_) | |\/| | | |\ | __/| | | | |_| \_|_| |_| |_| ------------------------------------- User: npm PUID:0 ID:0 GROUP:0 Group: npm PGID:0 ID:0 ------------------------------------- ❯ Starting nginx ... ❯ Starting backend ... [7/16/2024] [1:02:13 PM] [Global ] › ℹ info Using Sqlite: /data/database.sqlite [7/16/2024] [1:02:15 PM] [Migrate ] › ℹ info Current database version: none [7/16/2024] [1:02:15 PM] [Setup ] › ℹ info Logrotate Timer initialized [7/16/2024] [1:02:15 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager [7/16/2024] [1:02:15 PM] [Setup ] › ℹ info Logrotate completed. [7/16/2024] [1:02:15 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [7/16/2024] [1:02:15 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [7/16/2024] [1:04:26 PM] [IP Ranges] › ✖ error [7/16/2024] [1:04:26 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [7/16/2024] [1:04:26 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ... [7/16/2024] [1:04:26 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [7/16/2024] [1:04:26 PM] [Global ] › ℹ info Backend PID 161 listening on port 3000 ... [7/16/2024] [1:04:26 PM] [SSL ] › ℹ info Completed SSL cert renew process ```
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jan 26, 2025):

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

<!-- gh-comment-id:2614172809 --> @github-actions[bot] commented on GitHub (Jan 26, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:31:30 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jan 26, 2026):

Issue was closed due to inactivity.

<!-- gh-comment-id:3797639384 --> @github-actions[bot] commented on GitHub (Jan 26, 2026): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1542
No description provided.