Site Unreachable

LATW Cloud reads your content and writes the translations back through the plugin’s REST API, at
/wp-json/latw/v1/cloud/ (with Drupal and PrestaShop, through the module at /latw/v1/cloud/). When it cannot get through, the site shows as Unreachable and its
jobs wait with Waiting: site unreachable. Nothing is lost: LATW Cloud keeps retrying, and the
jobs continue as soon as the site answers.

Test connection — in the site’s Settings tab in the panel, or on the plugin’s settings
screen in WordPress — tells you whether the path is open again.

#The usual causes

A security plugin. Wordfence and similar plugins can block REST API requests from outside.
Allow requests to /wp-json/latw/v1/cloud/. On Drupal and PrestaShop, a security module or
ModSecurity can do the same: allow POST requests to /latw/v1/cloud/.

PrestaShop with Friendly URLs off. The module’s address needs them: turn them on in
Shop Parameters → Traffic & SEO.

Cloudflare or another firewall. A WAF rule or bot protection can stop LATW Cloud before it
reaches WordPress. Add an exception for the same path. LATW Cloud has no fixed IP addresses to
allow instead — but every request on that path is signed with the site’s secret, and the plugin
rejects any that is not.

Password protection. A site behind basic auth, as staging sites often are, cannot be reached.

A local site. localhost or a staging copy on your own computer is not reachable from the
internet and cannot be connected.

A changed address. After moving the site to another domain, adding or removing www, or
switching from http to https, connect it again from the plugin.

The site is down or very slow. LATW Cloud asks for a few items at a time and gives each request
20 seconds. A host that cannot answer that fast shows up as unreachable too.

#Connection lost

If WordPress says Connection lost on the plugin’s LATW Cloud settings, the site’s security keys
in wp-config.php changed and the plugin can no longer read its secret. Press Connect with LATW
to connect again; the site keeps its settings in the panel.

#Webflow

A Webflow site has no plugin and no address of its own to block: LATW Cloud calls the Webflow API
with the site token. It shows as Unreachable when:

• The token was deleted in Webflow, or Webflow deleted it after a year without use.
• The token lacks a scope — it needs read and write access to Pages, CMS and Components, and
  read access to Sites.
• Localization was turned off, or the last extra language was removed.

Generate a new token in Webflow and paste it in Settings → Connection → Replace token; see
Connecting Webflow. Webflow’s limit of API requests a minute usually only slows a job down:
LATW Cloud waits and continues on its own. When the limit stays reached for minutes, the job waits
like for an unreachable site and is retried automatically.

#Update required

Update required is not a network problem: the plugin on the site is too old for LATW Cloud.
Update it in Plugins, and the waiting jobs continue.