mirror of
https://github.com/webbukkit/dynmap.git
synced 2024-11-21 17:55:22 +01:00
2
Use dynmap via Pterodactyl
Tony edited this page 2023-10-25 19:53:05 -07:00
Admins
- Allocate the port on the node you host your Minecraft instance on. 8123 is the default port for dynmap. You should configure the ports as you wish.
- Assign the port to your Minecraft server:
Normal users
- Create a port allocation and take note of the newly allocated port.
- Using this port, edit the
webserver-portof yourconfiguration.txt
Troubleshooting:
- Make sure you've selected the right IP address when adding the server to the node.
- Make sure the port is open (no firewall or router blocking it). Try testing reachability in the shell with
nc -vzw 10 <your-server-ip> <dynmap-port>
If you can SSH into the node,
- Try
docker ps -f "label=Service=Pterodactyl" --format='table {{.ID}}\t{{.Image}}\t{{.Ports}}'and check that the ports are mapped correctly and the listening IP address is matched to the same node as your Minecraft server.
CONTAINER ID IMAGE PORTS
05878da27e13 ghcr.io/pterodactyl/yolks:java_17 10.0.0.5:8123->8123/tcp, 10.0.0.5:8123->8123/udp, 10.0.0.5:27000->27000/tcp, 10.0.0.5:27000->27000/udp
The steps below only help diagnose if dynmap isn't running or encountered an error. More likely than not, address and port allocations were misconfigured, and you should check the previous steps carefully.
- If the ports are mapped correctly, try testing if dynmap is running with
curl -L <your-server-ip>:<dynmap-port>while in the SSH session. - If you couldn't reach dynmap even in the SSH session, you can try
docker exec <container-id> curl localhost:<dynmap-port> - If that fails, dynmap isn't running or encountered an error and you should refer to general dynmap troubleshooting.