001 / DOCS

Troubleshooting Guide

Common issues and solutions for the Ingestics WordPress plugin.

API fetch errors

401 Unauthorized

Your credentials are invalid or the authentication method is wrong.

• Verify your API key, token, or password is correct
• Check that you selected the correct authentication method
• For OAuth2, ensure your client ID and secret are correct
• Check if your token has expired (OAuth2 Authorization Code with refresh)

403 Forbidden

Your API key lacks permissions, or SSRF protection is blocking the URL.

• Check if your API key has the required permissions on the provider’s dashboard
• If fetching from a private/internal API, SSRF protection may be blocking it. Ingestics blocks private IP ranges for security.
• Check if the API requires a specific plan or tier

404 Not Found

The endpoint URL is incorrect.

• Verify the endpoint URL in the provider settings
• Check the API documentation for the correct path
• Some APIs use different base URLs for different regions

429 Too Many Requests

You have exceeded the API’s rate limit.

• Reduce the fetch frequency (e.g., from every 2 hours to every 6 hours)
• Enable exponential backoff retry (Lite+)
• Contact the API provider to increase your rate limit
• On Business edition, use the rate-limit budget queue to manage request frequency

500 Server Error

The API server is experiencing issues.

• Ingestics will automatically retry with exponential backoff (Lite+)
• Check the API provider’s status page
• If the error persists, contact the API provider’s support

Timeout

The API took too long to respond.

• Reduce the number of items per fetch (pagination limit)
• Check if the API is under heavy load
• Increase the PHP timeout in wp-config.php: set_time_limit(300);

RSS feed errors

Feed not found

The feed URL is incorrect or the site does not have an RSS feed.

• Use auto-discovery: enter the website URL instead of the feed URL
• Check if the site has moved or changed its feed structure
• Try common feed paths: /feed/, /rss/, /atom.xml

Feed parse error

The feed format has changed or is malformed.

• Check the diagnostics page for the specific parse error
• Validate the feed at validator.w3.org/feed/
• Contact the site owner if the feed is permanently broken

Full-text extraction not working

Full-text extraction depends on the source site’s HTML structure.

• Some sites block automated fetching (check robots.txt)
• JavaScript-rendered content may not be extractable
• Sites with paywalls will not provide full text
• Try disabling full-text extraction and use the feed summary instead

Scheduling issues

Scheduled fetches not running

WP-Cron is not firing on your site.

• Check if WP-Cron is disabled in wp-config.php
• On low-traffic sites, set up a real cron job (see Scheduling)
• Check for conflicting cron plugins
• Verify the schedule interval is set correctly in the provider settings

Fetches running but no posts created

The fetch is working but no posts are being published.

• Check if the publish mode is set to “Draft” — posts may be created as drafts
• Check the diagnostics page for duplicate detection — all items may already exist
• Verify the field mapping is correct — the title field may be empty
• Check content quality filters — posts may be below the minimum length

Performance issues

Slow fetches

• Reduce the pagination limit (fewer items per fetch)
• Enable unchanged-item skipping (Pro+) to skip items that have not changed
• Use independent API/RSS schedules (Business) to parallelize fetches
• Check if your hosting has sufficient PHP memory and timeout limits

High memory usage

• Reduce the number of items per fetch
• Disable full-text extraction for high-volume feeds
• Increase PHP memory limit: define('WP_MEMORY_LIMIT', '512M');

Getting help

If you cannot resolve an issue with this guide:

• Free edition — Community support via WordPress.org forums
• Lite ($49) — Email support
• Pro ($99) — Priority email support
• Business ($199) — Priority email + phone support

Visit the support page to submit a support request. Include the diagnostic information from Ingestics → Diagnostics for faster resolution.