NginxProxyManager / NginxProxyManager/nginx-proxy-manager

[ip-ranges.amazonaws.com](ip-ranges.amazonaws.com) is blocked by GFW, deployment will never continue

Open
#4,064 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
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

image

although amazonaws.com can be accessed from China mainland successfully, it' subdomain ip-ranges.amazonaws.com cannot, which is hard coded in backend/internal/ip_ranges.js.

Nginx Proxy Manager Version

latest --> 2 (linux/amd64)

To Reproduce
Steps to reproduce the behavior:

  1. Just deploy it on any VPS within GFW, and you will see the request of ip-range has no response

Expected behavior

Screenshots

image

Operating System

root@[REDACTED]:~# neofetch
       _,met$$$$$gg.          root@[REDACTED]
    ,g$$$$$$$$$$$$$$$P.       ----------------
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 12 (bookworm) x86_64
 ,$$P'              `$$$.     Host: CVM 3.0
',$$P       ,ggs.     `$$b:   Kernel: 6.1.0-26-amd64
`d$$'     ,$P"'   .    $$$    Uptime: 1 day, 39 mins
 $$P      d$'     ,    $$P    Packages: 612 (dpkg)
 $$:      $$.   -    ,d$$'    Shell: bash 5.2.15
 $$;      Y$b._   _,d$P'      Resolution: 1024x768
 Y$$.    `.`"Y$$$$P"'         Terminal: /dev/pts/0
 `$$b      "-.__              CPU: AMD EPYC 7K62 (2) @ 2.595GHz
  `Y$$                        GPU: 00:02.0 Cirrus Logic GD 5446
   `Y$$.                      Memory: 565MiB / 1838MiB
     `$$b.
       `Y$$b.
          `"Y$b._
              `"""

Additional context

This machine was bought from Tencent Co. Ltd. by my boss before I could prevent him from doing so cause Tencent is a company with a terrible reputation in China mainland. Forking your repo may help, but I don't think this url should be hard coded while a mirror site is needed here.

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 backend/internal/ip_ranges.js and inspect how the hard-coded ip-ranges.amazonaws.com request is used during deployment. Reproduce the request from a VPS within the GFW, then verify that deployment can obtain the required IP ranges successfully in that environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, networking
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.