502 Bad Gateway Error | Dynmap® | Page 1

prisma basalt Feb 24, 2025, 3:28 PM

#

I am trying to reverse proxy my dynmap with nginx, but I am just getting a 502 bad gateway error when I visit the page. I have seen other people online with the same issue, but I can't find a solution anywhere.

mossy kindleBOT Feb 24, 2025, 3:28 PM

#

Before we get started, please tell us a bit about your server setup:

#

Thank you! Please provide any errors you are experiencing and upload your configuration.txt. Someone from our <@&801354402010628138> team will respond to help shortly. As a general reminder, everyone on our support team is a volunteer, please be kind!

#

(optional) Please upload your configuration.txt to https://pastebin.com and send us the link. BE SURE TO REMOVE PASSWORDS

Pastebin

Pastebin.com - #1 paste tool since 2002!

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

prisma basalt Feb 24, 2025, 3:29 PM

#

I am on 1.21, but I wouldn't give me an option for that.

#

https://pastebin.com/ztLL3Lxu

Pastebin

configuration.txt - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

willow kettle Feb 24, 2025, 4:15 PM

#

You configuration.txt looks reasonable. How are you configuring nginx? Is nginx and your Dynmap on the same machine? Can you confirm that you can access http://127.0.0.1:8123/ from the same machine? If you only have SSH access, you could try something like wget http://127.0.0.1:8123/ to check.

prisma basalt Feb 24, 2025, 4:24 PM

#

Yes nginx and dynmap are running on the same machine and both are running in dockers on a truenas server. One important piece of information that I forgot to give was that I have used the exact same method to configure other ports (like 25565 for my Minecraft serve) and it has worked without issue.
I can access dynmap when I use the port directly. But for security reasons I don't want to forward it.

willow kettle Feb 24, 2025, 4:27 PM

#

So your nginx should forward some port (80, or 443) and/or subdomain and/or uri to http://192.168.a.b:8123/ I guess? That is, a local address and not your public one.

prisma basalt Feb 24, 2025, 4:27 PM

#

nginx configuration:

#

Yes nginx is fowarding to 80 and 443

willow kettle Feb 24, 2025, 4:28 PM

#

Note that the internal server only supports HTTP, not HTTPS

#

(I've never setup nginx, so I'm not sure what these settings mean exactly)

prisma basalt Feb 24, 2025, 4:29 PM

#

#

ok, I have both set up.

willow kettle Feb 24, 2025, 4:29 PM

#

Nginx could probably answer to either, but it must always connect to the internal server using HTTP.

prisma basalt Feb 24, 2025, 4:30 PM

#

It does

willow kettle Feb 24, 2025, 4:30 PM

#

Ok, but it fails to connect?

#

What does the nginx log say when you try to access it?

#

Also, is the Dynmap and the nginx server in the same docker or different? I'm assuming the table you show is name, interface(s), public port, internal port, internal IP, protocols, enabled? If so, I'm guessing you have docker setup so that ports 30022 on the physical machine is mapped to 443 in the docker "machine"? Is 8123 on the physical machine mapped to 8123 in the Dynmap docker?

prisma basalt Feb 24, 2025, 4:36 PM

#

willow kettle Nginx could probably answer to either, but it must always connect to the interna...

nvm, that was the issue. I feel so dumb now.
I though that part was for external ip, not internal. I hindsight that doesn't make much since given the menu structure.

willow kettle Feb 24, 2025, 4:37 PM

#

So you got it working?

prisma basalt Feb 24, 2025, 4:37 PM

#

yep

#

thanks for the help

willow kettle Feb 24, 2025, 4:37 PM

#

Great! Happy mapping! 🙂

mossy kindleBOT Feb 28, 2025, 12:02 AM

#