504 Gateway Time-out

[Sigri44]

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.

[Sigri44]

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

[combatistor]

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

[5fxKu8VV8n]

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.

[shashankhrs]

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.

[mufazmi]

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.

[WaxArsatia]

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?

[github-actions]

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