This guide is for when setup for TCPShield is failing. This checklist will give you a list of things to double check to ensure everything is configured correctly.
Before running through this checklist, it may be worth using our new Debug Tool! Insert your domains (The one you set your CNAME for is often best) and see what may be going wrong.
Is your domain verified?
Are you confident your backend server is accepting connections? Ensure the correct port that BungeeCord / Spigot is running on is open and property set in the panel.
Are you trying to join the backend IP directly? The TCPShield plugin blocks this intentionally.
Has your DNS propagated? It can take up to 24 hours sometimes for DNS to fully propagate for everyone.
Use https://www.whatsmydns.net/ to ensure this.
Does your backend set have the expected IP addresses in the panel?
Does your firewall accept connections from the TCPShield network? List here.
The TCPShield Discord is available if needed, but this should cover most issues people will encounter when setting up TCPShield.