Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Frans de Jong 541 posts 1788 karma points MVP 3x c-trib
    Jan 07, 2020 @ 21:19
    Frans de Jong

    Log flooding with imageprocessor errors using blobstorage


    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?

  • Corné Strijkert 80 posts 455 karma points c-trib
    Jan 09, 2020 @ 12:49
    Corné Strijkert

    Accidentally I had the same issue yesterday.

    For me the solution was deleting the web.config in the media folder.

    See 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.

  • Frans de Jong 541 posts 1788 karma points MVP 3x c-trib
    Jan 09, 2020 @ 13:38
    Frans de Jong

    Ah, I'll have a look. Thanks for directing me to the possible solution.

  • Alexander 33 posts 83 karma points
    Jan 18, 2021 @ 15:05

    Deleting web.config from media folder didn't help. Any other ways to fix that?

  • Bobi 345 posts 949 karma points
    Apr 27, 2022 @ 01:49

    Has anyone determined how to fix this?

  • Georg 1 post 71 karma points
    Nov 29, 2022 @ 09:51

    I'm using a private Azure Blob Storage container and I got these exceptions. Changing

    <add key="AzureBlobFileSystem.UsePrivateContainer:media" value="false"/>

    in my web.config to

    <add key="AzureBlobFileSystem.UsePrivateContainer:media" value="true"/>

    resolved this issue for me.

  • Angel 49 posts 105 karma points
    Aug 03, 2023 @ 16:43

    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.

Please Sign in or register to post replies

Write your reply to: