WordPress sends a request to wp-cron.php to get this loopback info. However, as a security precaution, we are blocking access to wp-cron.php. So nginx returns a 403 response when WordPress sends that request. That’s why you’re seeing this loopback issue along with the page cache header. You can ignore this error, nothing to worry about. We trigger cron every 10 minutes via wp-cli, so your cron is executing perfectly, no issues there.
Docs
- Getting Started
- Account
- Server
- Site
- FAQs
- Frequently Asked Questions
- Should I use the X caching plugin on FlyWP?
- Which file/path should be edited to add the configuration To add a custom NGINX config to a single website
- Getting “Your site could not complete a loopback request” on WordPress site health. Is this an issue?
- How to upload Unfiltered fonts/unsupported files on WordPress using FlyWP?
- How to manage emails on FlyWP
- Let’s encrypt SSL is not activating on my domain on FlyWP
- How can I execute a custom PHP file via Cron on a server with multiple subdomains?
- How to access your FlyWP server via FileZilla Using SSH Keys
- Setting Up Wildcard SSL with Cloudflare on FlyWP
- Frequently Asked Questions
- Affiliate Program
- Home
- Docs
- FAQs
- Frequently Asked Question...
- Getting “Your site could not complete a loopback request” on WordPress site health. Is this an issue?