can't bind to port (java null exception)

[shithubsucks]

I'm unable to bind to any ports with velocity-3.3.0-SNAPSHOT-371. When I try I get a big error:

[22:50:00 INFO]: Booting up Velocity 3.3.0-SNAPSHOT (git-75d6dcc1-b371)... [22:50:00 INFO]: Loading localizations... [22:50:00 INFO]: Connections will use NIO channels, Java compression, Java ciphers [22:50:00 WARN]: Player info forwarding is disabled! All players will appear to be connecting from the proxy and will have offline-mode UUIDs. [22:50:00 INFO]: Loading plugins... [22:50:00 INFO]: Loaded 0 plugins [22:50:00 WARN] [io.netty.util.internal.MacAddressUtil]: Failed to find a usable hardware address from the network interfaces; using random bytes: 6c:2e:44:ef:40:00:69:48 [22:50:00 ERROR]: Can't bind to /[0:0:0:0:0:0:0:0]:25547 java.nio.channels.UnsupportedAddressTypeException: null at java.base/sun.nio.ch.Net.checkAddress(Net.java:149) ~[?:?] at java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:337) ~[?:?] at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:301) ~[?:?] at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:141) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:562) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1334) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:260) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:380) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[velocity-3.3.0-SNAPSHOT-371.jar:3.3.0-SNAPSHOT (git-75d6dcc1-b371)] at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] [22:50:00 INFO]: Done (0.84s)!

my velocity.toml:
`# Config version. Do not change this
config-version = "2.6"

What port should the proxy be bound to? By default, we'll bind to all addresses on port 25577.

bind = "[::]:25547"

What should be the MOTD? This gets displayed when the player adds your server to

their server list. Only MiniMessage format is accepted.

motd = "<#09add3>A Velocity Server"

What should we display for the maximum number of players? (Velocity does not support a cap

on the number of players online.)

show-max-players = 500

Should we authenticate players with Mojang? By default, this is on.

online-mode = true

Should the proxy enforce the new public key security standard? By default, this is on.

force-key-authentication = true

If client's ISP/AS sent from this proxy is different from the one from Mojang's

authentication server, the player is kicked. This disallows some VPN and proxy

connections but is a weak form of protection.

prevent-client-proxy-connections = false

Should we forward IP addresses and other data to backend servers?

Available options:

- "none": No forwarding will be done. All players will appear to be connecting

from the proxy and will have offline-mode UUIDs.

- "legacy": Forward player IPs and UUIDs in a BungeeCord-compatible format. Use this

if you run servers using Minecraft 1.12 or lower.

- "bungeeguard": Forward player IPs and UUIDs in a format supported by the BungeeGuard

plugin. Use this if you run servers using Minecraft 1.12 or lower, and are

unable to implement network level firewalling (on a shared host).

- "modern": Forward player IPs and UUIDs as part of the login process using

Velocity's native forwarding. Only applicable for Minecraft 1.13 or higher.

player-info-forwarding-mode = "NONE"

If you are using modern or BungeeGuard IP forwarding, configure a file that contains a unique secret here.

The file is expected to be UTF-8 encoded and not empty.

forwarding-secret-file = "forwarding.secret"

Announce whether or not your server supports Forge. If you run a modded server, we

suggest turning this on.

If your network runs one modpack consistently, consider using ping-passthrough = "mods"

instead for a nicer display in the server list.

announce-forge = false

If enabled (default is false) and the proxy is in online mode, Velocity will kick

any existing player who is online if a duplicate connection attempt is made.

kick-existing-players = false

Should Velocity pass server list ping requests to a backend server?

Available options:

- "disabled": No pass-through will be done. The velocity.toml and server-icon.png

will determine the initial server list ping response.

- "mods": Passes only the mod list from your backend server into the response.

The first server in your try list (or forced host) with a mod list will be

used. If no backend servers can be contacted, Velocity won't display any

mod information.

- "description": Uses the description and mod list from the backend server. The first

server in the try (or forced host) list that responds is used for the

description and mod list.

- "all": Uses the backend server's response as the proxy response. The Velocity

configuration is used if no servers could be contacted.

ping-passthrough = "DISABLED"

If not enabled (default is true) player IP addresses will be replaced by in logs

enable-player-address-logging = true

[servers]

Configure your servers here. Each key represents the server's name, and the value

represents the IP address of the server to connect to.

lobby = "127.0.0.1:30066"
factions = "127.0.0.1:30067"
minigames = "127.0.0.1:30068"

In what order we should try servers when a player logs in or is kicked from a server.

try = [
"lobby"
]

[forced-hosts]

Configure your forced hosts here.

"lobby.example.com" = [
"lobby"
]
"factions.example.com" = [
"factions"
]
"minigames.example.com" = [
"minigames"
]

[advanced]

How large a Minecraft packet has to be before we compress it. Setting this to zero will

compress all packets, and setting it to -1 will disable compression entirely.

compression-threshold = 256

How much compression should be done (from 0-9). The default is -1, which uses the

default level of 6.

compression-level = -1

How fast (in milliseconds) are clients allowed to connect after the last connection? By

default, this is three seconds. Disable this by setting this to 0.

login-ratelimit = 3000

Specify a custom timeout for connection timeouts here. The default is five seconds.

connection-timeout = 5000

Specify a read timeout for connections here. The default is 30 seconds.

read-timeout = 30000

Enables compatibility with HAProxy's PROXY protocol. If you don't know what this is for, then

don't enable it.

haproxy-protocol = false

Enables TCP fast open support on the proxy. Requires the proxy to run on Linux.

tcp-fast-open = false

Enables BungeeCord plugin messaging channel support on Velocity.

bungee-plugin-message-channel = true

Shows ping requests to the proxy from clients.

show-ping-requests = false

By default, Velocity will attempt to gracefully handle situations where the user unexpectedly

loses connection to the server without an explicit disconnect message by attempting to fall the

user back, except in the case of read timeouts. BungeeCord will disconnect the user instead. You

can disable this setting to use the BungeeCord behavior.

failover-on-unexpected-server-disconnect = true

Declares the proxy commands to 1.13+ clients.

announce-proxy-commands = true

Enables the logging of commands

log-command-executions = false

Enables logging of player connections when connecting to the proxy, switching servers

and disconnecting from the proxy.

log-player-connections = true

[query]

Whether to enable responding to GameSpy 4 query responses or not.

enabled = false

If query is enabled, on what port should the query protocol listen on?

port = 25577

This is the map name that is reported to the query services.

map = "Velocity"

Whether plugins should be shown in query response by default or not

show-plugins = false`

[shithubsucks]

Nevermind. Apparently this is openJDK's fault. According to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239890 newer versions of OpenJDK default with java.net.preferIPv4Stack=True. I have no idea why. Putting -Djava.net.preferIPv6Addresses=true -Djava.net.preferIPv4Stack=false in the cmdline fixes the issue.