## **Overview**

When Content Assistant displays a **vault not connected** error during content generation or publishing, the most common cause is *not* a WordPress configuration issue — it is a firewall or Web Application Firewall (WAF) rule set by your hosting provider that blocks requests to the **/wp-json/** REST API endpoint before they ever reach WordPress.

This article explains why this happens and walks you through general steps to resolve it.

## **Why This Happens**

Search Atlas Content Assistant communicates with your WordPress site through the WordPress REST API. All requests are sent to a URL that ends in **/wp-json/**. Many hosting providers run server-level firewalls or WAF rules that inspect incoming traffic and can block these requests automatically — even when your WordPress REST API settings appear correct inside WordPress itself.

Common reasons a hosting firewall blocks REST API requests include:

- The firewall treats automated API calls as suspicious bot traffic.
- A security rule flags requests that do not originate from a browser.
- WAF rulesets block access to **/wp-json/** as a hardened security measure.
- The hosting control panel has a security setting enabled that restricts REST API access.

Because the block happens at the server level, disabling or re-enabling the REST API inside WordPress will not fix the problem.

## **How to Confirm This Is the Cause**

Before changing any settings, confirm that the REST API endpoint is being blocked at the hosting level:

1. Open a new browser tab and go to **https://yourdomain.com/wp-json/** (replace with your actual domain).
2. If you see a JSON response listing WordPress routes, the REST API is reachable and the issue is elsewhere.
3. If you see an error response or a generic hosting error page, your hosting provider firewall may be blocking the endpoint.
4. You can also use your browser's developer tools (Network tab) to check the HTTP response code returned for the **/wp-json/** URL.

## **General Fix: Whitelist the REST API in Your Hosting Firewall**

The steps below apply to most hosting providers. Log in to your hosting control panel and look for a section related to **Security**, **Firewall**, or **WAF**.

1. Locate the firewall or WAF settings for your domain.
2. Find any rule that blocks or restricts access to **/wp-json/** or REST API requests.
3. Add a whitelist or allow rule for the path **/wp-json/\*** so all REST API sub-routes are permitted.
4. Save your changes and wait a few minutes for the settings to take effect.
5. Return to Content Assistant and attempt to reconnect your vault or retry publishing.

## **If the Issue Persists**

If you have reviewed your hosting firewall settings and the vault connection error continues, please have your domain name, hosting provider name, and any error messages ready when you reach out. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.