Previously, I explained the process of integrating Backblaze B2 with Cloudflare and binding your own domain. I’ll also briefly record how to integrate WordPress with Backblaze storage.
Before integration, it’s recommended to bind Cloudflare first. Of course, if you don’t mind, you can ignore this step.
1. Create a Backblaze bucket
After creation, we need to use an endpoint, for example: s3.us-east-005.backblazeb2.com
2. Create a Backblaze application key (try not to use the main application key).
Therefore, create a separate application key. Go to the next step to create a key for a specific bucket.
After creation, be sure to save the application key, as it only appears once.
We need keyID and applicationKey.
3. Install the Media Cloud plugin in the WordPress admin panel (or another plugin).
Media Cloud Settings:
Enable Cloud Storage: Turn on
CLOUD PROVIDER Settings:
Storage Provider: Select Backblaze S3 Compatible
Access Key: Enter the keyID of the Backblaze application key.
Secret: Enter the applicationKey of the Backblaze application key.
Bucket: Enter the name of the bucket corresponding to your application key in Backblaze.
Bucket Privacy: Select the Backblaze bucket type: Public.
Custom Endpoint: Enter the Backblaze bucket endpoint.
Path Style Endpoint: Enabled.
UPLOAD HANDLING Settings:
Upload Images: Enabled (Uploads image files to cloud storage.)
DELETING FILES Settings:
Delete Uploaded Files: Enabled (Deletes uploaded files from WordPress.) (Server deletes uploaded files)
It depends on your needs. I don’t save images locally on the server, so I enabled it. If your local server has enough hard drive space, you don’t need to enable it.
Delete From Storage: Enabled (Enabling this option will also delete the file from cloud storage when you delete it from your media library)
CDN SETTINGS:
CDN Base URL: Enter the Cloudflare domain name you’ve bound to your Backblaze bucket.
Save the above settings. You can change the remaining settings as needed.