Skip to main content

Troubleshooting

If you have trouble sending emails, review these common scenarios to debug your Cloudflare integration.

Missing or Invalid API Token

If the plugin cannot authenticate with Cloudflare, you will see a red error badge in your WordPress dashboard.

  • Ensure Token Scope is Correct: Create a new Custom Token with Account > Workers Email Routing > Edit permissions.
  • Check Zone Requirements: Ensure the token gives permissions specifically to the zone (domain) your WordPress site is hosted on.
  • Do not use Global API Keys: WPFlareMail deliberately restricts the use of Global API keys for security reasons. Only use scoped Custom Tokens.

Emails Are Not Sending

If the test email says "Success" but you don't receive it:

  1. Check your Spam Folder: If your SPF, DKIM, or DMARC are incorrect, the email may be silently categorized as spam.
  2. Check Cloudflare Email Routing Dashboard: Check the "Routing Rules" to ensure Cloudflare is successfully processing routes for your domain.
  3. Verify Workers Paid Tier: Using the outbound email API requires the $5/mo Workers Paid plan at Cloudflare. If you are on the free tier, API requests to send outbound mail will fail silently or return a 403.

Plugin Conflict: Another SMTP Plugin is Active

WPFlareMail overrides the wp_mail() function. If you have another SMTP plugin active at the same time, they will conflict.

Fix: Deactivate all other SMTP plugins. Make WPFlareMail the sole email routing handler.

How to view logs

Pro users can use the Email Logs tab to see the exact API response Cloudflare returned (e.g. 200 OK). If a message bounced, Cloudflare's rejection reason is stored there.