Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Use a hostname such as map.example.com, point its DNS A record to the Minecraft server’s public IP, and place Nginx or Apache in front of Dynmap as a reverse proxy. Dynmap continues listening on its internal web port (8123 by default), while visitors use the clean hostname without :8123. Add a TLS certificate at the proxy when you want HTTPS.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Prove that Dynmap works directly before changing DNS or proxy settings. Open http://SERVER_IP:8123/ (or the port configured by your host), confirm that Dynmap reports a successful web-server start, and only then build the public hostname.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
How the finished setup works
A custom Dynmap URL has three separate layers. Keeping them separate makes failures much easier to diagnose:
- Dynmap’s embedded web server serves the map on its configured port. The documented default is
webserver-port: 8123. A shared Minecraft host may assign a different available port, and changing that value requires a server restart. - DNS maps the name people type, such as
map.example.com, to the server’s public IP with anArecord. - The reverse proxy listens on standard web ports 80 and 443, accepts requests for the hostname, and forwards them to Dynmap on its internal address and port. It can also terminate HTTPS.
Self-hosted installations must expose or port-forward the selected Dynmap port for direct external access. With a reverse proxy on the same machine, the proxy normally connects to Dynmap locally, while the firewall exposes only the public web ports.
#1 Best Overall
- 𝐁𝐥𝐚𝐳𝐢𝐧𝐠 𝐅𝐚𝐬𝐭 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞: Features the Broadcom BCM2712 2.4GHz quad-core 64-bit Arm Cortex-A76 CPU with advanced GPU capabilities, ensuring smooth and efficient operation for various applications.
- 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗴𝗲𝘁 𝘀𝘁𝗮𝗿𝘁𝗲𝗱: Comprehensive Kit Includes 11 essential components, such as the Raspberry Pi 5 board, cooling case, power supply, preflashed128GB Micro SD card, and more, to get you up and running quickly.
- 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁 𝗖𝗼𝗼𝗹𝗶𝗻𝗴 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: The kit includes a unique solid built passive cooling case thatalso has a fan and adjusts the fan speed based on temperature, ensuring optimal cooling and performance.
- 𝗩𝗲𝗿𝘀𝗮𝘁𝗶𝗹𝗲 𝗨𝘀𝗮𝗴𝗲: Ideal for use as a mini-computer, media hub, DIY server, Plex server, Minecraft server, home automation, retro gaming, Network wide ad blocker or container management device, making it perfect for a wide range of projects and applications.
- 𝗤𝘂𝗮𝗹𝗶𝘁𝘆 𝗔𝗰𝗰𝗲𝘀𝘀𝗼𝗿𝗶𝗲𝘀: Comes with a durable neoprene storage bag, HDMI cables, and a quickstart guide, providing a smooth and 𝗲𝗮𝘀𝘆 𝘀𝗲𝘁𝘂𝗽 𝗲?𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 and keeping your components organized and protected.
| URL a visitor uses | What handles the request | Typical upstream |
|---|---|---|
http://map.example.com |
Nginx or Apache on port 80 | http://localhost:8123/ |
https://map.example.com |
Nginx or Apache on port 443, with TLS | http://localhost:8123/ |
http://SERVER_IP:8123/ |
Dynmap directly | Dynmap’s embedded web server |
The internal port does not change merely because you add a domain. Visitors omit :8123 because the proxy is listening on the standard HTTP or HTTPS port.
What you need before starting
You need a running Minecraft server with Dynmap installed, permission to edit its configuration, a domain whose DNS you can manage, and a host on which Nginx or Apache can listen. You also need network control at every relevant layer: the operating-system firewall, a cloud security group if the server is hosted in a cloud, and a home router if the server is behind NAT. A TLS certificate is optional; Certbot is one tool that can obtain and install one for a proxy.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11There is no Dynmap setting that magically registers a domain. The domain, DNS record, web server, and network rules are separate pieces. If a managed Minecraft host does not let you run a reverse proxy or bind ports 80 and 443, ask its administrator whether it provides a proxy endpoint or an assigned web port. Do not assume that the default 8123 port is available on a shared plan.
Before you change DNS: verify Dynmap itself
Check the configured port
Open Dynmap’s configuration and find webserver-port. Unless your host supplied another value, use 8123. Shared hosts sometimes restrict ports, so ask the host administrator which port is available and restart the Minecraft server after changing the setting.
Test the direct address
- Start Minecraft and wait for the server log to state that Dynmap’s web server started successfully.
- From a browser, visit
http://SERVER_IP:8123/, replacing the port with the configured value when necessary. - Confirm that the map loads and that tiles or player information respond normally.
- If the page does not load, stop here. Investigate the Dynmap log, local firewall, cloud security group, router port-forwarding, or host restrictions before touching DNS or Nginx.
This direct test isolates Dynmap from every later component. A reverse proxy cannot repair a web server that is not running or a port that is blocked.
Choose the hostname and DNS record
Use a subdomain for the map
map.example.com is usually the least disruptive choice because it leaves the root domain available for a website or other service. In your registrar or DNS provider’s interface, create an A record whose name is the subdomain label (often map) and whose value is the server’s public IPv4 address.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use the root domain when appropriate
For a root hostname such as example.com, many DNS dashboards use @ as the record name. The Dynmap Nginx guide specifically documents an A record with host @ pointing to the server’s IP. Registrar interfaces differ, so follow the labels shown by your provider.
Keep the names identical
The DNS name, the proxy’s server_name (or Apache virtual host), and the certificate name must all be the exact hostname visitors use. A record for map.example.com does not automatically cover example.com, and a certificate for one name does not make the other name valid.
DNS propagation depends on the provider and the record’s TTL; the Dynmap documentation does not promise a universal wait time. Verify that the record resolves to the intended public IP before diagnosing the proxy.
Check the address before testing the proxy
Make sure the record points to the public address that actually receives web traffic. If Nginx or Apache is on a separate machine from Minecraft, the record must point to the proxy machine, not necessarily the private address of the Minecraft host. The proxy then needs network access to Dynmap’s configured upstream address. A private address such as 192.168.x.x is not a usable public DNS target for Internet visitors.
Recommended Free Tools
Rank #2
- This Certified Refurbished product is tested and certified to look and work like new. The refurbishing process includes functionality testing, basic cleaning, inspection, and repackaging.
- HP EliteDesk 705 G4 Mini Desktop Computer: AMD Quad-Core Ryzen 5 Pro 2400GE upto 3.8GHz, 8GB DDR4 RAM, 256GB SSD
- Multitasking is easy with 8 GB of RAM, 256 GB SSD of storage
- Equipped with a blazing fast AMD Ryzen 5 Pro 3.60 GHz processor.
- Pre-installed with Windows 11 Pro 64-bit, this mini PC is ready to handle all your business tasks with ease.
Nginx reverse proxy setup
Nginx is the clearest route when you want to preserve Dynmap’s internal service while presenting a normal web URL. The following configuration follows the Dynmap Wiki pattern; replace the hostname and upstream port with your values.
1. Create the virtual host
server {
server_name map.example.com;
listen 80;
location / {
proxy_pass http://localhost:8123/;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
}The trailing slash in the shown upstream URL is part of the documented pattern. If Dynmap uses another port, change only the upstream target, for example http://localhost:PORT/. If Nginx runs on a different machine, replace localhost with the Dynmap server’s reachable address and allow that connection through the network firewall.
The forwarded headers are useful when Dynmap or another layer needs to know the original host and client address. Keep the Host, X-Real-IP, and X-Forwarded-For lines together unless you have a deliberate proxy policy that replaces them.
2. Enable and test the virtual host
Place the server block in the location used by your operating system, enable the site if your distribution uses a separate enabled-sites directory, and validate the Nginx configuration before restarting the service:
sudo service nginx configtestFix every reported syntax or path error. After a successful test, restart or reload Nginx using the service method provided by your operating system. Visit http://map.example.com and confirm that the Dynmap map appears. A configuration test checks syntax; it does not prove that DNS, the firewall, or Dynmap’s upstream is reachable, so perform the browser test as a separate step.
3. Check the DNS-to-hostname match
If the default server responds instead of Dynmap, the request is often reaching Nginx with a hostname that does not match server_name. Check spelling, the DNS record, and whether the browser is using the root domain or the subdomain. The proxy hostname and the DNS hostname must be identical.
Add HTTPS and remove the port from the public URL
Use a certificate tool such as Certbot with the Nginx or Apache configuration when you want https://map.example.com. The proxy terminates TLS; Dynmap can continue receiving ordinary HTTP on its internal port.
- Make sure the DNS record already points to the proxy server.
- Allow TCP port 80 for certificate validation and HTTP access.
- Allow TCP port 443 for HTTPS access. On a home network, forward those ports from the router to the proxy host.
- Run your certificate tool for the exact hostname and let it update the proxy configuration, or install the certificate in your existing virtual host.
- Test the HTTPS URL and check that the certificate name matches the hostname.
After TLS is working, users can visit https://map.example.com without specifying Dynmap’s internal port. Port 8123 remains the upstream target inside the proxy configuration.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHTTP and HTTPS are independent listeners. Opening 80 does not open 443, and a certificate cannot make a blocked 443 connection work. If you use an automatic HTTP-to-HTTPS redirect, keep port 80 reachable so certificate validation and the initial redirect can complete.
Apache alternative
Apache is a practical choice when it already serves your other sites. On Debian or Ubuntu, enable the modules needed for proxying, including rewrite and proxy_http, then place the following directives in the appropriate virtual host:
Rank #3
- 𝐁𝐥𝐚𝐳𝐢𝐧𝐠 𝐅𝐚𝐬𝐭 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞: Features the Broadcom BCM2712 2.4GHz quad-core 64-bit Arm Cortex-A76 CPU with advanced GPU capabilities, ensuring smooth and efficient operation for various applications.
- 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗴𝗲𝘁 𝘀𝘁𝗮𝗿𝘁𝗲𝗱: Comprehensive Kit Includes 11 essential components, such as the Raspberry Pi 5 board, cooling case, power supply, preflashed128GB Micro SD card, and more, to get you up and running quickly.
- 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝘁 𝗖𝗼𝗼𝗹𝗶𝗻𝗴 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: The kit includes a unique solid built passive cooling case thatalso has a fan and adjusts the fan speed based on temperature, ensuring optimal cooling and performance.
- 𝗩𝗲𝗿𝘀𝗮𝘁𝗶𝗹𝗲 𝗨𝘀𝗮𝗴𝗲: Ideal for use as a mini-computer, media hub, DIY server, Plex server, Minecraft server, home automation, retro gaming, Network wide ad blocker or container management device, making it perfect for a wide range of projects and applications.
- 𝗤𝘂𝗮𝗹𝗶𝘁𝘆 𝗔𝗰𝗰𝗲𝘀𝘀𝗼𝗿𝗶𝗲𝘀: Comes with a durable neoprene storage bag, HDMI cables, and a quickstart guide, providing a smooth and 𝗲𝗮𝘀𝘆 𝘀𝗲𝘁𝘂𝗽 𝗲?𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 and keeping your components organized and protected.
ProxyRequests off
ProxyPass / "http://localhost:8123/"
ProxyPassReverse / "http://localhost:8123/"ProxyRequests off is important because this is a reverse proxy, not an open forward proxy. Replace the port if your Dynmap configuration differs. Validate the Apache configuration, restart Apache, and open the domain over HTTP or HTTPS. As with Nginx, DNS must resolve the hostname to the Apache server, and ports 80 and 443 must be reachable from the Internet when those protocols are used.
Use the same hostname in the Apache virtual host that you plan to place in DNS and in the certificate request. If Apache serves several sites, a mismatched virtual-host name can send the request to another site’s default page even though the proxy directives themselves are correct.
Direct port, reverse proxy, or copied files?
| Approach | Public URL | Advantages | Limitations and use case |
|---|---|---|---|
| Direct Dynmap port | http://SERVER_IP:8123/ or the configured port |
Fastest diagnostic path; no proxy configuration. | Exposes a non-standard port and the server IP; HTTPS and hostname handling are not provided by Dynmap itself. |
| Nginx reverse proxy | http(s)://map.example.com |
Clean hostname, standard ports, and a straightforward place to terminate TLS. | Requires Nginx configuration, DNS, and firewall access. |
| Apache reverse proxy | http(s)://map.example.com |
Fits installations that already use Apache; uses ProxyPass and ProxyPassReverse. |
Requires the proxy modules and a valid Apache virtual-host configuration. |
| External web server serving copied static files | Depends on the external server | Can separate the public web server from Dynmap’s embedded server. | The documented material identifies this pattern but does not provide a complete copy, update, or synchronization procedure. It is less direct than proxying when you want Dynmap’s live service preserved. |
For most installations, reverse proxying is the least surprising design: Dynmap keeps generating the map, while the established web server handles the domain, ports, and certificate. Serving copied files can introduce stale map data or an additional synchronization process, so do not choose it merely to avoid a short proxy configuration.
Firewall, router, and forwarded-client-IP settings
Open only the ports you intend to use
- Direct testing: the configured Dynmap port must be reachable from the testing location. Self-hosted servers may also need router port-forwarding.
- HTTP: allow and forward port 80 to the proxy host.
- HTTPS: allow and forward port 443 to the proxy host.
- Proxy-to-Dynmap: ensure the proxy host can reach Dynmap’s upstream address and port, even if the upstream port is not publicly exposed.
Cloud security groups, operating-system firewalls, and home routers can each block a connection. Check all applicable layers rather than assuming that a successful DNS lookup means the port is open. If the proxy and Dynmap share one machine, binding Dynmap to its local interface and exposing only 80 and 443 publicly can reduce unnecessary direct exposure; follow the bind-address options available in your Dynmap configuration and host.
Configure trusted proxies only when needed
Dynmap’s configuration reference documents trusted-proxies for deployments that need forwarded client-IP handling, such as IP-based username recognition. Loopback addresses are shown as defaults. Do not broaden this setting simply because a proxy exists; configure trusted proxies when your deployment actually relies on the forwarded client address, and list only proxy addresses you control. Trusting arbitrary forwarded headers can make client-IP-based behavior unreliable.
Operational checks after it works
Test the complete path from outside the server’s local network when possible. A local browser can succeed through a local route while an Internet visitor is blocked by the router or an upstream firewall. Test both the HTTP hostname and the HTTPS hostname, then test the direct Dynmap URL separately so you know which layer is healthy.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Record the final values in one place: the public hostname, DNS target, Dynmap port, proxy host, and whether the certificate is installed. If a shared host changes the assigned port, update the proxy’s upstream and restart Minecraft after changing Dynmap’s configuration. If the public IP changes, update DNS; the proxy configuration normally remains the same as long as the hostname and internal route are unchanged.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting by symptom
| Symptom | Likely cause | What to check |
|---|---|---|
| Direct IP URL fails | Dynmap is not running, the port is wrong, or a firewall/port-forward blocks it. | Read the server log for a successful web-server start, confirm webserver-port, and test locally before changing DNS. |
| Domain does not resolve | Missing or incorrect A record, or DNS changes are still propagating. |
Verify that the record’s value is the proxy server’s public IP and allow for the provider’s TTL. |
| Browser times out on the domain | Port 80 or 443 is blocked by a host firewall, cloud security group, or router. | Open and forward the port that matches the URL scheme, then test again. |
| Nginx or Apache shows its default page | The request hostname does not match the configured virtual host. | Compare the browser hostname, DNS record, and Nginx server_name or Apache virtual host name character for character. |
| 502 Bad Gateway | The proxy cannot connect to Dynmap’s upstream. | Confirm Dynmap is running and listening on the configured port; the documented default target is localhost:8123. Check the proxy host’s local connectivity and any firewall rule between proxy and Dynmap. |
| HTTP works but HTTPS fails | Port 443 is closed, the certificate does not include the hostname, or the TLS virtual host is incomplete. | Allow/forward 443, inspect the certificate name, and verify the HTTPS virtual-host configuration. |
| Certificate issuance fails | The hostname does not yet resolve to the proxy, or port 80 validation cannot reach the server. | Correct DNS first and ensure port 80 is reachable from the Internet. |
| Map loads but client IP or username behavior is wrong | Forwarded headers are absent or Dynmap does not trust the proxy address. | Keep the documented proxy headers, then configure trusted-proxies only for the proxy addresses required by your setup. |
| Nginx will not restart after editing | A syntax error or invalid directive was introduced. | Run sudo service nginx configtest, correct the reported line, test again, and restart only after validation succeeds. |
Frequently asked questions
Frequently Asked Questions
How do I use my own domain instead of the Dynmap IP?
Create an A record for the chosen hostname pointing to the proxy server’s public IP, then configure Nginx or Apache to forward that hostname to Dynmap’s configured webserver port. Verify Dynmap directly first so DNS and proxy testing are not hiding an application problem.
Can I put Dynmap on map.example.com?
Yes. Add an A record named map (the exact label used by your DNS provider), set the proxy’s server_name or Apache virtual host to map.example.com, and request a certificate for that same hostname if you use HTTPS.
How do I remove :8123 from the Dynmap URL?
Put a reverse proxy on port 80 and/or 443 and set its upstream to Dynmap, normally http://localhost:8123/. Visitors then use the standard HTTP or HTTPS URL; 8123 remains an internal upstream port.
Rank #4
- Intel Core i7-6700T
- 32GB RAM
- 1TB SSD
- USB WIFI dongle, USB mouse, USB keyboard included
- Windows 11 Professional 64-bit
Does adding a domain change Dynmap’s port?
No. The domain changes how visitors reach the service. Dynmap keeps listening on webserver-port, which is 8123 by default unless a host assigned another port. Restart Minecraft after changing that setting.
Should I expose port 8123 publicly after installing Nginx?
Direct exposure is needed for direct external testing, but the proxy can connect locally or over a private network once it works. You can limit public access to the proxy’s 80 and 443 ports if your network design permits it.
Should I choose Nginx or Apache?
Use the server you already administer. Nginx uses a location block and proxy headers; Apache uses ProxyPass and ProxyPassReverse and requires the rewrite and proxy_http modules on Debian or Ubuntu. Both can present the same custom hostname and terminate TLS.
Can I use the root domain instead of a subdomain?
Yes. Many DNS dashboards represent the root record with @. Point that A record to the appropriate public IP and use the exact root hostname in the proxy configuration and certificate. A root-domain record and a map subdomain are separate names.
Why does the domain show my web server’s default page?
The request is reaching the proxy, but its hostname does not select the Dynmap virtual host. Compare the browser URL, DNS name, Nginx server_name or Apache virtual host, and certificate name character for character.
Why do I get a 502 Bad Gateway?
The proxy cannot reach Dynmap. Confirm the Minecraft server is running, Dynmap reported a successful web-server start, the configured port is correct, and the proxy host can connect to the upstream address. The standard example is localhost:8123.
Do I need HTTPS?
HTTPS is optional for the proxy, but it requires a certificate and an Internet-reachable port 443. Port 80 is also commonly needed for HTTP access and certificate validation. Dynmap can remain on ordinary HTTP behind the proxy.
Why does certificate issuance fail even though DNS looks correct?
The hostname may resolve to the wrong public IP, or port 80 may be blocked by a host firewall, cloud security group, or router. Correct the A record and make the proxy reachable from the Internet before retrying.
When should I configure trusted-proxies?
Only when your deployment depends on forwarded client-IP handling, such as IP-based username recognition. Add only proxy addresses you control; the configuration reference shows loopback addresses as defaults.
The Bottom Line
First make Dynmap work directly on its configured port. Then point an A record at the proxy host, configure Nginx or Apache to forward the chosen hostname to Dynmap, validate the proxy configuration, and open the required firewall and router ports. Add a certificate at the proxy for HTTPS; the internal 8123 port remains unchanged.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
