Umbraco.Cloud.Issues
Umbraco.Cloud.Issues copied to clipboard
umbraco
ImageProcessor exception
Issue description
Since our project deployed live in cloud, the below error is logged multiple times a day on different image url. The website is UP and running normally. Umbraco version - 8.11.2 Error: ImageProcessor exception: ProcessImageAsync 559 : The request /image/xxx.jpeg?fh=640&fw=640 could not be understood by the server due to malformed syntax.
No such errors are logged in the cloud dev environment.
I notice that the imagefolderid path is missing in the url tagged in the error message. for ex. c2fbg3kx is missing in the url - /media/c2fbg3kx/xxx.jpg
The images appears in the webpage correctly.
@Ramya-Devendiran Did you find a solution to this issue? Several of our clients experience the same issue on latest version of Umbraco 8. We also receive issues on the form "ImageProcessor.Common.Exceptions.ImageProcessingException: ProcessImageAsync 610 : No image exists at D:\home\site\wwwroot\media\1234\name-of-image.jpg". There is no image with that name in the folder 1234 but in 1235 there is. Does it have anything to do with the legacy media picker field?
@Ramya-Devendiran we have the same problem. Did you find a solution for this?
Which version of https://www.nuget.org/packages/Umbraco.Cloud.StorageProviders.AzureBlob are you using?
Hey @RyuLindow, we're not using that package. Our website is self-hosted on azure.
Ah, in that case, I'm not sure if this thread is relevant for you as projects on Umbraco Cloud our own blob storage package and this is the GH tracker for Umbraco Cloud.
You might want to look into upgrading your Umbraco/imageprocessor version and see if that helps. I would also advise looking on https://our.umbraco.com/forum/ or the CMS tracker :)
Which version of https://www.nuget.org/packages/Umbraco.Cloud.StorageProviders.AzureBlob are you using?
We are not using blob storage. We use the default PhysicalFileSystem storage.
@Ramya-Devendiran It's recommended that you have your media in blob storage on Cloud rather than in the physical file storage.
Reason are:
- Better performance with blob storage
- Physical storage limits as per: https://our.umbraco.com/Documentation/Umbraco-Cloud/Getting-Started/Umbraco-cloud-plans/#hard-quotas-for-shared-umbraco-cloud-plans
If you reach out to support, we can help you migrate your media to our blob storage, as part of your UC subscription :)
We're using the default PhysicalFileSystem as well. @Ramya-Devendiran did you try storing the media in blob storage and did it solve the problem?
Howdy there 🤠
Looks like a lot of water has flowed under the bridge since the last update on this issue.
From what I can tell, this issue is not related to Umbraco Cloud. My recommendation is to open a new issue on the CMS issue tracker.
Sorry for the long wait and any inconvenience this might have caused.
Kind regards, @mclausen, Cloud Platform/Core Team Lead
