starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #1266] Error 504, 502 and connection error #1021

New issue

Closed

opened 2026-02-26 06:35:27 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:35:27 +03:00

Owner

Originally created by @PierreP94 on GitHub (Jul 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1266

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:

Redirect the port 80 and the 443 used by DSM to 82 and 444.
Do the tutorial on official website.
Connect to proxy_default all the containers.
Make the redirection using http://name:port in NPM
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 :/

Originally created by @PierreP94 on GitHub (Jul 28, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1266 **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 :/

kerem

2026-02-26 06:35:27 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:35:28 +03:00

Author

Owner

@PierreP94 commented on GitHub (Jul 28, 2021):

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 commented on GitHub (Jul 28, 2021): 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

kerem commented

2026-02-26 06:35:28 +03:00

Author

Owner

@PierreP94 commented on GitHub (Jul 30, 2021):

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

@PierreP94 commented on GitHub (Jul 30, 2021): Well it's working more or less but I believe that redirecting to www.domaine_name.com:entrance_port is a bit lame :/

kerem commented

2026-02-26 06:35:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 7, 2024):

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

@github-actions[bot] commented on GitHub (Mar 7, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:35:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 20, 2025): Issue was closed due to inactivity.

No milestone

No project

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#1021

No description provided.

Rows
Columns