“Background updates are not working as expected”
This WordPress Site Health warning means one or more automatic-update checks failed. It does not prove your website is down, compromised or missing a particular patch. Expand the result in Tools → Site Health and record the individual failed check. You may instead see “Background updates may not be working properly”; investigate its details in the same way.
For a business website, first establish who owns updates: you, your host or a deployment provider. A host-managed or version-controlled site can intentionally prevent WordPress from changing files. Confirm how security updates are delivered before changing that policy.
Record the failed check before changing settings
- Save the exact expanded Site Health message, affected site, time and WordPress/PHP versions. Do not share credentials or recovery links.
- Check Dashboard → Updates and your host's maintenance records. Establish whether an update is available, intentionally deferred, failed, or already installed by the host.
- Confirm a usable backup and staging environment. On a shop, separate file recovery from database recovery so new orders are not overwritten.
- Ask the host whether an updater or deployment is running. Do not start overlapping updates or delete update locks while work is active.
Match the evidence to the next check
| Evidence | What to check | Avoid |
|---|---|---|
| File changes or automatic updates explicitly disabled | Ask who set DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED and how the site is maintained. | Removing intentional deployment controls without a replacement. |
| Files cannot be written or FTP credentials requested | Ask the host to verify ownership, effective write access, storage quota and its supported update method. | Recursive chmod 777 or forcing FS_METHOD to bypass diagnosis. |
| Scheduled events are late | Check the configured WP-Cron or host scheduler and whether the specific update task completed. | Disabling WP-Cron before confirming a working replacement. |
| Downloads fail or time out | Use the timestamp and destination in hosting logs to check DNS, outbound HTTPS, timeouts and resource limits. | Assuming every timeout is a plugin conflict. |
| A host intentionally manages updates | Request the update policy, last successful run and confirmation that required patches are covered. | Dismissing the warning solely because the hosting brand is familiar. |
“Your site could not complete a loopback request”
This is a separate Site Health result that can accompany scheduling problems. It describes a request from WordPress back to its own site. A failed loopback and a failed download from WordPress.org are different requests; use the reported URL and timestamp to distinguish them.
If the details mention cURL error 7, investigate connection failure; error 28 indicates a timeout; error 60 concerns certificate verification. Have the host inspect the full error, DNS, certificate chain and relevant access logs. Do not disable TLS verification or broadly switch off the firewall to make a warning disappear. Apply a narrowly scoped correction only after the blocked request is identified.
Verify the updater, not just the warning
Repeat Site Health after the specific cause is corrected. Check the installed component version and update logs. A successful manual update does not prove automatic scheduling works; confirm the next relevant scheduled task or host-managed update result. Test login, contact forms and checkout in a controlled environment when changed components affect them.
If the site is stuck on “Briefly unavailable for scheduled maintenance. Check back in a minute.”, use the stale maintenance flag checks. If a fatal error followed the update, follow the critical-error guide. For delayed scheduled tasks, see WP-Cron diagnosis.
When to request a repair review
Stop if there is no usable backup, update ownership is unclear, or the next step would alter live order data, file ownership or security controls. Request a free human review with the redacted Site Health result, recent changes and affected business function. We confirm availability and any paid scope before work. For recurring update management, review WordPress support for small businesses.
Sources and scope
Warning text checked against WordPress Site Health source. See the official WordPress updating guide and WP-Cron handbook. These checks narrow the cause; they do not establish a diagnosis for an unseen website.