How to Configure Wasabi CDN
This guide follows Wasabi’s official Management Console steps to create a bucket and access keys, then paste them into XFile Ultra.
Sources: Working with buckets and objects · Creating a new access key · Service URLs by region · Console: https://console.wasabisys.com/
---
Where this goes in XFile Ultra
Admin → Servers → Servers management → Add new CDN (or edit an existing CDN)
Provider: Wasabi
---
What to paste into XFile Ultra
| XFile Ultra field | Copy from Wasabi |
|---|---|
| Access key ID | Access Key (Access Key ID) |
| Secret access key | Secret Key (shown once — click Show) |
| Bucket name | Exact bucket name |
| Region | Region code for that bucket (e.g. us-east-1, eu-central-1) |
| Public / custom domain URL | Optional |
You do not paste a separate endpoint. XFile Ultra uses https://s3.<region>.wasabisys.com.
---
Step 1 — Create the Wasabi bucket
Per Wasabi: Creating a Bucket:
1. Sign in at https://console.wasabisys.com/
2. On the Wasabi menu (left), click Buckets
3. In the upper right of the Console panel, click Create Bucket (new accounts may show a large blue Create Bucket button in the middle — either works)
4. In Select Bucket Name, enter a unique DNS-compliant name (3–63 characters; lowercase letters, numbers, periods, dashes; must start with a letter or number)
5. Select the region (geographic location). Wasabi shows the region name and service URL together — write down the region code (example: eu-central-1). You can use the copy icon next to the region URL if shown
6. Click Create Bucket now to finish with defaults, or click Next only if you need versioning / object lock
Write down:
- Exact bucket name
- Region code (must match this bucket)
Region service URL reference: Wasabi storage regions.
---
Step 2 — Create an Access Key (Access Key ID + Secret Key)
Per Wasabi: Creating a New Access Key:
> An account can have only two access keys per user (two for Root, two per sub-user). If you already have two, delete one before creating another.
1. On the Wasabi menu (left), click Access Keys
2. Click Create Access Key
3. Choose the user type:
- Root User — fastest for a single-admin site
- Sub-User — better practice for teams (create the user first under Users with programmatic access and a policy such as WasabiFullAccess)
4. Click Create
5. On the key screen:
- Copy the Access Key
- Click Show to reveal the Secret Key, then copy it
- Or use Download (CSV) / copy to clipboard
6. Click X to close only after you have saved both values
Wasabi will not show the Secret Key again later.
---
Step 3 — (Recommended) Create a sub-user instead of Root keys
Wasabi recommends not using Root for day-to-day API access. Official path from Creating a User Account and Access Key:
1. Left menu → Groups → Create Group → name it → Save (optional but recommended)
2. Left menu → Users → Create User
3. Enter a user name → enable Programmatic access (so an API key can be created)
4. Next → add the user to a group → Next
5. Attach a policy (for a simple start click + on WasabiFullAccess) → Next → Create User → Close
6. Then create keys as in Step 2, choosing Sub-User and that user
---
Step 4 — Map values into XFile Ultra
| Field | Value |
|---|---|
| Access key ID | Access Key from Step 2 |
| Secret access key | Secret Key from Step 2 |
| Bucket name | Bucket from Step 1 |
| Region | Region code from Step 1 |
Finish in XFile Ultra
1. Open Admin → Servers → Servers management → Add new CDN (or edit an existing CDN)
2. Choose the matching CDN provider
3. Paste every value from the “What to paste” table
4. Leave Performance mode on unless you want uploads to proxy through your VPS
5. Set the server status to ON when ready
6. Click Test connection
7. Click Save
If Test connection succeeds but says Performance mode requires bucket CORS, open Performance mode requires bucket CORS and paste the rule for your provider.
---
Common problems
Bucket not found / wrong region or endpoint
The bucket name must match exactly. The region (or Contabo / IDrive endpoint, or Cloudflare Account ID) must be the one for that bucket.
Access denied / bad credentials
Wrong Access Key ID or Secret Access Key, or the key cannot read/write that bucket. Create a new key with the right permissions and paste again.
Secret key lost
Almost every provider shows the secret once. You cannot look it up later — create or regenerate a key, update XFile Ultra, and stop using the old key.
Test connection OK, browser upload fails
Usually CORS. Use the Performance mode CORS article, or turn Performance mode off temporarily while you fix it.