Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesEnable IP forwarding on both sides of the connection: set ip_forward: true in the BungeeCord proxy’s config.yml, set settings: bungeecord: true in spigot.yml on every backend server, then restart the proxy and all backends. If either side is left unchanged, Spigot can continue seeing the proxy address or construct the wrong player UUID.
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.
What BungeeCord IP forwarding does
A BungeeCord network has two connections for each player. The player connects to the proxy, and the proxy opens a second connection to the selected Spigot server. By default, the backend connection originates from the proxy, so the backend may identify the proxy as the connecting address instead of the player’s real address.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →IP forwarding adds the player’s original address to the proxy-to-backend handshake. Spigot can then expose the actual address to server-side plugins and logs. The same setting also forwards the player’s true online-mode UUID instead of allowing an offline-mode username hash to be used as the backend identity.
That distinction affects bans, moderation tools, audit logs, permissions and player data. A network that uses address-based bans can otherwise ban the proxy rather than the player, while UUID-based data can appear under a different identity when a player moves between proxy-connected and directly connected contexts.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Prerequisites and scope
- A working BungeeCord proxy with at least one Spigot backend.
- Access to the proxy’s generated
config.yml. - File access to
spigot.ymlon every backend that players can reach through the proxy. - Permission to stop and start, or otherwise restart, the proxy and each backend.
Use the file structure generated by the versions you installed. Keep unrelated settings intact; change only the forwarding entries unless you have another reason to edit the file.
The SpigotMC Wiki described BungeeCord #711 and later together with Spigot 1.7 #5 and later as requiring manual forwarding on both the proxy and Spigot. Those figures are historical context from the 2018 guide, not a guarantee of compatibility for every current BungeeCord fork, Spigot build or Paper-based server. Modern projects can change configuration names, defaults or supported forwarding modes, and there is no single compatibility matrix covering every combination.
Recommended Free Tools
How the two-sided configuration works
| Component | File | Setting | Purpose |
|---|---|---|---|
| BungeeCord proxy | config.yml |
ip_forward: true |
Places the player’s original address and online-mode UUID into the proxy-to-backend connection. |
| Each Spigot backend | spigot.yml |
settings: bungeecord: true |
Tells Spigot to accept and use the forwarding data supplied through the BungeeCord path. |
Both flags describe one trust relationship. The proxy must send the data, and each backend must be configured to interpret it. Enabling only one side leaves the network incompletely configured and can produce the same symptoms as having forwarding disabled.
Step-by-step setup
1. Back up the configuration files
Before editing, make a copy of the proxy config.yml and every backend spigot.yml. A backup gives you a known rollback point if indentation changes, a version-specific format differs, or a later troubleshooting step requires returning to the previous state.
2. Enable forwarding in BungeeCord
- Stop the proxy if your installation requires it for safe file editing, and open the BungeeCord proxy’s
config.yml. - Find the top-level
ip_forwardentry. In a standard generated file, it should be a Boolean value rather than a quoted string. - Set it exactly as follows:
ip_forward: true
Keep the entry at the same indentation level used by the generated file. YAML is indentation-sensitive, so do not nest this key under listeners, servers or another section unless your installed configuration explicitly places it there.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
3. Enable BungeeCord mode on every Spigot backend
- Open
spigot.ymlon the first backend. - Under the existing
settings:section, setbungeecordtotrue:
settings:
bungeecord: true
Do not create a second settings: block if one already exists. Add or edit the key inside the existing block and preserve the rest of the file. Repeat this edit on every Spigot server that receives players through the proxy, including lobby, hub, minigame and fallback servers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Save and restart the complete network
Save the proxy file and all backend files. Restart the BungeeCord proxy and every Spigot backend; a plugin reload or a configuration-only reload is not a reliable substitute for restarting the processes. Restarting both sides ensures that the proxy loads its forwarding mode and each backend loads its acceptance mode before the next player connection is created.
If you run several backends, restart them all rather than testing one changed server while other servers still use the old configuration. A player moved between differently configured servers can otherwise appear to have inconsistent address or UUID information.
Configuration examples
Proxy config.yml
ip_forward: true
This is a top-level proxy setting. Leave the listener, server list, permissions and other generated entries in place.
Each backend spigot.yml
settings:
bungeecord: true
The snippet shows the required nesting, not a complete spigot.yml. Your file may contain many additional settings under settings:; change only the Boolean value for bungeecord.
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 & 11Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Verify that forwarding is actually working
Verification must follow the same route real players use. A direct connection to a backend bypasses the proxy and cannot prove that BungeeCord forwarding is configured correctly.
- Start the proxy and all configured backends after saving the files.
- Connect to the BungeeCord listener, not to a backend’s direct address.
- Join a backend through the proxy and identify which backend handled the connection.
- Use a server-side plugin or a server log that reports the connecting player’s address and UUID.
- Confirm that the reported address is the player’s actual address rather than the proxy address.
- Confirm that the UUID is the player’s online-mode UUID, not an offline-mode username hash.
- Repeat the check on each backend, because one server can still have an incorrect
spigot.ymleven when another server works.
Use a controlled test account where possible and record the result from the same connection path each time. A direct backend test, a proxy test and a test performed before a restart are different tests and should not be treated as interchangeable.
Troubleshooting by symptom
The backend still logs the proxy address
- Open the proxy’s
config.ymland verify that the active proxy instance hasip_forward: true. - Open
spigot.ymlon the specific backend handling the player and verifysettings.bungeecord: true. - Check for duplicate keys or an incorrectly indented entry. YAML parsers use the effective structure, not the position you intended.
- Confirm that both the proxy and that backend were restarted after the edit.
- Reconnect through the proxy listener and check the address again.
Do not assume that changing the proxy file fixes every backend. The acceptance flag is stored separately on each Spigot server.
The UUID is unexpected or player data appears under a second identity
Check both flags and the connection route. The proxy forwards the true online-mode UUID only when its forwarding option is enabled, and Spigot uses that data only when BungeeCord mode is enabled. A player who connected directly to a backend, or who connected before the complete restart, may have data created under a different identity. Test again through the proxy after both sides are running the new settings.
One backend works while another does not
Treat this as a per-backend configuration issue first. Compare the working and failing servers’ spigot.yml files, paying particular attention to the existing settings: block and indentation. Verify that the proxy’s server entry routes the test player to the backend you think it does, then restart the failing backend and retest through the proxy.
Rank #4
- Dual Converters, Infinite Potential:Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
The change appears to have no effect
- Make sure you edited the configuration directory used by the running process, not an archived copy or a different server instance.
- Check startup output for YAML parsing errors or a process that failed to restart.
- Ensure the value is the Boolean
true, not text with unusual quoting or capitalization. - Verify that your test connection enters through BungeeCord rather than using a saved direct backend address.
If a configuration error prevents startup, restore the backup, correct the indentation or key placement, and restart again. Do not remove unrelated settings while diagnosing a forwarding problem.
Security: forwarding is trusted identity data
Forwarding works because Spigot trusts the proxy path to supply the player’s address and UUID. That trust is appropriate only when backend connections are controlled. If an arbitrary Internet client can connect directly to a backend listener, it may bypass the proxy path or send traffic that the backend was not intended to accept.
Keep backend listener ports inaccessible to untrusted clients and allow connections from the proxy or a trusted private network. The exact firewall, bind-address and hosting arrangement depend on your operating system, provider and topology; there is no single universal firewall rule that fits every BungeeCord deployment. The important requirement is that normal players reach the backend through the proxy, while direct public access is blocked or otherwise restricted.
Free tools Windows power users keep installed
One-click scans. No signup required.
After applying network restrictions, test from an ordinary player connection and from an administrator path used for maintenance. Ensure that staff still have a deliberate, documented way to reach a backend for console or maintenance work without exposing the gameplay listener to the public Internet.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Operational choices and limitations
Apply the setting consistently
Forwarding is a network-wide policy, not a cosmetic option for the lobby. Every backend that can receive a proxied player should use the same intended mode. Keep a written inventory of backend names and configuration locations so a newly added server does not silently run with a different identity model.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Understand what forwarding does not do
- It does not replace authentication or make a backend safe to expose publicly.
- It does not configure firewall rules, proxy listeners or server routing.
- It does not retroactively rewrite UUIDs or player records already created under another identity.
- It does not make a direct backend connection equivalent to a proxied connection.
Those are separate operational concerns. Forwarding supplies identity information during the proxy-to-backend handshake; it does not solve every networking or account-management problem around a proxy network.
Version context and proxy alternatives
The documented historical prerequisite was BungeeCord #711 or newer with Spigot 1.7 #5 or newer, as stated by the SpigotMC Wiki in 2018. Current BungeeCord forks and current Spigot or Paper releases may have different support details, defaults and security recommendations. Check the documentation for the exact proxy and server builds you operate before copying assumptions from an older guide.
When evaluating a different proxy technology, compare more than the name of the forwarding switch. The meaningful questions are which forwarding mode is used, how the backend authenticates or trusts forwarded data, whether backend configuration is required, how online UUIDs are handled, which server versions are supported, and how backend network isolation is enforced. The two-file procedure in this guide describes the legacy BungeeCord configuration model and should not be transplanted unchanged to another proxy.
Maintenance checklist
- Back up
config.ymland every backendspigot.ymlbefore edits. - Confirm
ip_forward: truein the active BungeeCord proxy configuration. - Confirm
settings.bungeecord: truein every relevant Spigot backend. - Preserve YAML indentation and avoid duplicate keys or duplicate
settings:sections. - Restart the proxy and all backends after saving.
- Test through the BungeeCord listener, never only through a direct backend address.
- Check both the reported address and UUID on each backend.
- Restrict backend listeners to the proxy or a trusted network.
- Recheck the settings whenever a backend is cloned, replaced or upgraded.
Bottom line
Correct BungeeCord IP forwarding is a coordinated proxy-and-backend change: ip_forward: true in the proxy, bungeecord: true under settings on every Spigot backend, a full restart, and a test made through the proxy listener. Once those pieces agree and backend ports are kept away from untrusted clients, Spigot can receive the player’s real address and online-mode UUID instead of the proxy address or an offline-mode identity.
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.

