Log flooding with imageprocessor errors using blobstorage
Hi,
I'm using a blobstorage for the first time on cloud. It all looks good but now my log file is flooding with the following error:
ImageProcessor.Common.Exceptions.ImageProcessingException: GetResponseAsync 132 : Response status code does not indicate success: 404 (The specified blob does not exist.).
All images seem fine so I don't get where this is coming from.
Your images seems fine when you use imagecropper URL's, but when you're trying to access the file without the imagecropper url params you will get the 404 error.
I found that I had to go and set the public access level on the container to "Public read access for container and blobs". I did this using Azure Storage Explorer, right click on the blob container...Set Public Access. After I did this, the error went away.
Log flooding with imageprocessor errors using blobstorage
Hi,
I'm using a blobstorage for the first time on cloud. It all looks good but now my log file is flooding with the following error:
ImageProcessor.Common.Exceptions.ImageProcessingException: GetResponseAsync 132 : Response status code does not indicate success: 404 (The specified blob does not exist.).
All images seem fine so I don't get where this is coming from.
Does anyone have a idea?
Accidentally I had the same issue yesterday.
For me the solution was deleting the web.config in the media folder.
See https://our.umbraco.com/forum/using-umbraco-and-getting-started/88940-filesystemprovider-doesnt-map-the-media-folder-on-774 as well.
Your images seems fine when you use imagecropper URL's, but when you're trying to access the file without the imagecropper url params you will get the 404 error.
Ah, I'll have a look. Thanks for directing me to the possible solution.
Deleting web.config from media folder didn't help. Any other ways to fix that?
Has anyone determined how to fix this?
I'm using a private Azure Blob Storage container and I got these exceptions. Changing
in my web.config to
resolved this issue for me.
I found that I had to go and set the public access level on the container to "Public read access for container and blobs". I did this using Azure Storage Explorer, right click on the blob container...Set Public Access. After I did this, the error went away.
is working on a reply...