If you're getting a timeout error while installing the Search Atlas WordPress plugin behind AWS CloudFront, this guide walks you through the working fix.
🚨 The Problem
🚨 The Problem
A user attempting to install the Search Atlas plugin experienced a timeout error, even though:
The server was behind AWS CloudFront
External calls were allowed
No IP restrictions were configured
All other WordPress plugins were disabled
Cache had been cleared
Despite standard troubleshooting, the timeout persisted.
🧠 Why This Happens
🧠 Why This Happens
When your WordPress server is behind CloudFront (or other CDN/security layers), automated API calls during plugin setup may fail due to:
Execution time limits
CDN-layer request handling
Server-level configuration conflicts
Initial handshake sync issues
Even if there are no explicit IP restrictions, the automated setup can still fail silently.
✅ The Working Solution: Manual Plugin Connection
✅ The Working Solution: Manual Plugin Connection
Instead of relying on automatic setup, manually connect the plugin using your API credentials.
🔧 Step 1 — Open the Search Atlas Plugin in WordPress
In your WordPress dashboard:
WordPress Admin → Search Atlas Plugin → Settings
🔑 Step 2 — Paste Your API Key
In the API Key field:
Paste your assigned API key
Save
🆔 Step 3 — Add the OTTO Pixel UUID
Below the API Key field, you’ll see:
OTTO Pixel UUID
Paste the provided UUID into this field
Save
🧹 Step 4 — Purge All Caches
This is critical.
Clear:
WordPress cache
Server cache
CloudFront cache
Any object caching layers
Wait 30–60 seconds.
🔄 Step 5 — Click “Sync”
After clearing cache:
Click Sync Plugin
If successful, the plugin will connect and your dashboard will load normally.
🔑 Where to Find Your UUID and API Key in Search Atlas
🔑 Where to Find Your UUID and API Key in Search Atlas
🆔 Where to Find Your UUID (OTTO Pixel UUID)
Your UUID is embedded inside your OTTO Pixel script.
📍 Exact Navigation Path (Inside the Dashboard):
Left Sidebar → AI SEO → Installation Guide → Custom Installation
What You’ll See:
A section titled: Step 1: Copy Your Pixel Script
A script block with your OTTO pixel
Inside the script tag, look for something like:
data-uuid="87a7de3c-6f0e-4269-8518-df74976bb97c"
That value is your UUID.
It is:
Unique per project
Used to identify your OTTO installation
Automatically generated
🔐 Where to Find Your API Key
Your API Key is located in account-level settings.
📍 Exact Navigation Path (Inside the Dashboard):
Top Right → Click your Profile Name → Settings → API Keys
What You’ll See:
A section titled: Search Atlas API Key
A long alphanumeric key like:
9581270b5f64faea242925febbdd817c
That is your API Key.
It is:
Account-level (not project-specific)
Used for integrations and external connections
Sensitive (do not share publicly)
⚠️ Important Difference
UUID | API Key |
Found in OTTO Installation Guide | Found in Account Settings |
Project-specific | Account-level |
Used for Pixel installation | Used for API integrations |
Inside | Listed under API Keys panel |
🎉 Expected Result
🎉 Expected Result
You should now:
See your Search Atlas dashboard
Confirm the plugin shows as connected
No longer receive timeout errors
🛠 If It Still Doesn’t Work
🛠 If It Still Doesn’t Work
Check:
PHP memory limits
max_execution_time
Firewall or WAF rules
CDN request timeout settings
If needed, escalate to support with:
A short Loom video
Server environment details
Hosting provider information
If you're running WordPress behind CloudFront or another CDN and seeing timeouts, manual setup is the fastest resolution path.