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 532 posts 1778 karma points MVP 2x c-trib
    Jan 07, 2020 @ 21:19
    Frans de Jong
    0

    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?

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

    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.

  • Frans de Jong 532 posts 1778 karma points MVP 2x c-trib
    Jan 09, 2020 @ 13:38
    Frans de Jong
    0

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

  • Alexander 31 posts 81 karma points
    Jan 18, 2021 @ 15:05
    Alexander
    0

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

  • Bobi 342 posts 935 karma points
    Apr 27, 2022 @ 01:49
    Bobi
    0

    Has anyone determined how to fix this?

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

    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.

Please Sign in or register to post replies

Write your reply to:

Draft