starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #566] 504 Gateway Time-out #476

New issue

Closed

opened 2026-02-26 06:32:59 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 06:32:59 +03:00

Owner

Originally created by @Sigri44 on GitHub (Aug 19, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/566

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?
Yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
No

Describe the bug
A clear and concise description of what the bug is.
If I create a https proxy host I get a 504 Gateway Time-out if I request the site.
What version of Nginx Proxy Manager is reported on the login page?
v2.3.1

To Reproduce
Steps to reproduce the behavior:

Go to Dashboard
Click on Hosts
Click on Add proxy host
Fill in subdomain name
Select https scheme
fill in domain and port
select SSL
request SSL cert
select force ssl or deselect will result same 504 Gateway Timeout
open new created site and wait for error

Expected behavior
A clear and concise description of what you expected to happen.

display the site I requested.

Screenshots

Operating System
running on docker container station.

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.

Originally created by @Sigri44 on GitHub (Aug 19, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/566 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? Yes If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? No Describe the bug A clear and concise description of what the bug is. If I create a https proxy host I get a 504 Gateway Time-out if I request the site. What version of Nginx Proxy Manager is reported on the login page? v2.3.1 To Reproduce Steps to reproduce the behavior: Go to Dashboard Click on Hosts Click on Add proxy host Fill in subdomain name Select https scheme fill in domain and port select SSL request SSL cert select force ssl or deselect will result same 504 Gateway Timeout open new created site and wait for error Expected behavior A clear and concise description of what you expected to happen. display the site I requested. Screenshots ![image](https://user-images.githubusercontent.com/9304947/90669616-3570c500-e252-11ea-997d-1afeded247e4.png) Operating System running on docker container station. 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.

kerem

2026-02-26 06:32:59 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@Sigri44 commented on GitHub (Aug 24, 2020):

AH !! Big error, same when i test with IP address !!!

@Sigri44 commented on GitHub (Aug 24, 2020): AH !! Big error, same when i test with IP address !!! ![image](https://user-images.githubusercontent.com/9304947/91074439-d7225880-e63c-11ea-8b67-0b0ff7ed2a2f.png) ![image](https://user-images.githubusercontent.com/9304947/91074465-e30e1a80-e63c-11ea-887f-c834e710d828.png)

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@combatistor commented on GitHub (Sep 23, 2020):

I also have the same problem. In my case I don't use SSL, just HTTP to access my internal servers. my internal DNS is provided by Pihole
Edit: It was a firewall config issue, make sure you open the correct ports

@combatistor commented on GitHub (Sep 23, 2020): I also have the same problem. In my case I don't use SSL, just HTTP to access my internal servers. my internal DNS is provided by Pihole Edit: It was a firewall config issue, make sure you open the correct ports

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@5fxKu8VV8n commented on GitHub (Dec 20, 2021):

Thank you so much @combatistor for your answer, since few weeks i had this problem with Pi-hole, Gitea, etc... My ufw was not having necessary rules to allow trafic for these services.

@5fxKu8VV8n commented on GitHub (Dec 20, 2021): Thank you so much @combatistor for your answer, since few weeks i had this problem with Pi-hole, Gitea, etc... My ufw was not having necessary rules to allow trafic for these services.

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@shashankhrs commented on GitHub (Sep 19, 2023):

My setup is on portainer.

I can access the services with the IP address properly but when I try to access with the domain there's an error message "Gateway time-out Error code 504". My UFW was disabled.
I enabled UFW and added the below rules:
To Action From

22/tcp ALLOW Anywhere
21/tcp ALLOW Anywhere
21 ALLOW Anywhere
9000 ALLOW Anywhere
9000/tcp ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
8080/tcp ALLOW Anywhere
81/tcp ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
21/tcp (v6) ALLOW Anywhere (v6)
21 (v6) ALLOW Anywhere (v6)
9000 (v6) ALLOW Anywhere (v6)
9000/tcp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
8080/tcp (v6) ALLOW Anywhere (v6)
81/tcp (v6) ALLOW Anywhere (v6)

Still not able to access.

@shashankhrs commented on GitHub (Sep 19, 2023): My setup is on portainer. I can access the services with the IP address properly but when I try to access with the domain there's an error message "Gateway time-out Error code 504". My UFW was disabled. I enabled UFW and added the below rules: To Action From -- ------ ---- 22/tcp ALLOW Anywhere 21/tcp ALLOW Anywhere 21 ALLOW Anywhere 9000 ALLOW Anywhere 9000/tcp ALLOW Anywhere 80/tcp ALLOW Anywhere 443/tcp ALLOW Anywhere 8080/tcp ALLOW Anywhere 81/tcp ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 21/tcp (v6) ALLOW Anywhere (v6) 21 (v6) ALLOW Anywhere (v6) 9000 (v6) ALLOW Anywhere (v6) 9000/tcp (v6) ALLOW Anywhere (v6) 80/tcp (v6) ALLOW Anywhere (v6) 443/tcp (v6) ALLOW Anywhere (v6) 8080/tcp (v6) ALLOW Anywhere (v6) 81/tcp (v6) ALLOW Anywhere (v6) Still not able to access.

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@mufazmi commented on GitHub (Oct 23, 2023):

I have setup one of subdomain for portainer. while deploying the new image. it's take time.
i want here the configuration to wait for the server response , doesn't matter how much time server take to repsonse.

the nginx manager should wait for the server response.

@mufazmi commented on GitHub (Oct 23, 2023): I have setup one of subdomain for portainer. while deploying the new image. it's take time. i want here the configuration to wait for the server response , doesn't matter how much time server take to repsonse. the nginx manager should wait for the server response.

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@WaxArsatia commented on GitHub (May 6, 2024):

I have setup one of subdomain for portainer. while deploying the new image. it's take time. i want here the configuration to wait for the server response , doesn't matter how much time server take to repsonse.

the nginx manager should wait for the server response.

same here, i use nginx proxy manager too for portainer, my schema is Cloudflare Access Tunnel > Nginx Proxy Manager > Portainer, and got 504 error when triggering gitops webhook using github actions, did this related to cloudflare or nginx proxy manager?

@WaxArsatia commented on GitHub (May 6, 2024): > I have setup one of subdomain for portainer. while deploying the new image. it's take time. i want here the configuration to wait for the server response , doesn't matter how much time server take to repsonse. > > the nginx manager should wait for the server response. same here, i use nginx proxy manager too for portainer, my schema is Cloudflare Access Tunnel > Nginx Proxy Manager > Portainer, and got 504 error when triggering gitops webhook using github actions, did this related to cloudflare or nginx proxy manager?

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 18, 2024):

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

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

kerem commented

2026-02-26 06:33:00 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 2, 2026):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jan 2, 2026): 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#476

No description provided.

Rows
Columns