mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #143] 504 Gateway Time-out #125
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fa-ve on GitHub (May 13, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/143
Checklist
jc21/nginx-proxy-manager:latestdocker image?Yes
Yes
No
Describe the bug
If I create a https proxy host I get a 504 Gateway Time-out if I request the site.
v2.0.13
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
display the site I requested.
Screenshots
N/A
Operating System
Additional context
Add any other context about the problem here, docker version, browser version if applicable to the problem. Too much info is better than too little.
@OhHeyAlan commented on GitHub (May 13, 2019):
Step #5, try setting it to
httpfor the scheme.@fa-ve commented on GitHub (May 14, 2019):
same for HTTP, HTTP to HTTP is working perfect.. HTTPS to HTTPS is giving this timeout..
@fa-ve commented on GitHub (May 14, 2019):
it's a weird issue, if I connect the server through an internal IP I get the error message. If I expose the same through my public IP it works as expected. a other internal https site is working.. so something is wrong with the destination site I expect
@jc21 commented on GitHub (May 16, 2019):
The error suggests that Nginx cannot talk to your upstream server. Without knowing your network stack, this is hard to diagnose.
@murraydb commented on GitHub (Jul 24, 2020):
Just in case anyone find this. I had this trouble with Heimdall and Tautulli.
if my server address was 192.168.3.69 - I had been using that for most items. (Sonarr, PiHole, Radarr, Plex, JellyFin etc.)
When I used that same address for either Tautulli or Heimdall I would get the 504 Gateway timeout.
My solution was to check the docker items ip in portainer ex 172.17.0.2 for Heimdall and http://172.17.0.5 for Tautulli. Also to note, use the docker internal port 80 for Heimdall in my case, though I have 740 exposed via docker.
I know this wasn't a bug in the nginx-proxy-manager project, but I figured, I would share my solution in case others find this thread via google as I did.
@luminousmg commented on GitHub (Aug 7, 2020):
I had a similar issue with Digital Ocean, when using the assigned IP address of the droplet. I corrected the issue by setting up a "Floating IP" in Digital Ocean and assigned that to the droplet. Everything worked once I started using the floating IP address. (I imagine this would also occur on AWS and you would need to assign an elastic IP address to the instance.) Also this is not a bug of this project, but hopefully, this helps others who may encounter this issue. Be sure to double-check the firewall and open required ports on your instance as well.
@b4oshany commented on GitHub (Sep 6, 2020):
@luminousmg, thanks for ur comment. I landed in the same problem
@kimtiago commented on GitHub (Jun 14, 2022):
Thanks! This topic saved me.
@dongido001 commented on GitHub (Jan 19, 2023):
OMG @luminousmg Thanks a lot! was about to give up already. Saved me on Digital ocean (It's now called reserved IP)