When something will not connect

When an AI client cannot reach your site, open NibWP → Status before anything else. It is read-only, so it is safe to run and safe to screenshot.

1. Press Re-run diagnostic. Each check comes back Pass, Check, Problem or Info, grouped as Connection, Authentication, WordPress & server, Plugins, themes & firewalls, and Sandbox & extensions.
2. Read the verdict at the top. When something is broken it names one Fix this first. Checks that failed only because of that one are marked as caused by it, so you have a single thing to fix rather than a column of red that clears all at once.
3. The three causes we see most often:
   • Permalinks set to Plain. Go to Settings → Permalinks, choose anything else, then copy the endpoint again from NibWP → Connect, because it will have changed.
   • Application passwords switched off — by a security plugin, by a WP_APPLICATION_PASSWORDS constant in wp-config.php, or because the site is not served over HTTPS.
   • The server stripping the Authorization header before PHP sees it. The credentials are correct, the server discards them, and the request looks exactly like a wrong password. On Apache or LiteSpeed the screen offers a one-click, reversible fix; on nginx it is a fastcgi_param HTTP_AUTHORIZATION line in the PHP location block.
4. Check the Your endpoint card. That address has to be reachable from the machine running the client, not only from the server. Open it in a private window to test: a login prompt or a JSON error means reachable, a firewall page or a timeout does not.
5. Still stuck? Deactivate security and firewall plugins one at a time, re-running after each, then generate a fresh application password. If it still fails, copy the Support report and send it to us — site address and versions only, no passwords or keys.

Full guide: How to: read NIBWP Status