Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

somenet77's avatar

Disk named do-spaces cannot be accessed

I have already configured my disk spaces in Digital Ocean Spaces, which worked fine till yesterday. However, after my latest deployment, I encountered the 'disk cannot be accessed' issue. Below is my setting, which worked before.

But this works fine on my local computer. When I deploy to my production server, it triggers the above error.

'do-spaces' => [
            'driver' => 's3',
            'key' => env('DO_ACCESS_KEY_ID'),
            'secret' => env('DO_SECRET_ACCESS_KEY'),
            'region' => env('DO_DEFAULT_REGION'),
            'bucket' => env('DO_BUCKET'),
            'url' => env('DO_URL'),
            'endpoint' => env('DO_ENDPOINT'),
            'use_path_style_endpoint' => env('DO_USE_PATH_STYLE_ENDPOINT', false),
            'throw' => false,
            'bucket_endpoint' => true, 
            'root' => 'skmdd/media',
            'visibility' => 'public',
        ],

When I set throw to true, I get this issue

Unable to write file at location: 16763/signature.png. Error executing "PutObject"
0 likes
3 replies
Glukinho's avatar

How different is your production .env file compared to local one?

somenet77's avatar

almost the same configuration for Digital Ocean Spaces.

Glukinho's avatar

Almost the same or the same?

Did you try to clear config cache?

Please or to participate in this conversation.