When a connection does not work

The symptoms people meet when connecting a WordPress site, why each happens and the one change that fixes it.

These are the problems that stop a WordPress site connecting, with the fix for each. After a fix, press Connect again with the same code.

There is no Settings, PageSoar in WordPress

Why: The plugin was uploaded but not activated.

Fix: In WordPress, open Plugins, find PageSoar Connector and press Activate.

PageSoar says it could not reach the site, or the site stays on waiting

Why: A security plugin or firewall is turning PageSoar away. Wordfence, Solid Security, Cloudflare WAF and Sucuri can all do this.

Fix: In that tool, allow requests to /wp-json/pagesoar/v1/, then press Connect in WordPress again with the same code.

The test site asks for a password before WordPress opens

Why: Password protection from the host or a plugin also stops PageSoar's check.

Fix: Leave /wp-json/pagesoar/v1/ out of the password protection, or switch it off while you connect.

WordPress says the site could not reach PageSoar

Why: The host blocks outgoing calls from the web server.

Fix: Send your host or IT team the lines below, then press Connect again with the same code.

Please allow outgoing HTTPS from our WordPress server to PageSoar:
Host: pagesoar.com
Port: 443
Path: /connector/

Opening your site's /wp-json/ address shows a page not found

Why: Permalinks are set to Plain, which hides the address PageSoar uses.

Fix: In WordPress, open Settings, Permalinks, choose any option except Plain (Post name is the usual one) and save.

PageSoar says the site did not answer

Why: The site was down or slow, or the address in PageSoar is not the site's.

Fix: Open the site in a browser to check it loads, check its address in Workspace settings, then press Check again.