-
Notifications
You must be signed in to change notification settings - Fork 55
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
Exception when loading on Spigot 1.16.3 #20
Comments
Please install ProtocolLib :) |
Yep! Thank you @JosiahWhite That's fixed things, sorry about that, didn't realise that would be needed. Now isn't possible to connect using the direct IP, only works via the TCPshield address - brilliant. Thank you guys for your hard work on this, I can't believe this is a freely available to use system - would have been a nightmare to try and setup a cloud hosted SSLH (I'm guessing that is what this is using in the background?) proxy to do this instead! So thank you guys for your hard work (and very prompt response to this issue!). |
@JosiahWhite An additional question in fact; how can I tell that it's routing requests to your western datacentre rather than to one of the others? Or is that something it just handles automatically based on where the incoming IP is connecting from? Also, I'm guessing it's normal that the latency is a little higher for a home hosted server when connecting via this proxy service. What protection is lost if I disable the |
@Diedinium By default, requests are routed by geography, based on the region the player is closest to. We do offer the ability to change this, but only upon request and in certain situations. If you disable that option, you are disabling very important features TCPShield provides you. Also, please continue this conversation in our support discord. Thank you. |
Short and simple; the plugin throws an exception when attempting to load on a spigot 1.16.3 server:
To replicate just set up a spigot 1.16.3 server, and try to use the plugin - no other special setup should be required.
The text was updated successfully, but these errors were encountered: