docker droplet with nginx proxy manager and various other dockers

Hi All,

New to digitalocean but experienced enough with nginx proxy manager (NPM) and dockers. I have set up NPM and 2 other dockers. Everything is reachable by IP number of the droplet and port number and if I ping the (sub) domain I get the result I expect with the ip numbr of the droplet. However I am not able to use NPM as I am used to IE ip of droplet:port for a proxy host. I also tried localhost:port and Mainly the result is # 504 Gateway Time-out openresty I also got some json responses with using localhost:port:

**{**"status": "OK","version": **{**"major": **2**,"minor": **10**,"revision": **4****}****}**

But I have no clue where that comes from. I have searched high and low but could not find any information that helped me address the issue. The dockers themselves have no issue, I get all the expected results when using droplet0ip:port. IE a webpage displays and I can also send a push message that way. Any tips would be appreciated.

Kind Regards,

Gerrit Kuilder

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
January 11, 2024

Hello Gerrit,

Welcome to DigitalOcean and the world of Docker and Nginx Proxy Manager NPM! From your description, it seems the core issue might revolve around DNS configuration rather than the Docker or NPM setup itself.

When you mention that everything is reachable via the IP address of the droplet but not through the (sub)domain, it suggests a possible mismatch or misconfiguration in the DNS settings. Here are some key points to focus on:

  1. DNS Records: Verify that your DNS records are correctly pointing to your droplet’s IP address. This includes checking A records for your main domain and any subdomains you are using. Since you’re getting the correct IP when pinging your domain, it seems like the A records are probably set up correctly.

  2. Subdomain Configuration: Make sure that your subdomains are correctly configured in both your DNS settings and in NPM. Each subdomain should have an A record pointing to your droplet’s IP.

  3. Propagation Time: Remember that DNS changes can take time to propagate. After making any changes to your DNS records, it might take up to 48 hours for these changes to fully propagate across the internet.

Best of luck with your setup, and feel free to reach out if you have further questions!



Site Moderator
Site Moderator badge
January 10, 2024


If the DNS was recently updated keep in mind that DNS changes might take up to 48 hours to fully update, this is mainly due to DNS cache from the ISPs and general DNS propagation time.

You can examine the Nginx error_log for the 504 Gateway Time-out error as this is usually Nginx related error.

Additionally, you can use tools like curl or telnet to manually test the connectivity from both the localhost and external machines.


Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel