Commonly asked questions
Disconnected on Login
High Latency and General Lag
How to Read a Traceroute
Connection Complaint Policy
Protect a website
Protect a home hosted server
This guide is for when the setup for TCPShield is failing. This checklist will give you a list of things to double-check to ensure everything is configured correctly.
Is your domain verified? Is your domain pointing to the correct backend set?
Are you confident your backend server is accepting connections? Ensure the correct port that BungeeCord / Spigot is running on is open and matches what you have in the backend set on our panel.
Are you trying to join the backend IP directly? The TCPShield plugin (and proxy protocol) blocks this intentionally.
Have you configured the proxy protocol correctly? The TCPShield plugin and proxy protocol setting can't coexist. More information can be found
Make sure you
install the TCPShield plugin in both your proxy server and your game mode server.
If you are using TCPShield plugin, keep in mind that it might not be compatible with your existing plugins (antiBot and antiVPN specifically). Try disabling them or switch to
Has your DNS
? It can take up to 24 hours sometimes for DNS to fully propagate for everyone.
to ensure this.
For more information on how DNS propagation works, please refer to
Have you tried using your subdomain instead of your SRV record? Some clients can have issues resolving your SRV record.
Does your backend set have the expected IP addresses in the panel?
Does your firewall accept connections from the TCPShield network? List
TCPShield Discord is available
if needed, but this should cover most issues people will encounter when setting up TCPShield.
Panel - Previous
Next - Troubleshooting