1. The perfect tool for BackBlaze B2 storage. Browse your cloud storage easily. Play and cast compatible media files from cloud. Preview and share files, images and documents.
2. Backblaze Mobile for iOS let’s you access your files whether they were backed up to Backblaze from your Mac or your PC. Thumbnails Once you’ve downloaded a photo, the file list will show a thumbnail version of the file so you can easily select just the right photo when you’re ready to share.

1. Veeam Backblaze B2
2. Backblaze B2 Cloud Storage

lovedigit

Network license

Version 3.20.0.beta.1 PHP version 7.4.16 Database driver MariaDB Database version 10.3.25 Web browser Chrome. The S3 Compatible API for Backblaze B2 Cloud Storage allows 1000’s of integrations to work with B2 natively. If you’re new to the S3 Compatible API, please see our Getting Started Guide. If you have any trouble using NetApp Cloud Sync with B2, please let us know by emailing us at b2feedback@backblaze.com. ‎The perfect tool for Backblaze B2 cloud storage. Play your media files instantly without downloads. Compatible with all macOS media formats. Apple certified security using secure connections.

▶ Reproduction steps

1. Upload large number of images inside an album
2. Delete album so all images are queued at once for deletion
3. Check database chv_queues table and error log

😢 Unexpected result
I created a separate chevereto instance with v3.20.0.beta.1, setup entirely new backblaze bucket and created an external storage with it.
After initial setup. I uploaded 1000 images to this website.
Queues were however processed. It was throwing same error trace as it is logged on my actual website permanently. But, on test website, it was able to process request after several failed attempts.
I am not knowledgeable enough to diagnose it myself to find the root cause.
If someone wants to test this on their website, here is the zip file with 1000 images. Please make sure that you upload them inside album, and delete them all at once. If your deletion queue has only few hundred rows, it will process without errors.
Download 1000 images: https://gofile.io/d/J44aAg
This indicates that it is actually affected by number of rows in deletion queue to be processed rather than the size of the backblaze bucket which we initially suspected as culprit.
But, I can only guess. Rodolfo will be able to find the issue.
I have 75K images pending for deletion. I really need a fix for this. There are several illegal images which needs to be removed from the server. 3 out of 5 of my external storages are on backblaze now. It is affecting the normal operations of the website. Please help.
📃 Error log message
Aw, snap! Internal Server Error [debug @ print,error_log] - https://v3-docs.chevereto.com/setup/debug.html
Fatal error [0]:
Triggered in /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php:424
Stack trace:
#0 /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php(452): esacB2Client->getFile()
#1 /var/www/chev_test/html/app/lib/classes/class.queue.php(161): esacB2Client->deleteFile()
#2 /var/www/chev_test/html/app/cron.php(39): CHVQueue:rocess()
#3 /var/www/chev_test/html/app/cron.php(26): storageDelete()
#4 /var/www/chev_test/html/app/loader.php(296): require_once('/var/www/chev_test/html/app/cron.php')
#5 /var/www/chev_test/html/cron.php(23): include_once('/var/www/chev_test/html/app/loader.php')

• Processing cleanUnconfirmedUsers
• Processing removeDeleteLog
• Processing deleteExpiredImages
• Processing storageDelete

Aw, snap! Internal Server Error [debug @ print,error_log] - https://v3-docs.chevereto.com/setup/debug.html
Fatal error [0]:
Triggered in /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php:424
Stack trace:
#0 /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php(452): esacB2Client->getFile()
#1 /var/www/chev_test/html/app/lib/classes/class.queue.php(161): esacB2Client->deleteFile()
#2 /var/www/chev_test/html/app/cron.php(39): CHVQueue:rocess()
#3 /var/www/chev_test/html/app/cron.php(26): storageDelete()
#4 /var/www/chev_test/html/app/loader.php(296): require_once('/var/www/chev_test/html/app/cron.php')
#5 /var/www/chev_test/html/cron.php(23): include_once('/var/www/chev_test/html/app/loader.php')
Aw, snap! Internal Server Error [debug @ print,error_log] - https://v3-docs.chevereto.com/setup/debug.html
Fatal error [0]:
Triggered in /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php:424
Stack trace:
#0 /var/www/chev_test/html/app/vendor/esac/backblaze-b2/src/Client.php(452): esacB2Client->getFile()
#1 /var/www/chev_test/html/app/lib/classes/class.queue.php(161): esacB2Client->deleteFile()
#2 /var/www/chev_test/html/app/cron.php(39): CHVQueue:rocess()
#3 /var/www/chev_test/html/app/cron.php(26): storageDelete()
#4 /var/www/chev_test/html/app/loader.php(296): require_once('/var/www/chev_test/html/app/cron.php')
#5 /var/www/chev_test/html/cron.php(23): include_once('/var/www/chev_test/html/app/loader.php')

• Processing tryForUpdates
• Processing cleanUnconfirmedUsers
• Processing removeDeleteLog
• Processing deleteExpiredImages

--
[OK] Cron tasks ran

• Processing removeDeleteLog
• Processing tryForUpdates
• Processing cleanUnconfirmedUsers
• Processing storageDelete
• Processing deleteExpiredImages

Last updated November 06, 2020

Backblaze B2 Cloud Storage (B2) public and private buckets can be used as origins with Fastly.

TIP: Backblaze offers an integration discount that eliminates egress costs to Fastly when using Backblaze B2 Cloud Storage as an origin. In addition, Backblaze also offers a migration program designed to offset many of the data transfer costs associated with switching from another cloud provider to Backblaze. To ensure your migration has minimal downtime, contact support@fastly.com.

Before you begin

Before you begin the setup and configuration steps required to use B2 as an origin, keep in mind the following:

• You must have a valid Backblaze account. Before you can create a new bucket and upload files to it for Fastly to use, you must first create a Backblaze account at the Backblaze website.
• Backblaze provides two ways to set up and configure B2. B2 can be set up and configured using either the Backblaze web interface or the B2 command line tool. Either creation method works for public buckets. To use private buckets, however, you must use the B2 command line tool. For additional details, including instructions on how to install the command line tool, read Backblaze's B2 documentation.
• Backblaze provides two APIs for integrating with Backblaze B2 Cloud Storage. You can use the B2 Cloud Storage API or the S3 Compatible API to make your B2 data buckets available through Fastly. The S3 Compatible API allows existing S3 integrations and SDKs to integrate with B2. Buckets and their specific application keys created prior to May 4th, 2020, however, cannot be used with the S3 Compatible API. For more information, read Backblaze's article on Getting Started with the S3 Compatible API.

Using Backblaze B2 as an origin

To use B2 as an origin, follow the steps below.

Creating a new bucket

Data in B2 is stored in buckets. Follow these steps to create a new bucket via the B2 web interface.

TIP: The Backblaze Guide provides details on how to create a bucket using the command line tool.

1. Log in to your Backblaze account. Your Backblaze account settings page appears.
2. Click the Buckets link. The B2 Cloud Storage Buckets page appears.

3. Click the Create a Bucket link. The Create a Bucket window appears.

4. In the Bucket Unique Name field, enter a unique bucket name. Each bucket name must be at least 6 alphanumeric characters and can only use hyphens (-) as separators, not spaces.
5. Click the Create a Bucket button. The new bucket appears in the list of buckets on the B2 Cloud Storage Buckets page.
6. Upload a file to the new bucket you just created.

Veeam Backblaze B2

NOTE: Buckets created prior to May 4th, 2020 cannot be used with the S3 Compatible API. If you do not have any S3 Compatible buckets, Backblaze recommends creating a new bucket.

Backblaze B2 Cloud Storage

Uploading files to a new bucket

Once you've created a new bucket in which to store your data, follow these steps to upload files to it via the B2 web interface.

TIP: The Backblaze Guide provides details on how to upload files using the command line tool.

1. Click the Buckets link in the B2 web interface. The B2 Cloud Storage Buckets page appears.
2. Find the bucket details for the bucket you just created.
3. Click the Upload/Download button. The Browse Files page appears.
4. Click the Upload button. The upload window appears.
5. Either drag and drop any file into the window or click to use the file selection tools to find a file to be uploaded. The name and type of file at this stage doesn't matter. Any file will work. Once uploaded, the name of the file appears in the list of files for the bucket.
6. Find your bucket's assigned hostname so you can set up a Fastly service that interacts with B2.

Finding your bucket's assigned hostname

To set up a Fastly service that interacts with your B2, you will need to know the hostname Backblaze assigned to the bucket you created and uploaded files to.

Find your hostname in one of the following ways:

• Via the B2 web interface when you're using the standard B2 Cloud Storage API. Click the name of the file you just uploaded and examine the Friendly URL and Native URL fields in the Details window that appears. The hostname is the text after the https:// designator in each line that matches exactly.

• Via the command line and the B2 Cloud Storage API. Run the b2 get-account-info command on the command line and use the hostname from the downloadUrl attribute.

• Via the B2 web interface when you're using the S3 Compatible API. Click the Buckets link and find the bucket details for the bucket you just created. The hostname is the text in the Endpoint field.

Creating a Backblaze application key for private buckets

Your Backblaze master application key controls access to all buckets and files on your Backblaze account. If you plan to use a Backblaze B2 private bucket with Fastly, you should create an application key specific to the bucket.

NOTE: The Backblaze documentation provides more information about application keys. When creating application keys for your private bucket, we recommend using the least amount of privileges possible. You can optionally set the key to expire after a certain number of seconds (up to a maximum of 1000 days or 86,400,000 seconds). If you choose an expiration, however, you'll need to periodically create a new application key and then update your Fastly configuration accordingly each time.

Via the web interface

To create an application key via the B2 web interface:

1. Click the App Keys link. The Application Keys page appears.

2. Click the Add a New Application Key button. The Add Application Key window appears.

3. Fill out the fields of the Add Application Key controls as follows:
   • In the Name of Key field, enter the name of your private bucket key. Key names are alphanumeric and can only use hyphens (-) as separators, not spaces.
   • From the Allow access to Bucket(s) menu, select the name of your private bucket.
   • From the Type of Access controls, select Read Only.
   • Leave the remaining optional controls and fields blank.

4. Click the Create New Key button. A success message and your new application key appear.

5. Immediately note the keyID and the applicationKey from the success message. You'll use this information when you implement header-based authentication with private objects.

Via the command line

To create an application key from the command line, run the create-key command as follows:

where <bucketName> <keyName> represents the name of the bucket and key you created. For example:

The keyID and the applicationKey are the two values returned.

NOTE: Application keys created prior to May 4th, 2020 cannot be used with the S3 Compatible API.

Creating a new service

To create a new Fastly service, you must first create a new domain and then create a new Host and edit it to accept traffic for B2. Instructions to do this appear in our guide to creating a new service. While completing these instructions, keep the following in mind:

1. When you create the new Host, enter the B2 bucket's hostname in the Hosts field on the Origins page.
2. When you edit the Host details on the Edit this host page, confirm the Transport Layer Security (TLS) area information for your Host. Specifically, make sure you:
   • secure the connection between Fastly and your origin.
   • enter your bucket's hostname in the Certificate hostname field.
   • select the checkbox to match the SNI hostname to the Certificate hostname (it appears under the SNI hostname field).
3. Also when you edit the Host, optionally enable shielding by choosing the appropriate shielding location from the Shielding menu. When using B2 Cloud Storage, this means you must choose a shielding location closest to the most appropriate Backblaze data center. For the data centers closest to:
   • Sacramento, California (in the US West region), choose San Jose (SJC) from the Shielding menu.
   • Phoenix, Arizona (in the US West region), choose Palo Alto (PAO) from the Shielding menu.
   • Amsterdam, Netherlands (in the EU central region), choose Amsterdam (AMS) from the Shielding menu.
4. Decide whether or not you should specify an override Host in the Advanced options area:
   • If you're using the S3 Compatible API, skip this step and don't specify an override Host.
   • If you're not using the S3 Compatible API, in the Override host field in the Advanced options, enter an appropriate address for your Host (e.g., s3-uswest-000.backblazeb2.com or f000.backblazeb2.com).

Using the S3 Compatible API

Using the S3 Compatible API with public objects

To use the S3 Compatible API with public objects, you will need to make sure the Host header contains the name of your B2 Bucket. There are two ways to do this, both of which require you to get your region name which will be the 2nd part of your S3 Endpoint. So if your S3 Endpoint is s3.us-west-000.backblazeb2.com, this means your region will be us-west-000.

1. In the Origin you created set the Override host field in the Advanced options to <bucket>.s3.<region>.backblazeb2.com (e.g., testing.s3.uswest-000.backblazeb2.com)

2. Create a VCL Snippet. When you create the snippet, select within subroutine to specify its placement and choose miss as the subroutine type. Then, populate the VCL field with the following code. Be sure to change specific values as noted to ones relevant to your own B2 bucket - in this case var.b2Bucket would be 'testing' and var.b2Region would be 'uswest-000'.

Using the S3 Compatible API with private objects

To use a Backblaze B2 private bucket with Fastly, you must implement version 4 of Amazon’s header-based authentication. You can do this using custom VCL.

Start by obtaining the following information from Backblaze (see Creating a Backblaze application key for private buckets):

Item	Description
Bucket name	The name of your Backblaze B2 bucket. When you download items from your bucket, this is the string listed in the URL path or hostname of each object.
Region	The Backblaze region code of the location where your bucket resides (e.g., uswest-000).
Access key	The Backblaze keyID for the App Key that has at least read permission on the bucket.
Secret key	The Backblaze applicationKey paired with the access key above.

Once you have this information, you can configure your Fastly service to authenticate against your B2 bucket using header authentication by calculating the appropriate header value in VCL.

Start by creating a regular VCL snippet. Give it a meaningful name, such as AWS protected origin. When you create the snippet, select within subroutine to specify its placement and choose miss as the subroutine type. Then, populate the VCL field with the following code (be sure to change specific values as noted to ones relevant to your own AWS bucket):

Using the B2 API

Public Objects

You'll need to make sure the URL contains your bucket name. There are two ways to do this.

• Using a Header object.

  1. Click the Create header button again to create another new header. The Create a header page appears.

  2. Fill out the Create a header fields as follows:
     • In the Name field, type Rewrite B2 URL.
     • From the Type menu, select Request, and from the Action menu, select Set.
     • In the Destination field, type url.
     • From the Ignore if set menu, select No.
     • In the Priority field, type 20.
  3. In the Source field type the '/file/<Bucket Name>' req.url.
  4. Click the Create button. A new Authorization header appears on the Content page.
  5. Click the Activate button to deploy your configuration changes.

• Alternatively create a VCL Snippet. When you create the snippet, select within subroutine to specify its placement and choose miss as the subroutine type. Then, populate the VCL field with the following code. Be sure to change the variable to the name of your own B2 bucket.

Private Objects

1. Niresh mac os x mavericks 10.9 iso download. To use a Backblaze B2 private bucket with Fastly, you must obtain an Authorization Token. This must be obtained via the command line.

2. You'll now need to authorize the command line tool with the application key you obtained.
3. You will now need to get an authorization token for the private bucket.

   e.g

   This will create a token that is valid for 86400 seconds (i.e 1 day), the default. Mac os 10.5 5 download. You can optionally change the expiration time from anywhere between 1s and 604,800 seconds (i.e 1 week).

   Take note of the generated token.

NOTE: You will need to regenerate an authorization token and update your Fastly configuration before the end of the expiration time. A good way to do this would be through Fastly's versionless Edge Dictionaries.

Passing a generated token to Backblaze

There are two ways you can pass the generated token to Backblaze. The first is using an Authorization header. This is the recommended method.

1. Click the Create header button again to create another new header. The Create a header page appears.

2. Fill out the Create a header fields as follows:
   • In the Name field, enter Authorization.
   • From the Type menu, select Request, and from the Action menu, select Set.
   • In the Destination field, enter http.Authorization.
   • From the Ignore if set menu, select No.
   • In the Priority field, enter 20.
3. In the Source field, enter the Authorization Token generated in the command line tool, surrounded by quotes. For example, if the token generated was DEC0DEC0C0A, then the Source field would be 'DEC0DEC0C0A'
4. Click the Create button. A new Authorization header appears on the Content page.
5. Click the Activate button to deploy your configuration changes.

Alternatively, the second way is to pass an Authorization query parameter.

1. Click the Create header button again to create another new header. The Create a header page appears.

2. Fill out the Create a header fields as follows:
   • In the Name field, enter Authorization.
   • From the Type menu, select Request, and from the Action menu, select Set.
   • In the Destination field, enter url.
   • From the Ignore if set menu, select No.
   • In the Priority field, enter 20.

3. In the Source field, enter the header authorization information using the following format:

   Using the previous example, that would be:

4. Click the Create button. A new Authorization header appears on the Content page.
5. Click the Activate button to deploy your configuration changes.

Back to Top