Skip to content
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

Broken with Velocity #54

Closed
greysilly7 opened this issue Jun 9, 2021 · 8 comments
Closed

Broken with Velocity #54

greysilly7 opened this issue Jun 9, 2021 · 8 comments

Comments

@greysilly7
Copy link

Velocity Version: 1.1.8
MC Server Version: Yatopia 1.16.5 Build 118
Steps to reproduce:
setup velocity
put tcpsheild jar in plugins

problem: cant connect to server

@Boxiogral
Copy link

Also can't connect, but when i disable only-allow-proxy-connections it works, here's debug info:
imagen

@greysilly7
Copy link
Author

Also can't connect, but when i disable only-allow-proxy-connections it works, here's debug info:
imagen

Can confirm that disabling only-allow-proxy-connections works

@andythetech
Copy link

andythetech commented Jun 12, 2021

I'm having the same problem.

Running Velocity 1.1.8
Purpur (Paper fork) 1.16.5 #1163
TCPShield 2.5

@greysilly7
Copy link
Author

Should also add my backend servers used yatopia 1.16.5 build 118

@AoElite
Copy link

AoElite commented Jun 21, 2021

@greysilly7 @relavis I've made some slight changes on my fork that may fix this issue for you. Try using this build. Also I recommend using Java 16 but as long as you are using at least Java 11 I think it should work. If it doesn't work just tell me what Java version and I'll try to fix it.

@andythetech
Copy link

@greysilly7 @relavis I've made some slight changes on my fork that may fix this issue for you. Try using this build. Also I recommend using Java 16 but as long as you are using at least Java 11 I think it should work. If it doesn't work just tell me what Java version and I'll try to fix it.

Using Java 16 and still experiencing the same errors. Thanks for checking it out though, hopefully a fix can be found.

@emmaboecker
Copy link

@AoElite For me your Fork worked! Thank you!

@trev-sharp
Copy link
Contributor

Anyone experiencing an issue relating to this should update to the latest build. The latest build requires you use at least Java 11 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants