Error 504, 502 and connection error

[PierreP94]

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?
  • No
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug

I have connection error ERR_NAME_NOT_RESOLVED, 502 Bad Gateway or 504 Gateway Time-out
following the container I'm redirecting to....
It's also working for one (bitwarden).

Nginx Proxy Manager Version

Latest

To Reproduce
Steps to reproduce the behavior:

1. Redirect the port 80 and the 443 used by DSM to 82 and 444.
2. Do the tutorial on official website.
3. Connect to proxy_default all the containers.
4. Make the redirection using http://name:port in NPM
5. Then it's impossible to connect even if the http://Nas_local_IP:port is working written directly in the navigator (I have ofc tried to fill NPM like this and it's not working better :)

Expected behavior

Screenshots

Operating System

I'm trying to hide all my Synology NAS 918+ behind reverse proxy with nginx proxy manager.

Additional context

I have check that DNS is finding hosts with

docker exec proxy_app_1 host portainer
portainer has address 192.168.16.4

Thanks for help :/

[PierreP94]

Well that was because I haven't used internal port of docker and for the domain i had to redirect to www.domaine_name.com:entrance_port

So it was impossible to use local ip adress. Don't know why

[PierreP94]

Well it's working more or less but I believe that redirecting to www.domaine_name.com:entrance_port is a bit lame :/

[github-actions]

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

[github-actions]

Issue was closed due to inactivity.