Open ImPlasmaTbh opened 2 years ago
Are you trying to direct connect to the server with the backend ip? The payload it's receiving is just your servers backend IP address, not the domain or any of the TCPShield signature.
I am joining with "ciphermc.com" which was the IP I set in the domains section whilst configuring the plugin. No DNS records points straight to the backend IP, everything uses the CNAME records.
Also note that using RealIP v2.5.6 on velocity did not work however when I changed to the waterfall, the plugin worked just fine.
Same issue using the plugin with paper
Same issue Velocity - Pterodactyl - Cloudflare
I think TCPShield has mostly been abandoned unless you're a paying customer :( I stopped using it.
I just setup TCP Shield on my bungeecord network using the latest version of the plugin which did not work. I would get an error when trying to connect however everything was configured correctly. This was using the plugin version v2.5.5![image](https://user-images.githubusercontent.com/46997381/163673335-ff15defe-c9c6-48d5-87b6-b256b477e229.png)
After going through a couple of other github issues of people experiencing the same error, I found a solution where going down a version fixed it (In my case, v2.5.6 to v2.5.5), which was it and now TCP Shield works fine.
Velocity information:![image](https://user-images.githubusercontent.com/46997381/163673393-140ac4c6-cdcd-42f1-aab3-0d317025a4a3.png)