Skip to content
Docs menuTroubleshooting › Site not reachable

Site not reachable

What the check page and the Sites list mean when flitagent.com cannot reach a site, and what to do.

TroubleshootingLast updated
On this page1 section

flitagent.com checks a site right after you connect it, on every request and whenever you open Check your site: click Check next to the site under Sites in your account, or Check the connection on flitagent.com in FlitAgent → Connect, shown until flitagent.com first reaches the site. Sites shows each site’s status with the last error.

  • Not reachable: flitagent.com got no usable answer, for example the site is down, the request timed out, a firewall blocked it or the answer was not JSON. Check that the site loads over HTTPS from outside your network, then click Check again on Check your site.
  • Local and private sites: flitagent.com must reach this site over the internet, so local and private sites cannot be connected.
  • Not accepting requests from flitagent.com: the site refused flitagent.com’s signed requests, usually because it was disconnected in FlitAgent → Connect. Connect it again there.
  • The administrator who connected the site can no longer use FlitAgent: that user was deleted or is no longer an administrator. Connect the site again as another administrator.

In your AI app

A tool call that cannot reach a site returns an error naming the site and the reason. “flitagent.com is busy, try again in a moment” means many calls were in progress; try again. A call over your account’s limit says which limit and when it resets.

Last updated

Something wrong or missing on this page? Email hello@flitagent.com.