If "enable-status" is false, the connection to the backend server will fail

[viasnake]

Describe the bug
When enable-status in server.properties is false, Failed to connect is displayed.

To Reproduce

1. Set up Velocity & Catalyst.
2. Set enable-status in server.properties to false.
3. Failed to connect.

Expected behavior
The player will be successfully connected to the backend server.

Screenshots

Desktop (please complete the following information):

• Velocity Version: 1.1.5
• Catalyst Version: 0.3.2
• Additional Plugins installed on velocity: Anvil 0.3.0

Additional context
This issue does not occur with Velocity alone, so you may want to mark it as a bug. If this is not fixed, it might be a good idea to provide a FAQ.

This issue is a bit tricky for the following reasons:

• No errors will be output to the console at all.
• Console of the backend server will log as if the player connected for a moment and then immediately disconnected.

Almost certainly, the following checks are causing this issue.
https://github.com/AnvilPowered/Catalyst/blob/088793a6de30fe200169ef365a1a8a319c127492/catalyst-velocity/src/main/java/org/anvilpowered/catalyst/velocity/listener/VelocityListener.java#L119-L120

However, simply removing this check does not seem like a good idea. I don't understand Java and Velocity, so I can't come up with a good solution.

[viasnake]

I don't know why this happens, but redoing everything will fix it. I can tell you for sure that this is not caused by Proxy_Protocol.
If I can identify the cause I will open the issue again.

[viasnake]

I found the cause.
When "enable-status" in "server.properties" is false, "Failed to connect" is displayed.
Usually "enable-status" is true by default, but I changed it to false for some reason. In any case, if you get the "Failed to connect" message as well, it is worth checking this setting.

Also, this issue does not occur with Velocity alone, so you may want to mark it as a bug. If this is not fixed, it might be a good idea to provide a FAQ.

[viasnake]

For now, I will reopen this issue, but feel free to close it if it not fixed.
A solution does exist for this issue. It's just hard to notice that it exists, and it doesn't affect most servers.

Sorry if this is a series of bad English. I'm not a native English speaker.