Backblaze B2 ফাইল স্টোরেজ
S3 এন্ডপয়েন্ট ও রিজিয়ন দিয়ে Backblaze B2-কে ফাইল সার্ভারের ধরন হিসেবে যোগ করে, সরাসরি ডাউনলোড ও আপলোডসহ। প্রিমিয়াম।
The Backblaze B2 plugin adds Backblaze B2 as a file server type. Files are kept in a B2 bucket through its S3-compatible endpoints: downloads go out with signed links straight from Backblaze, and with direct uploads on, browsers send their pieces to the bucket themselves. B2 is among the cheapest places to keep large amounts of data, which is why many file hosts start here.
It is a preset over the core's S3 driver: the plugin fills in Backblaze's endpoint pattern and regions, you type the key and the bucket.
Who it is for
Owners who want cheap, durable storage behind the site, or a second place for files when the local disk is full. Several B2 servers can sit beside local, Direct, FTP and other bucket servers; File servers explains how the site picks one for each upload.
Switching it on
Premium plugin, key storage-backblaze. Buy it on lcpanel.com, press Check again now on Admin → Configuration → License, then switch it on at Admin → Extensions → Plugins (the Manage Plugins page). The plugin's settings carry a single How to use note; everything real is typed on the server.
Adding the server
Admin → Infrastructure → File Servers → Add File Server. On the Add Storage Server page choose Backblaze B2 as the Server Type. The page says: Backblaze B2 with an S3-compatible application key (make the key with "Allow access to all buckets" off and pick the bucket). The region is in your bucket endpoint.
| Field | What to type |
|---|---|
| Access Key, Secret Key | The application key's id and the key itself. Make the key for one bucket, with Allow access to all buckets off. |
| Bucket | The bucket's name. |
| Region | Taken from your bucket's endpoint: us-west-000, us-west-001, us-west-002, us-west-004 (default), us-east-005 or eu-central-003. |
| Endpoint | s3.{region}.backblazeb2.com, with {region} filled from the field above. |
| Path-style URLs | Off. |
| Key Prefix | Optional folder inside the bucket. |
| Direct Downloads | Yes = signed links straight from B2; No = streamed through the site. |
| Direct Uploads | Yes = the browser uploads to B2 in parallel pieces (needs the CORS rule below). |
| Public / CDN URL (optional) | A CDN in front of the bucket. |
| Signed Link Lifetime | Seconds a signed link lives; 3600 by default. |
Then Server Label, Status, and the tabs shared by every server: CDN Support, Storage Options (Max Storage, Server Priority), Geo Targeting, Account Type Targeting, Installation Guidance. Save and test tries the keys at once.
CORS for direct uploads
Direct uploads send pieces from the visitor's browser to Backblaze, so the bucket must allow PUT from your domain. The rule to paste is printed under CORS rule the bucket needs for direct uploads on the server form, and on the S3 Connection Test page of the free Amazon S3 File Storage plugin. Until the rule is there the uploader falls back to the site's chunk.php road, which still works but passes every byte through your server (Uploads).
Downloads
Signed links take the traffic off your server. Note Site Settings → File Downloads → Direct bucket links only for unlimited speed: when on, members whose package has a Download Speed limit are streamed through the site so the cap holds, while unlimited packages get the direct link (Downloads).
Tips
- B2 regions are not interchangeable: a key made in one region does not reach a bucket in another. Read the region off the bucket's endpoint.
- Where uploads land is decided by Site Settings → File Uploads: Least Used Space, Specific Server, Until Full (by priority) or Random Server.
- The S3 Connection Test page checks every bucket server with one click; use it after rotating a key.
- Deletes and moves on bucket servers are queued and run by the cron (Files → Action Queue); keep the cron line in place (Scheduled jobs).