Hi Alex

How are you configuring ImageProcessor's cache? Are you storing the Cache in blob storage too? or on the local disk?

https://our.umbraco.com/Documentation/Extending/FileSystemProviders/Azure-Blob-Storage/index-v8#using-azure-blob-cache

When you request an image from Umbraco, the FileSystemProvider config is pointing to blob storage and storing/retrieving your image....

....if there are any querystring params on the request (or ImageProcessor is configured to process all image requests) then ImageProcessor 'processes the image' and stores a copy of the processed image in a cache... subsequent requests for the image are served directly from the cache...

so I'm wondering if your cache is set to disk whether that could be mucking things up when you switch?

When this occurs, if you request the same image that is not displaying but with different querystring parameters - does this return the image?? eg this would be a fresh processing request for the image, so if it's actioned and returns an image, it will show it's not an issue with Image Processor, but more to do with how an existingly processed image is cached.

You can either move the cache to blob storage, or perhaps clear out the Image Processor cache on disk, if that's how you have it configured, eg /app_data/temp/cache

regards

Marc

I have the cache.config and security.config configured to use blob storage for everything (I think). I can confirm that images uploaded to Umbraco have ended up on blob storage and in the cache container, as I expected. On build, they just don't appear on the site until a restart. As a backup for now, I have moved them from blob storage back into the actual file system Media folder until I can figure out this issue though. The following are my configs and how I access the images.

cache.config

<?xml version="1.0" encoding="utf-8"?>
<caching currentCache="AzureBlobCache">
<caches>
    <cache name="AzureBlobCache" type="ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache, ImageProcessor.Web.Plugins.AzureBlobCache" maxDays="365" browserMaxDays="7" folderDepth="6" trimCache="true" memoryMaxMinutes="1">
        <settings>
            <setting key="CachedStorageAccount" value="DefaultEndpointsProtocol=https;AccountName=[name];AccountKey=[key];EndpointSuffix=core.windows.net" />
            <setting key="CachedBlobContainer" value="[blob-container-name]-cache" />
            <setting key="UseCachedContainerInUrl" value="true" />
            <setting key="CachedCDNRoot" value="https://[name].blob.core.windows.net" />
            <setting key="CachedCDNTimeout" value="1000" />
            <setting key="SourceStorageAccount" value="DefaultEndpointsProtocol=https;AccountName=[name];AccountKey=[key];EndpointSuffix=core.windows.net" />
            <setting key="SourceBlobContainer" value="[blob-container-name]-media" />
            <setting key="StreamCachedImage" value="true" />
        </settings>
    </cache>
</caches>

security.config

<?xml version="1.0" encoding="utf-8"?>
<security>
<services>
    <service prefix="media/" name="CloudImageService" type="ImageProcessor.Web.Services.CloudImageService, ImageProcessor.Web">
        <settings>
            <setting key="Container" value="[blob-container-name]-media" />
            <setting key="MaxBytes" value="8194304" />
            <setting key="Timeout" value="30000" />
            <setting key="Host" value="https://[name].blob.core.windows.net" />
        </settings>
    </service>
    <service name="AzureImageService" prefix="media/" type="ImageProcessor.Web.Plugins.AzureBlobCache.AzureImageService, ImageProcessor.Web.Plugins.AzureBlobCache">
        <settings>
            <setting key="StorageAccount" value="DefaultEndpointsProtocol=https;AccountName=[name];AccountKey=[key];EndpointSuffix=core.windows.net" />
            <setting key="Container" value="[blob-container-name]-media" />
            <setting key="AccessType" value="Blob" />
        </settings>
    </service>
</services>

On the site I access images uploaded to umbraco using the MediaItem.Url() function. Some are lazy loaded, some are not, but they all end up with the same code.

<img data-src="@blockItemContent.Image.MediaItem.Url()" alt="image" class="lazyload" />

Some images used to have this wrapper

@Url.GetCropUrl(blockItemContent.Image.MediaItem)

but I unified them all to the first version when this didn't seem to make a difference.

If I am exclusively using azure blob storage, do I need both, CloudImageService AND AzureImageService, only one of them, or is anything else missing from there?

Lastly, (and least) Do I need the "EndpointSuffix" attribute in any of the StorageAccount settings?

is working on a reply...