CDN credentials and test connection
Save encrypted keys; Test connection runs HeadBucket and may flag CORS for Performance mode.
CDN credentials and test connection
Prove the master can reach the bucket before enabling uploads.
Where to find it
Admin → Servers → add/edit CDN → credential fields + Test connection
How it works
On create, access key, secret, and bucket (plus region / endpoint / account as required) are required. On edit, leave secret blank to keep the saved encrypted value.
Test connection runs S3 HeadBucket (and may try CORS). Need access key, secret, and bucket or you get: Fill S3 access key, secret key, and bucket name to test this CDN.
| Probe detail | Meaning |
|---|---|
s3_head_bucket_ok |
Reachable |
s3_head_bucket_ok_cors_required |
Reachable; CORS needed for direct browser upload |
bad_credentials / access_denied / bucket_not_found |
Fix keys or bucket |
wrong_endpoint / ssl_error / timeout |
Fix endpoint / TLS / network |
Performance mode on CDN rows (performanceMode, default on when unset) is separate from remote-node Performance mode. Allow save if connection test fails can leave a broken CDN enabled - fix credentials before putting weight/On traffic on it.
Common problems
Saved with a failing test
Turn Status Off or fix keys before uploads try that server.