Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latest docker image?
✔️
- Are you sure you're not using someone else's docker image?
✔️
Describe the bug
host.docker.internal is not resolved by nginx
To Reproduce
Steps to reproduce the behavior:
- Run NPM
- Run some web application on the Docker host (e.g. on port 5000)
- Use
host.docker.internal as target

- Try to access the proxied
host.docker.internal:5000
- Target page is not displayed and error is logged
2019/12/15 19:47:17 [error] 998#998: *368 host.docker.internal could not be resolved (3: Host not found), client: 192.168.16.1, server: xxx.local.test, request: "GET / HTTP/2.0", host: "xxx.local.test", referrer: "http://localhost:81/nginx/proxy"
Expected behavior
The NPM proxied domain, should show the page running under 127.0.0.1 on the Docker host
Workaround
If I ping host.docker.internal on the running app container and use the resulting IP as target it works

Operating System
macOS
Checklist
jc21/nginx-proxy-manager:latestdocker image?✔️
✔️
Describe the bug
host.docker.internalis not resolved by nginxTo Reproduce
Steps to reproduce the behavior:
host.docker.internalas targethost.docker.internal:5000Expected behavior
The NPM proxied domain, should show the page running under 127.0.0.1 on the Docker host
Workaround
If I ping
host.docker.internalon the runningappcontainer and use the resulting IP as target it worksOperating System
macOS