Docs

Connection test failing

7 min readUpdated November 9, 2026

Use this page when WP Media Cloud cannot talk to your storage. It explains which connection checks exist for each provider, what their messages mean, and how to read the error codes providers send back.

Which checks exist#

Every provider can be tested on the Health page. Go to Media Cloud > Health and click Run All Checks. The Upload Test row uploads a small test file to your storage and deletes it again.

ProviderHow to test the connection
All providersRun All Checks on the Health page. The Upload Test row uploads and deletes a small test file. For providers other than Bunny.net, this needs WP Media Cloud 1.1.9 or newer.
Cloudflare R2Also Test connection in the setup wizard. It uploads and deletes a small test file before you save.

To open the setup wizard again, go to Settings and click run the setup wizard. It opens with your current values, and saved keys show as Saved.

Cloudflare R2: Test connection messages#

Cloudflare R2 Test connection in the setup wizard
What you seeWhat it meansHow to fix it
“Connected. Uploading and deleting in “my-bucket” both work.”The keys and bucket are correct.Save the wizard.
“Enter the Account ID, bucket name, Access Key ID and Secret Key first.”A field is empty.Fill in all four fields.
“The Account ID should be 32 letters and numbers. Copy it from the Cloudflare dashboard.”The Account ID is not in the expected format.Copy it again from your Cloudflare dashboard.
“Bucket names use 3 to 63 lowercase letters, numbers and hyphens.”The bucket name is not valid.Type the bucket name exactly as it appears in R2.
“Upload failed: … Check that the token has Object Read & Write on this bucket and that the keys were copied in full.”R2 refused the upload. The provider’s error is in the middle.Check the token permissions and paste both keys again. Use the table of error codes below.
“Uploading works, but deleting the test file failed: …”The token can write but not delete.Give the token Object Read & Write, then delete the named test file from the bucket.
“Could not create a temporary file on this server.”PHP cannot write to its temp folder.Ask your host to fix the PHP temp folder permissions.

See Cloudflare R2 for token setup.

Bunny.net: Health page checks#

Go to Media Cloud > Health and click Run All Checks.

RowWhat you seeWhat it meansHow to fix it
Account API Key“No API key configured.”The Bunny API key is empty.Run the setup wizard and paste your account API key.
Account API Key“Could not reach api.bunny.net: …”The key is wrong, or the server cannot reach Bunny.Paste the key again. If it still fails, ask your host about outbound HTTPS.
Storage Zone“Zone or password not configured.”The storage zone or its password is missing.Run the setup wizard and select the zone. Paste its Zone Password.
Upload Test“Upload failed: Bunny Storage HTTP 401: …”The storage zone password is wrong.Copy the password from the zone’s FTP & API Access page. It is not the account API key.
Upload Test“Upload failed: cURL error …”The server could not reach Bunny Storage.Check the storage region and ask your host about outbound HTTPS.
Pull Zone / CDN“No pull zone configured.” or “Cannot reach …”The CDN hostname is missing or not responding.Select the pull zone in the setup wizard or in the Bunny.net CDN card in Settings.

See Bunny Edge Storage.

Other providers: Health page checks#

Amazon S3, Google Cloud Storage, DigitalOcean Spaces, Wasabi, Hetzner, Backblaze B2 and custom S3 endpoints have no Test connection button in the wizard. Use the Health page instead.

  1. Go to Media Cloud > Health and click Run All Checks.
  2. The Bucket row should say “… credentials saved. Bucket: your-bucket”.
  3. The Upload Test row should say “Test file uploaded and deleted successfully.”
  4. If it says “Test upload failed: …”, the rest of the message is the provider’s error. Look it up in the error code table on this page.

To also check a real image:

  1. Make sure Offload on upload is on in Settings under Offload Behaviour.
  2. Go to Media > Add New and upload a small image.
  3. Go to Media > Library in list view. The row under the image shows In cloud when the upload worked.
  4. If it shows Offload failed. Retry, hover over it to read the error. The same error is listed on the Dashboard under Bulk Offload.

In the setup wizard, Load lists your buckets when your keys are allowed to list them. If it shows an error, read it with the table below. A refused list does not always mean uploads will fail, because some keys can write to one bucket but cannot list buckets.

Health page messages for all providers#

Health tab with a failed provider check
RowWhat you seeWhat it meansHow to fix it
Bucket“Amazon S3 is missing: secret key, bucket. Run Setup Wizard.”The named fields are empty.Run the setup wizard and fill them in.
Upload Test“Test file uploaded and deleted successfully.”WP Media Cloud can write to and delete from your storage.Nothing to do.
Upload Test“Test upload failed: …”The provider refused the upload. Its error follows the colon.Look up the error in the error code table on this page.
Upload Test“Test file uploaded, but deleting it failed: …”The keys can write but not delete.Give the keys delete permission, then remove the named test file from the bucket.
Upload Test“Plugin not ready: storage credentials are incomplete. Check Settings or run the Setup Wizard.”A required field is empty, so nothing offloads.See New uploads not being offloaded.
Upload Test“Could not create a temporary file on this server, so the upload test was skipped.”PHP cannot write to its temp folder.Ask your host to fix the PHP temp folder permissions.
CDN URL“No CDN URL configured. Media will be served from the bucket directly.”No CDN is set, so the bucket address is used.Set a CDN in Settings, or make sure the bucket allows public reads.
CDN URL“CDN URL set (…) but unreachable: …”The server could not reach the CDN address.Check the address and its DNS.
Every row“Check failed: …”The Health request itself failed.Reload the page and run the checks again.

The Health page reads WPMC_* constants from wp-config.php as well as saved settings.

Error code table#

For S3-type providers, WP Media Cloud shows the HTTP status, the provider’s error code and its message. For example: “HTTP 403 SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided.”

Error codeWhat it meansHow to fix it
HTTP 403 InvalidAccessKeyIdThe access key does not exist.Copy the access key again. Check it belongs to this provider and account.
HTTP 403 SignatureDoesNotMatchThe secret key does not match the access key.Paste the secret again, with no spaces at either end.
HTTP 403 AccessDeniedThe key works but has no permission for this action or bucket.Give the key read, write and delete access to the bucket.
HTTP 403 RequestTimeTooSkewedThe server clock is too far off.Ask your host to sync the server clock.
HTTP 404 NoSuchBucketThe bucket name is wrong, or it is in another region or account.Check the Bucket name and region in the setup wizard.
HTTP 301 PermanentRedirectThe bucket must be reached through a different endpoint.Choose the region the bucket was created in.
HTTP 400 InvalidBucketNameThe bucket name is not valid.Type the name exactly as shown in the provider’s console.
“No response from storage provider”The request got no HTTP response.Check the endpoint or region, then ask your host about outbound HTTPS.
“cURL error 6: …”The server could not resolve the endpoint’s host name.Check the endpoint URL or region for typos.
“cURL error 28: …”The connection timed out.Ask your host to allow outbound HTTPS on port 443 to the provider.
“cURL error 60: …”The SSL certificate could not be verified.Ask your host to update the server’s CA certificates.

Provider tips#

  • Copy keys, do not type them. Most failures are a missing character or a trailing space.
  • Backblaze B2: use an application key, not the master key. Key ID takes the keyID and Application Key takes the applicationKey.
  • Google Cloud Storage: use an HMAC key from the Interoperability settings, not a JSON key file.
  • Custom S3: the Endpoint URL needs https://. If requests fail, try the other URL Style option.

Each provider guide has full setup steps: Amazon S3, S3-compatible endpoint, DigitalOcean Spaces, Wasabi, Hetzner Object Storage, Backblaze B2, Google Cloud Storage.

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only