When flitagent.com cannot reach the site, or an app connects but sees no tools from it, open FlitAgent → Settings and click Test connection under Connection. It checks, from the server to itself: HTTPS, permalinks, the endpoint (a JSON answer with a JSON content type, which catches caches, firewalls and HTML error pages) and whether request headers that start with FlitAgent- reach PHP, which flitagent.com’s signed requests need. Each check shows pass, warning, fail or skipped with a one-line fix; nothing is stored and no credentials are sent.
Common results
- HTTPS warning on a local site: flitagent.com cannot reach a local or private site, so it cannot be connected. Use a site with a public HTTPS address.
- Could not check: the site could not reach itself means the server cannot make loopback requests; Tools → Site Health shows why. flitagent.com’s check page still tests the connection from outside.
- FlitAgent headers missing: some hosts, firewalls and security plugins strip request headers they do not know. Ask the host to pass headers that start with
FlitAgent-to PHP.
Still stuck? Write to us with the plugin version, what Test connection reports and what flitagent.com’s check page says.