- Plesk for Linux
- Plesk for Windows
How to enable loopback connections for WordPress cron?
Some WordPress plugins use background processes.
WordPress simulates cron works by having the site connect back to itself via curl (or other available fallback connection methods if curl is unavailable) to trigger actions to take place behind the scene.
Connect to the server via SSH for Linux or RDP for Windows and enable loopback by adding the domain to the "hosts" file (
/etc/hosts - for Linux,
%SystemRoot%\System32\drivers\etc\hosts - for Windows):
CONFIG_TEXT: 127.0.0.1 www.example.com example.com localhost localhost.localdomain
If the first solution does not work, add the code below to
Go to Domains > example.com > File Manager > httpdocs and click on
wp-config.phpfile to edit and add the below string:
CONFIG_TEXT: define ('ALTERNATE_WP_CRON', true);
I'm using Plesk Obsidian / Ubuntu 18.04 on Amazon Lightsail. I was getting Loopback and Rest API warning message in WP's Site Health status. Adding the domains to the local host 127.0.0.1 in Option 1 here did not fix the two warning messages in my situation. The only way I was able to resolve it via hosts file was to add my Lightsail VPS's static external ip address to the list.
sudo nano /etc/hosts
the_external_static_ip_of_the_VPS www.yourdomain.com yourdomain.com
Please sign in to leave a comment.