Hey @splaquet,
Please have the AWS engineer check the following:
1. Ports & Protocols
SiteDrive communicates exclusively over HTTPS (Port 443) using the standard WordPress REST API.
-
Inbound (Remote Site): Must allow traffic on Port 443 from the IP address of your local/connecting site.
-
Outbound (Remote Site): Must allow traffic on Port 443 to
sitedrive.co (for license validation) and back to your local site URL.
2. REST API Whitelisting (Cloudflare / CloudFront / AWS WAF)
The most common cause of this error in an AWS setup is a Web Application Firewall (WAF) blocking the SiteDrive namespace. The AWS engineer should ensure the following URI pattern is not challenged (CAPTCHA) or blocked:
-
API Path:
/wp-json/sitedrive/v1/*
-
Methods:
POST , GET , DELETE
-
Content-Type:
application/json
IMPORTANT
Cloudflare “Bot Fight Mode” or AWS WAF “Core Rule Set” often flags server-to-server requests as suspicious because they don’t have a standard browser User-Agent. SiteDrive identifying as WordPress/VERSION; SITE_URL may need to be explicitly allowed.
3. Server-Level Configuration (EC2/Nginx/Apache)
If the request is reaching the EC2 instance but still failing, check these:
-
Authorization Headers: Ensure that custom headers (specifically
X-WP-Nonce ) are not being stripped by your load balancer or Nginx config.
-
Security Plugins: If the remote site runs Wordfence, Sucuri, or similar, ensure they aren’t blocking “Aggressive” REST API usage.
-
S3 Media Access: If you are using S3 for media storage, ensure the remote WordPress site can still serve those files via
wp_get_attachment_url() —SiteDrive relies on WordPress’s native methods to locate and “package” files for the remote drive.
Other Recommended “Fix” for AWS Engineer:
Create a WAF bypass rule or a Cloudflare Page Rule that disables security checks/challenges for: *example.com/wp-json/sitedrive/v1/*