Internal exception io.netty.handler.codec.decoderexception: net.minecraft server.v1_14_R1.ResourceKeyInvalidException: Non [a-z0-9/.-] character in path of location: legacy:bjmlrequest

Every server on 1.14.4 spigot or paper just has this error:
internal exception io.netty.handler.codec.decoderexception: net.minecraft server.v1_14_R1.ResourceKeyInvalidException: Non [a-z0-9/.-] character in path of location: legacy:bjmlrequest

Nothing wrong with the server because I made a brand new server, tried a different port and still got the error. What is happening?

My plugins on waterfall are:
BungeeTabListPlus
BungeeJoinMessages
BungeeHub
BungeeCompass
Viaversion

They are all up to date (im pretty sure)

Maybe cause this the Viaversion plugin.
https://hub.spigotmc.org/jira/browse/SPIGOT-4115

Ok thanks, but I need viaversion what are the alternatives?

How can i fix this?

Waterfall already supported 1.14.4-1.8

If you need 1.7.10 version support I recommend use the Tavertine.
https://papermc.io/downloads#Travertine

If you need support older versions try the ProtocolSupportBungee.
https://build.true-games.org/job/ProtocolSupportBungee/

ok do I remove viaversion on all my servers or just waterfall because I needsome servers to be 1.14.4 and some to be 1.8-1.14.4. And when I removed viaversion from waterfall, it worked but i still cant join my 1.14.4 servers. And the server I want to be 1.14.4 has the same error.

Oh and I found this in my console if it will help!

https://pastebin.com/kJVviuE1

This message is injected by some client mod. If you use vanilla, you would never experience this issue.

The issue is in part because BungeeCord and Waterfall do not correctly map legacy channel names, using invalid identifiers. It’s not strictly a ViaVersion issue.

The easy fix is to remove ViaVersion from the proxy and instead use ProtocolSupport + ViaVersion on your backend servers. If you can’t do that, you can try Velocity (shameless plug, I’m the creator and main developer) which has this behavior fixed, has a ViaVersion port, and won’t go haywire with mods in general, should you rely on/use them.

Do you have discord? I actually only have this problem on one server and I can’t seem to fix it. I don’t want to use Velocity because it’s not what i’m famillar with. I removed viaversion from the proxy and added ProtocolSupport it didn’t do anything.

Add me on discord: HydroFlare#2207