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
although amazonaws.com can be accessed from shina 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:
Just deploy it on any VPS within GFW, and you will see the request of ip-range has no response
This machine was bought from Tencent Co. Ltd. by my boss before I could prevent him from doing so causing Tencent is a company with a terrible reputation in shina mainland. Forking your repo may help, but I don't this url should be hardcoded while mirror site is needed here.
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
although amazonaws.com can be accessed from shina 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:
Expected behavior
Screenshots
Operating System
Additional context
This machine was bought from Tencent Co. Ltd. by my boss before I could prevent him from doing so causing Tencent is a company with a terrible reputation in shina mainland. Forking your repo may help, but I don't this url should be hardcoded while mirror site is needed here.