-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If "enable-status" is false, the connection to the backend server will fail #64
Comments
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. |
I found the cause. 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. |
For now, I will reopen this issue, but feel free to close it if it not fixed. Sorry if this is a series of bad English. I'm not a native English speaker. |
Describe the bug
When
enable-status
inserver.properties
is false,Failed to connect
is displayed.To Reproduce
enable-status
inserver.properties
to false.Expected behavior
The player will be successfully connected to the backend server.
Screenshots
Desktop (please complete the following information):
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:
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.
The text was updated successfully, but these errors were encountered: