Activating Linkilo with Cloudflare, WAFs, and Security Plugins

Older Linkilo versions could fail to activate on sites behind Cloudflare or strict security setups — the dreaded timeout or error page mid-activation. Linkilo 2.9 redesigned activation specifically to fix this. Here's what changed and what to expect.

Why activation used to fail

Activating a big plugin means creating database tables and running migrations. Older versions did all of it inside the single "Activate" click. Cloudflare cuts off any request that takes longer than about 100 seconds (error 524), and some WAFs kill long admin requests even sooner — so on large sites the activation request died before it finished, and WordPress never recorded the plugin as active.

How 2.9 activates instead

• Clicking Activate now returns in a few seconds, always.
• The heavy setup runs in the background in small, resumable steps as you use wp-admin.
• While it finishes you may briefly see a blue notice: "Linkilo is finishing its setup in the background (N of 6 steps done)." It disappears on its own — usually within one or two page loads.
• If a proxy or firewall kills a request mid-setup, nothing is lost: the next wp-admin page load resumes exactly where it stopped. No step ever runs twice.

There is nothing to configure — this is automatic.

If you still have trouble activating

1. "Plugin could not be activated because it triggered a fatal error" — usually an incomplete upload. Delete the plugin folder and re-upload the zip (see our separate article on this error).
2. Upload itself fails ("the link you followed has expired") — a server upload-size limit, not Cloudflare. See the fix article for that error.
3. The setup notice never clears — visit any two or three wp-admin pages (each visit advances setup). If it persists, contact support with a support export.

Security plugins

Wordfence, Kadence security features, and similar plugins don't interfere with 2.9 activation — the background steps are ordinary short admin requests, indistinguishable from normal wp-admin activity.