Copied to clipboard

Flag this post as spam?

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


  • Johannes Kjellberg 1 post 71 karma points
    Nov 05, 2020 @ 10:34
    Johannes Kjellberg
    0

    Image processor error

    Hi, I get an error in the Umbraco log: ERROR ImageProcessor.Web.HttpModules.ImageProcessingModule - ImageProcessor.Common.Exceptions.ImageProcessingException: ProcessImageAsync 609 : No image exists at http://[storageName]dev.blob.core.windows.net/media/1140/image1.jpg. But the url is incorrect! It should be http://[storageName]prod.blob.core.windows.net/media/1140/image1.jpg. So why are ImageProcessor looking at the wrong address? Where and how do I correct this? I'm using Azure and ImageProcessor 2.9.1 and ImageProcessor.Web 4.12.1.

    Thanks in advance for help!

    Rgds Johannes

  • Marc Goodson 2155 posts 14408 karma points MVP 9x c-trib
    Nov 18, 2020 @ 20:29
    Marc Goodson
    0

    Hi Joahnnes

    It sounds like one of the config settings for Image Processor or Umbraco's File System Providers is pointing at the wrong container?

    You can usually check the blob storage container settings for your Umbraco implementation in

    /config/filesystemproviders.config /config/imageprocessor/security.config /config/imageprocessor/cache.config

    There is an article here that explains about the configuration for V7 that you could cross reference:

    https://our.umbraco.com/Documentation/Extending/FileSystemProviders/Azure-Blob-Storage/index-v7

    I say 'usually' as sometimes the connection string for blob storage will have been moved to the web.config appsettings.

    regards

    Marc

  • Bobi 352 posts 956 karma points
    Apr 27, 2022 @ 03:44
    Bobi
    0

    I have the same issue in v8.18.0. Is there a fix for this?

  • ivan 41 posts 182 karma points
    Oct 05, 2022 @ 14:16
    ivan
    0

    Hello Bob,

    Did you already fixed this?

    I have also issue on this on v8.18.5

    Thanks

  • Arun 141 posts 404 karma points
    Feb 09, 2023 @ 11:35
    Arun
    0

    Did anyone get the solution?

    I was able to bypass this error log with the web config rule
    but didn't get any optimal solution yet.

    <rule name="Block none existing image files before ImageProcessor" stopProcessing="true">
         <match url="^media/" /> 
         <conditions><add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /></conditions>
         <action type="CustomResponse" statusCode="404" statusReason="File or Directory not found." statusDescription="The resource you are looking for might have been removed." />
    </rule>
    
Please Sign in or register to post replies

Write your reply to:

Draft