Not able to view image from storage folder in production

@SilenceBringer I tried doing what you have suggested both url are same.

@shariff what if you put the url in the browser?

Can you check that symlink was really created on the server?

@SilenceBringer If I check in browser its showing as Not Found. The symlink in created

@shariff check file really exists on the specified path.

@SilenceBringer It is there. This can be a problem of server?

@shariff maybe. try to create test file (not webp) in storage root and access it it browser directly.

@Sinnbeck It is present in the storage directory.

@shariff that is not really answering my question. What is the exact path from the root of your laravel project?

@Sinnbeck http://domain-name/storage/products/1/test-image.webp

@shariff that's an url. I am talking about on disk. Something like /storage/app/public/products/1/test-image.webp

Hint : it should be the above

@sinnbeck @silencebringer When I uploaded a image instorage/app/public/test-image.webp and try to access using asset("storage/test-image.webp"). I can able to view the image. Same image I uploaded in storage/app/public/products/1/test-image.webp I cannot able to access it.

@shariff good. Correct location then

Is the file in /public/storage/products/1/test-image.webp as well?

@Sinnbeck yeah it is available

@shariff ok weird then. Did you try it with any other file type? Like jpeg or png? Any chance that you have a route that matches the pattern?

@Sinnbeck Yeah I tried it is same for all images Or it may be any permission issue for directory?

@shariff what is the error? 404?

@Sinnbeck yeah its 404

@shariff Just to rule out routes, can you try adding return; right after <?php in web.php? And if your routes are cached, try clearing them as well php artisan route:clear

@Sinnbeck I tried but no luck

@shariff I assume the app stopped working when you did that?

Then I dont know sadly. Perhaps the server provider can spot some issue (which I then assume has to do with .htaccess or nginx)

@DougReimers Please create your own thread.

@shariff Ok good to know. Never seen permissions give 404, but now I know that for next time :)

@Sinnbeck In local it is working fine without assigning any permission. Only in server it is showing like that. May be some problem with server. If I add any new directory again I should assign a permissions or this will work?

'local' => [
    'driver' => 'local',
    'root' => storage_path('app'),
    'permissions' => [
        'file' => [
            'public' => 0777,
            'private' => 0600,
        ],
        'dir' => [
            'public' => 0777,
            'private' => 0700,
        ],
    ],
],

@shariff I assume it would work like that, but best to test it :)

@Sinnbeck thank you