Disk named public cannot be accessed

[Kokil]

I'm encountering an issue while using laravel-medialibrary version ^10.9 .
When i run php artisan media-library:regenerate it give:

Media id 1: Disk named public cannot be accessed

I have verified my filesystem configuration in config/filesystems.php and it appears to be set correctly:

'public' => [
    'driver' => 'local',
    'root' => storage_path('app/public'),
    'url' => env('APP_URL').'/storage',
    'visibility' => 'public',
    'throw' => false,
],

Could you please guide me in troubleshooting this issue? Is there anything specific I should be aware of when using laravel-medialibrary with Laravel 10.x?

[parallels999]

Folder permissions

[Kokil]

Folder permissions

I don't think it's due to folder permissions.
after your comment, I tried giving even 777 to the storage folder.

If I upload from the backend it's working.

[francoism90]

@Kokil What is your environment? Is this Laravel Sail or production?

[Kokil]

@Kokil What is your environment? Is this Laravel Sail or production?

It's in the local environment. i haven't tested that in production.

[francoism90]

@Kokil I also think this is a permission issue.

[Kokil]

Any Suggestion?

[francoism90]

I really don't know, if your public correctly defined in config/filesystems.php? Tried clearing your cache? Also does the symlink correctly exists?

Anyway, I don't think this is a package issue, sorry.

[Kokil]

After your comment, I take the following step :

1. Get the fresh filesystems.php.
2. I run artisan migrate:fresh --seed
3. cache: clear, remove old symlink, regenerate symlink
4. i upload the media from backend upload success.
5. after that i run : php artisan media-library:regenerate
   again same
   

PHP 8.1.7 & Laravel Framework 10.11.0
Note :
I migrate this application laravel 8 to laravel 10.
at laravel 8 i was working fine.

[bhojkamal]

I also got same error on laravel 10. but it was working in same way in laravel 9. The error is

"message": "Disk named `public` cannot be accessed",
    "exception": "Spatie\\MediaLibrary\\MediaCollections\\Exceptions\\DiskCannotBeAccessed",

[Kokil]

Yes i also upgrade from laravel 8 in laravel 8 it was working fine.

[Kokil]

any update on this ?

[fredsal]

@Kokil Hi, make a debug, and feel free to make a PR with the fix

laravel/compare/v8.x...v10.x

[middaparka]

I'm also seeing this issue, but only on PHP 8.2(.8) - 8.1(.12) is behaving as expected. (Both running Laravel 10.15.0.)

Specifically the file_put_contents call in the writeToFile method within …/laravel/vendor/league/flysystem-local/LocalFilesystemAdapter.php (line ~123) is returning false and triggering the exception, although the error_get_last() call response is null.

I'm assuming there must be a PHP CLI configuration difference that's causing this - did anyone else determine what their issue was?

[middaparka]

As an update, I can't see any significant PHP CLI config differences that could trigger this.

(Unless some really weird things are happening in the absence of an ODBC extension.) 🤔

To clarify, this is simply switching between the active PHP CLI version on the same VM instance, so the CLI commands are running as the same user in the same environment.

[titantwentyone]

Just some more info but have come across this using Sail and PHP 8.1.20 and Laravel 10.19. I am automating the import of some media. Oddly, The first 3 images upload fine, but the fourth stops with this same error. I did this multiple times with the same result. I even changed out the order of the imports to see if it was an image that was causing the issue but no joy.

[nocodelab]

Hello guys, did anyone solve this issue? I'm having the same problem with L10 and latest version of MediaLibrary.

[middaparka]

Not that I'm aware of. 😔

I still suspect it's due to some PHP change between PHP 8.1 and 8.2, perhaps relating to how streams are handled when executing via CLI rather than via FPM, but that's just a hunch.

The fact that it only occurs during CLI/Artisan command execution also feels significant, but it's not an obvious permissions issue. Having compared my PHP FPM and CLI configs in detail I couldn't see any meaningful differences that would cause this issue.

[nocodelab]

I confirm that it happens just via CLI :/

[Kokil]

Yes i also faced in CLI only.

[nocodelab]

I don't know if this can help, but I tried to change the "MEDIA_DISK" to public and everything works well.
If I change the disk to another one (no matter if s3 or with local driver) the issue magically appears.
Did you also try that?

For instance, here is the secondary local filesystem which triggers the error:

        'images' => [
            'driver' => 'local',
            'root' => storage_path('app/public/medias'),
            'url' => env('APP_URL').'/medias',
            'visibility' => 'public',
            'throw' => false,
        ],

[PerikiyoXD]

Try setting 'throw' to true and send the exception it throws. This is just to debug, change it back to 'false' after testing.

[PerikiyoXD]

In my case it was a weird naming problem using <filename>.png&v=<stamp>&_=<stamp>, which is invalid extension with all the extra url stuff.

[francoism90]

Could this be an issue with the filename sanitizer?

We also had this issue, but could indeed see the error with throw => true.

[middaparka]

Sadly the error I'm seeing is a generic unable to write to file message, which is strange as a zero byte file is being successfully created.

I still wonder if this is somehow related to the way streams work when using CLI as opposed to "normal" web access.

[PerikiyoXD]

Maybe CLI and FPM users differ. I've happened to face this issue with write-permissions on folders.

[liamseys]

Has anyone fixed this issue already?

[PerikiyoXD]

Did you try setting 'throw' => true, and debug from there?

[liamseys]

 's3' => [
            'driver' => 's3',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'region' => env('AWS_DEFAULT_REGION'),
            'bucket' => env('AWS_BUCKET'),
            'url' => env('AWS_URL'),
            'endpoint' => env('AWS_ENDPOINT'),
            'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', false),
            'throw' => false,
        ],

        'media' => [
            'driver' => 's3',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'region' => env('AWS_DEFAULT_REGION'),
            'bucket' => env('AWS_BUCKET'),
            'url' => env('AWS_URL'),
            'endpoint' => env('AWS_ENDPOINT'),
            'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', false),
            'throw' => false,
            'visibility' => 'public',
            'root' => 'media',
        ],

Only thing I did was another media disk set it to public and changed the root to 'media'. I'm trying to upload it to this disk from Spatie's Media Library.

[PerikiyoXD]

Provide more context. 'public' disk is the issue in this thread. I don't know if you're using S3 or other services and I recommend enabling "throw" => "true" to try diagnosing the issue more in depth.

[alhelwany]

It's a folder permission issue.

I ran this and it worked

sudo chgrp -R www-data storage; sudo chmod -R ug+rwx storage

Laravel 10

[wanzkarat]

I had the same error when adding new images (not regenerate) and on my side it was due to a wrong filename I tried to set (set the file extension incorrectly). Nothing to do with permissions on my end

[rohjay]

I was having this issue running laravel locally and trying to seed the db + drop in some test logo images. After doing the chgrp as suggested by @GeorgeTheNerd and that not having fixed the issue, I ran my command as www-data like this:

> sudo -u www-data php artisan migrate:fresh --seed

That did the trick 👍 hope this helps a fellow wayward dev =]

[jarbasmedeiros]

@Kokil Go to the filesystems file and change the public disk, comment 'visibility' => 'public' and add 'ACL' => 'public-read' to the array. it will stay like this:

'public' => [
            'driver' => 'local',
            'root' => storage_path('app/public'),
            'url' => env('APP_URL').'/storage',
            'ACL' => 'public-read',
            //'visibility' => 'public',
            'throw' => false,
        ],

It works for me : D