WPVibe is an AI integration tool for WordPress which can sometimes be blocked by the website firewall. This article explains a simple workaround that helps WPVibe connect successfully.

Problem

WPVibe uses HTTPS requests to WordPress core and plugin REST routes, including /wp-json/wp/v2/, /wp-json/wpvibe/v1/ and their ?rest_route= equivalents. Requests arrive from Cloudflare’s network or from one of WPVibe’s static relay IP addresses. If connecting through the Cloudflare network, actions from WPVibe can fail or appear blocked.

Solution

If WPVibe is being blocked, the goal is to temporarily trigger its fallback connection method and then allow its static relay IP addresses.

1. Allow these WPVibe static relay IP addresses in your firewall:
   – 192.241.129.49
   – 146.190.2.65
   – 152.42.154.10
   
   To verify the current list, review https://wpvibe.ai/relay-ips.txt.
   You can find instructions on how to allow an IP address in the firewall settings here.
2. Add a block rule for this exact URL path using a matches rule: /wpvibe/v1/ping
   The temporary block on /wpvibe/v1/ping helps trigger WPVibe’s automatic 24-hour fallback to static IP addresses.
3. Ask the AI to continue working through WPVibe on the site. If the first action fails after these changes, retry it once. If needed, repeat this process occasionally until the next step is completed. Failed requests should succeed when retried.
4. Contact WPVibe support and ask them to route your site through the static IPs only: support@wpvibe.ai. Until then, WPVibe may occasionally send requests from Cloudflare’s network, which the IP allowlist entry does not cover.

Once WPVibe support confirms your site is routed through the static IPs, you can remove the block rule for /wpvibe/v1/ping.

You can find instructions from WPVibe here.