This is my config/filesystems.php:

'b2' => [
        'driver' => 's3',
        'key' => '*************',
        'secret' => '**************',
        'region' => 'us-west-002',
        'bucket' => '***********',
        'endpoint' => '',
        'use_path_style_endpoint' => true, // <-- required for B2
    ],

The configuration has been verified using 's3cmd', and I can upload files successfully.

In my code, I use a simple:

use Illuminate\Support\Facades\Storage;
try {
    Storage::disk('b2')->put('/test-b2.txt', 'Hello from Laravel B2 root!');
    echo "✅ Uploaded!";
} catch (\Exception $e) {
    logger()->error('B2 Upload Error', ['message' => $e->getMessage()]);
    dd($e->getMessage());
}

The script returns: ✅ Uploaded!

But no files appear in my bucket. It used to work in past Laravel versions, but it does not anymore.

I've tried so many alternative using ChatGPT and they all failed.

So you're my last resort.

Thank you,

G

This is my config/filesystems.php:

'b2' => [
        'driver' => 's3',
        'key' => '*************',
        'secret' => '**************',
        'region' => 'us-west-002',
        'bucket' => '***********',
        'endpoint' => 'https://s3.us-west-002.backblazeb2',
        'use_path_style_endpoint' => true, // <-- required for B2
    ],

The configuration has been verified using 's3cmd', and I can upload files successfully.

In my code, I use a simple:

use Illuminate\Support\Facades\Storage;
try {
    Storage::disk('b2')->put('/test-b2.txt', 'Hello from Laravel B2 root!');
    echo "✅ Uploaded!";
} catch (\Exception $e) {
    logger()->error('B2 Upload Error', ['message' => $e->getMessage()]);
    dd($e->getMessage());
}

The script returns: ✅ Uploaded!

But no files appear in my bucket. It used to work in past Laravel versions, but it does not anymore.

I've tried so many alternative using ChatGPT and they all failed.

So you're my last resort.

Thank you,

G

• php
• laravel
• laravel-11
• backblaze

2 Answers 2

I found how to make it work.

First you need to install or re-install a specific version "3.336" of "aws/aws-sdk-php" in Laravel 11 or 12. Using composer:

composer require aws/aws-sdk-php:3.336

Then the driver needs to be as follow:

'b2' => [
            'driver' => 's3',
            'key' => '********',
            'secret' => '*********',
            'region' => 'us-west-002',
            'bucket' => '******',
            'endpoint' => 'https://s3.us-west-002.backblazeb2',
            'use_path_style_endpoint' => true, // <-- required for B2
            'visibility' => 'private',
            'throw' => true,
            'checksum' => false,
            'options' => [
                'http' => [
                    'verify' => false, // just in case, for SSL edge cases
                    'headers' => [
                        'x-amz-checksum-crc32' => null,
                    ],
                ],
            ],
        ],

The 'key', 'secret', 'bucket' keys should be your confidential values.

The 'region' and 'endpoint' should be what's after 'Endpoint' in your bucket on Backblaze UI.

The 'visibility' should be the same as in BackBlaze bucket's configuration for the files you upload. 'public' or 'private' is up to you but they need to be the same at both places.

The 'throw' can be 'true' or 'false' depending if you want an Exception to be thrown when there's an error. (I personally recommend true).

The 'checksum' must be set to 'false'.

The 'options' isn't listed nowhere in the documentation but if that section is not there, it does not work. (on my side at least).

Took me 2 days to figure everything out, hope it will help some of you struggling with the same issue.

Bests,

G

According to the documentation, it appears that failure to write to disk doesn't throw an error by default:

Failed Writes

If the put method (or other "write" operations) is unable to write the file to disk, false will be returned:

if (! Storage::put('file.jpg', $contents)) {
    // The file could not be written to disk...
}

If you wish, you may define the throw option within your filesystem disk's configuration array. When this option is defined as true, "write" methods such as put will throw an instance of League\Flysystem\UnableToWriteFile when write operations fail:

'public' => [
    'driver' => 'local',
    // ...
    'throw' => true,
],

Maybe setting the throw option will help you find out what the error is and the underlying problem.