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, sends will fail and the rejection reason will appear in your Email Logs.

  • Ensure Token Scope is Correct: Create a new Custom Token with the Account > Email Sending > Edit permission.
  • Check Account Resources: Ensure the token includes the Cloudflare account that owns the domain your WordPress site sends from.
  • Do not use Global API Keys: Flarepipe authenticates with Bearer tokens only, so Global API Keys will not work. Use a scoped Custom Token.

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

Flarepipe 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 Flarepipe 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.