Minecraft does not generate extra network ports for plugins. You obtain an unused port from your hosting panel or router, assign it to the server, set that same port in the plugin’s configuration file, open the correct firewall protocol, and restart the server. Dynmap normally uses TCP port 8123, Geyser normally uses UDP port 19132, and a Velocity proxy listens on the address defined by its bind setting.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
What an “additional port” actually is
A network port is an endpoint through which a service accepts traffic. Your Minecraft Java server already has a primary connection port. A plugin that provides another service—such as a browser map, Bedrock connectivity, or a proxy listener—needs a separate endpoint unless its design explicitly uses an existing listener.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The important distinction is between allocating a port and configuring a port:
- Allocation: Your hosting provider reserves and routes a port to the server, or you create a router-forwarding rule on a self-hosted machine.
- Configuration: You enter that port in the plugin’s own configuration file.
- Access control: The host firewall, operating-system firewall, and router must allow the right protocol to reach it.
Changing a number in a plugin file without obtaining a routed port first does not make the service reachable. Conversely, allocating a port without changing the plugin configuration leaves the plugin listening on its old value.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Check these prerequisites before editing files
Confirm that your host exposes extra ports
In a managed panel, look for a section named Network, Allocations, or Additional ports. Pterodactyl-style panels commonly let an administrator attach an allocation to a server. For HTTP-based map plugins such as Dynmap and BlueMap, the allocation may need an unfiltered port option enabled; otherwise a web request can be blocked before it reaches the plugin.
If your provider does not offer an additional allocation, you cannot make an external client reach that service merely by editing a file. Ask the provider whether an allocation can be added or use a host where you control the network.
Self-hosted servers need router forwarding
On a home or office network, choose an unused port and create a router rule that forwards it to the machine running Minecraft. The rule must identify the internal server address and the same protocol the plugin uses. A rule for TCP does not forward UDP traffic, and a UDP rule does not forward TCP traffic.
Record the protocol, not just the number
TCP and UDP are separate transport protocols. Dynmap’s web server uses TCP. Geyser’s Bedrock listener uses UDP. A Bedrock listener cannot share its UDP port with another UDP service, such as voice chat or a query service. Keep a written inventory of port, protocol, purpose, and destination before making changes.
Back up configuration files
Stop or suspend automated restarts while editing, then copy the relevant configuration file. YAML and TOML are indentation- and syntax-sensitive, so a backup gives you a direct recovery path if the server fails to start.
Procedure: allocate, configure, open, and test a port
- Choose the service. Identify whether you are publishing a web map, accepting Bedrock connections, or running a proxy listener. This determines the configuration file and protocol.
- Obtain an unused allocation. In a hosting panel, add or request an allocation and note its IP address and port. On a self-hosted network, reserve a port and forward it from the router to the Minecraft machine.
- Check for conflicts. Make sure no other plugin or process already listens on that port and protocol. A port can be free for TCP while occupied for UDP, but two services still cannot bind the same protocol and address combination.
- Edit the plugin file. Use the exact key and path documented below for the plugin and server platform. Preserve quotation marks, indentation, and surrounding syntax.
- Save and restart the server. Most of these listeners are created during plugin startup. A live reload may leave the old socket active or fail to create the new one.
- Allow the protocol through firewalls. Add a TCP rule for Dynmap or a UDP rule for Geyser. Apply the same protocol in the router-forwarding rule if the server is behind NAT.
- Verify locally first. Read the startup log for the listener address and port. A local test separates a plugin configuration error from a host-routing problem.
- Test externally. From a device outside the server’s LAN, open the map URL or attempt a Bedrock connection using the allocated address and port. If it fails, troubleshoot in the order listed below rather than changing several settings at once.
Plugin port settings and defaults
| Plugin | Configuration key | File | Default or example | Protocol |
|---|---|---|---|---|
| Dynmap | webserver-port |
plugins/dynmap/configuration.txt(mods: dynmap/configuration.txt) |
8123 default |
TCP |
| Geyser | Bedrock port in the bedrock section |
Spigot: plugins/Geyser-Spigot/config.ymlFabric: config/Geyser-Fabric/config.ymlNeoForge: config/Geyser-NeoForge/config.yml |
19132 default |
UDP |
| Velocity | bind |
velocity.toml |
0.0.0.0:25577 in the documented example |
TCP |
Defaults can change between plugin releases. Treat the values above as the defaults or example identified in the October 14, 2026 reference material, then confirm the generated file for the version you actually run.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Dynmap: add a browser map port
1. Allocate a TCP port
Request an additional host allocation or create a router-forwarding rule for TCP. Dynmap’s web interface is separate from the Minecraft gameplay port, so visitors need the map address and the newly allocated port.
2. Set webserver-port
Open plugins/dynmap/configuration.txt. Modded installations use dynmap/configuration.txt. Find webserver-port and replace its value with the allocated port. Do not change unrelated web-server settings while diagnosing connectivity.
3. Restart and read the log
After restart, a successful listener reports a line in this form:
[dynmap] Web server started on address 0.0.0.0:8123The number in the message should match your configured port; if you selected another value, the log should show that value instead. If the message still shows 8123, the wrong file was edited, the change was not saved, or the plugin regenerated its configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Open the map
Use the host’s public address and the Dynmap port in a browser. If the server is behind a router, test from outside the local network so that the forwarding rule is actually exercised. A browser timeout usually points to allocation, firewall, or forwarding; a Dynmap startup error points to the plugin or file syntax.
Geyser: add a Bedrock crossplay port
1. Reserve a UDP allocation
Geyser’s Bedrock listener uses UDP and defaults to port 19132. Reserve a separate UDP port if that default is unavailable. Do not assign the same UDP port to voice chat, query, or another Bedrock-facing service.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
2. Edit the platform-specific configuration
For a Spigot-based server, edit plugins/Geyser-Spigot/config.yml. Fabric installations use config/Geyser-Fabric/config.yml, and NeoForge installations use config/Geyser-NeoForge/config.yml. In the bedrock section, set the port to the value allocated by the host or forwarded by the router.
3. Check clone-remote-port
When clone-remote-port is enabled, Geyser overwrites the Bedrock port with the Java port each time it starts. If you need a fixed, separate Bedrock port, leave this option disabled. Otherwise, a correct manual port can appear to “revert” after every restart.
Recommended Free Tools
4. Allow UDP and run the connection test
Open the selected UDP port in the host and operating-system firewalls. Geyser provides the console command:
geyser connectiontest <ip> <port>Replace <ip> and <port> with the address and UDP port you want to test. Run the command after restart and compare its result with an external Bedrock connection attempt. If the command succeeds but players cannot connect, inspect the public address, router rule, and provider allocation.
Velocity: configure the proxy listener
Set the proxy’s bind address
Velocity’s listener is defined in velocity.toml. The example 0.0.0.0:25577 binds on all local interfaces at TCP port 25577. Replace the port with the allocation supplied by your host, or use the address and port appropriate for your network design.
Velocity is different from Dynmap and Geyser: its bind value is the proxy’s primary client-facing listener, not an extra listener created by a plugin on an already-running backend. If you operate several proxies, each one needs an address and port combination that does not conflict with another listener.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Configure backend trust separately
Each backend Paper server also needs a velocity block with the shared secret in paper-global.yml. That secret and forwarding configuration allow the backend to work with the proxy; they are separate from allocating an additional web or Bedrock port. Changing a Dynmap or Geyser port does not replace the Velocity-to-backend configuration.
Planning several plugins on one server
Count listeners per server rather than assuming one spare port covers every plugin. A Velocity network that runs Dynmap and Geyser on each backend can require several unused allocations: one TCP web port for each Dynmap instance, one UDP Bedrock port for each Geyser instance, and the proxy’s TCP listener.
| Service layout | Ports to plan | Why |
|---|---|---|
| One standalone server with Dynmap | One additional TCP port | Dynmap’s browser web server listens separately from gameplay. |
| One standalone server with Geyser | One additional UDP port | Bedrock clients connect through Geyser’s UDP listener. |
| One server with Dynmap and Geyser | One TCP port and one UDP port | The services use different protocols and separate configuration keys. |
| Velocity proxy plus backend map and Bedrock services | Proxy TCP listener, plus each backend’s required TCP and UDP listeners | The proxy listener and backend plugin listeners serve different roles. |
Keep a per-server inventory containing the allocation, protocol, internal destination, configuration key, and last verification date. This prevents a later plugin installation from silently reusing a port already assigned to another service.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →BlueMap and Plan: do not guess the setting
The available reference material does not verify BlueMap’s web-server file, port key, default, or protocol. One excerpt associates a port value with plugins/BlueMap/webserver.conf, but that entry is not sufficiently verified to use as a universal instruction. Check the configuration generated by the exact BlueMap version and server platform before allocating a port.
The location and key for Plan’s web port are likewise unresolved. Do not assume that Plan uses Dynmap’s file, port, or protocol. Use the configuration shipped with your Plan version or the host’s documented support route; if no extra allocation is available, changing an assumed key will not expose the dashboard.
Firewall and routing checklist
- Confirm the host allocation points to the correct server instance.
- Match the firewall protocol to the plugin: TCP for Dynmap and the Velocity listener; UDP for Geyser.
- On a router, forward the public port to the Minecraft machine’s current private address.
- Ensure another service is not already bound to the same protocol and port.
- Test from outside the local network; a test from the server itself can succeed even when public routing is broken.
- If a provider uses an unfiltered allocation option for HTTP map services, enable it for the map port.
When a connection fails, check the host or router first. A correctly edited configuration cannot accept traffic that the upstream network never routes to the machine.
Restart verification and failure diagnosis
The plugin starts on the old port
- Verify that you edited the correct platform path and not a similarly named backup file.
- Search the file for duplicate keys; a later duplicate may override the first value.
- Check whether a startup option such as Geyser’s
clone-remote-portrewrites the value. - Restart fully rather than relying on a reload command.
The server reports that the address is already in use
Another process has the same protocol and port, or a previous process did not shut down cleanly. Stop the conflicting service, choose a different allocation, and restart. Do not solve a TCP conflict by changing only the firewall; the listener conflict occurs before firewall rules matter.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, 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 minuteThe log shows the listener, but clients time out
This usually indicates a routing or firewall path problem. Confirm the allocation, public address, protocol, host firewall, operating-system firewall, and router-forwarding destination in that order. For Dynmap, verify that the web allocation is not filtered. For Geyser, verify UDP specifically; a successful TCP test does not prove that UDP is reachable.
Local access works but external access fails
The plugin is probably listening correctly, while the public path is not. Check NAT forwarding, the server’s private IP address, and whether your provider assigns a public address that accepts inbound traffic. Ask the host to confirm that the allocation is attached to the correct container or server.
Geyser players still reach the Java port
Inspect clone-remote-port and the bedrock section after restart. If cloning is enabled, Geyser will replace the separate Bedrock value with the Java port. Disable cloning when the Bedrock listener must remain on its own UDP allocation.
Operational practices that prevent recurring port problems
- Store a backup of each configuration file before changing a port.
- Document every allocation with its protocol and service owner.
- Apply one port change at a time, then restart and verify the startup log.
- Use the plugin’s own diagnostic output where available, including Geyser’s
connectiontest. - Recheck paths and defaults after upgrading a plugin, mod loader, or server platform; the October 14, 2026 reference values are not a promise that every future release will use the same files.
- Remove unused allocations and firewall rules when a service is retired, so old listeners are not left exposed.
The reliable sequence is always the same: obtain a routed allocation, set the plugin’s documented key, restart, allow the correct protocol, and test from the network where real users will connect.
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.
