Troubleshoot WordPress backup status that will not load

Separate a failed WordPress site-list request from one site’s backup-list failure, preserve evidence, and retry without disconnecting healthy sites.

Last reviewed

The WordPress integration page makes one request for sites and then one backup-list request per displayed site. A top-level failure and a row with unknown backup details therefore have different causes and should not trigger the same recovery.

Four panels show capturing the account-wide alert, isolating one Unknown backup row, comparing wp-admin evidence, and preserving a redacted failing response.
Four panels show capturing the account-wide alert, isolating one Unknown backup row, comparing wp-admin evidence, and preserving a redacted failing response. Open full-size screenshot.

Steps

  1. Open Integrations → WordPress while signed in and copy the exact alert. Could not load your WordPress sites. Please try again. means the site-list request itself failed.
  2. If the table loads but one row shows Unknown or blank stored details, record that site ID and URL. The page converts a failure of that site’s backup request to an unknown row while leaving other sites visible.
  3. Reload once after confirming the browser is online. Do not disconnect a site merely to refresh status; disconnect revokes its credential and is not a status reload.
  4. Check whether the account session expired. The sites route returns Sign in required for an unsigned session, Site not found for a missing record, and You can only view your own sites for another owner.
  5. Compare the same site in wp-admin. Its dosya tab shows whether the local key is connected, unreadable, or revoked; the Backups list remains the source for the local archive.
  6. If only one row still fails, preserve the request status and response body for support. If every row fails, preserve the top-level alert, account, time, and browser before signing in again.

The page fetches backup details for only the first 20 displayed sites. A Showing 20 of N sites notice means additional active sites exist even though their backup rows were not requested on that view.

Reference for “Troubleshoot WordPress backup status that will not load”: Dosya WordPress plug-in overview page.
Reference for “Troubleshoot WordPress backup status that will not load”: Dosya WordPress plug-in overview page. Open full-size screenshot.

Expected result

The page either repopulates the account’s active site rows and their newest backup states, or the evidence identifies whether the account-wide sites request or one site-specific backups request failed. No healthy connection is revoked as a refresh tactic.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.