If preloading in FlyingPress isn’t starting or gets stuck, it’s usually due to connectivity or server restrictions. Here are the most common causes and how to fix them:
1. Site Is Local or Not Publicly Accessible
FlyingPress performs preloading from our cloud servers, so your site must be accessible from the internet.
Common scenarios:
The site is hosted on localhost or a private/staging server.
The domain is behind a VPN, firewall, or private network.
Solution:
Make sure the site is publicly accessible from the internet.
Preloading will not work in local or restricted environments.
2. Site Blocks Requests from FlyingPress Servers
Our preload servers are located in USA, Germany, and Singapore. If your site blocks traffic from these regions, preloading will fail.
Solution:
Remove any country-based restrictions or firewalls blocking these regions.
Disable CAPTCHA or security plugins that challenge or block automated requests.
3. admin-ajax.php Is Blocked or Rate-Limited
FlyingPress uses WordPress’s admin-ajax.php to trigger and manage preloading.
Solution:
Whitelist your own server’s IP in any firewall or rate-limiting system.
Contact your host if requests to
admin-ajax.phpare blocked or throttled.Check that no security plugin is interfering.
4. Cloudflare “Under Attack Mode” Is Enabled
Cloudflare’s Under Attack Mode presents a JavaScript challenge that blocks our preload bot.
Solution:
Disable Under Attack Mode to allow preloading.
5. HTTP Authentication Is Enabled
If your site requires HTTP Basic Authentication, our servers won’t be able to access it.
Solution:
Disable HTTP authentication.
6. Server Does Not Meet System Requirements
FlyingPress needs a compatible environment to preload properly.
Requirements:
Latest stable versions of WordPress, PHP, and MySQL/MariaDB
Standard file permissions
Standard WordPress folder structure
Solution:
Check that your server meets all FlyingPress system requirements.