Troubleshooting
Solutions to the most common issues — queue stalls, OpenAI errors, image failures, license problems.
First step: check the Logs tab
Every issue starts here. Open AI AutoBlogger → Logs. Filter by level: Error first, then Warning. Most fixes become obvious from a clear error message.
Queue isn’t moving
Symptoms: Articles stuck in queued for >15 minutes.
Diagnosis:
- WP-Cron may be disabled. Test by visiting
https://yoursite.com/wp-cron.php— if it 200s, cron is reachable. If your host disables it (WP Engine, some VPS), set up a real system cron:*/2 * * * * curl https://yoursite.com/wp-cron.php?doing_wp_cron - Check Logs for Error: OpenAI API timeout — usually means the model is overloaded. AutoBlogger retries 3× then marks the job failed.
- License could have lapsed past the 7-day grace period. Re-verify in License tab.
“OpenAI API error 429 — rate limit”
You’re sending too many requests too fast. Common on free-tier OpenAI accounts and with very high AutoPilot cadence (10+ per day).
Fix: reduce AutoPilot cadence, or upgrade your OpenAI usage tier (Settings → Limits → Increase). Tier upgrades are automatic once you’ve spent $5/$50/$100 cumulatively.
“OpenAI API error 401 — invalid key”
Either the key is mistyped, was rotated, or your billing balance hit zero.
Fix: regenerate the key at platform.openai.com/api-keys, paste it back into API Settings, save. Check Billing shows a positive balance.
Image generation fails
- DALL·E 3 rejected the prompt — usually a content-policy match. Edit the article title to remove the trigger word.
- Unsplash rate limit — free tier is 50 requests/hour. Upgrade or switch provider.
- MonsterAPI / Imagine.art timeout — these can take 15+ seconds. AutoBlogger waits up to 30 seconds, then falls back to no image. Re-run with the article title from Manual Generation.
License activation fails
Look at the error message — recent versions of AutoBlogger surface the actual server error (not a generic “activation failed”).
- “Slots full” — see License management for moving slots between domains.
- “Invalid key format” — re-copy the key, watch for
I/l/1/O/0confusion. - “License server unreachable” — your firewall or host is blocking outbound HTTPS to openaiautoblogger.com. Whitelist the domain.
Generated articles missing schema
If Google’s Rich Results Test finds no schema, check that SEO Settings → JSON-LD schema is enabled. Schema is emitted via wp_head on singular pages — view-source on a generated post and search for "@type":"Article". If absent, your theme may be stripping wp_head output (rare but possible with heavy custom themes).
Webhook not firing
- Hit Send test payload in SEO Settings — confirms AutoBlogger can reach your endpoint at all.
- Check Logs — failed webhooks log the response status + body.
- Endpoints must respond within 10 seconds and return 2xx, or AutoBlogger schedules a retry (1 / 5 / 30 / 120 min).
Articles publishing as drafts
Check AutoPilot → Publishing → Mode. If “Save as draft” is selected, that’s by design. Switch to “Publish immediately” to go live automatically.
Still stuck?
Send us your Logs tab export + which step you’re stuck on. Most issues we resolve same day.
Issue not listed?
Send us a ticket with your Logs export and we’ll diagnose it within 24 hours.