Internal server error when trying to upload images

[patrick-alpcot]

Hi!

I am unable to upload images via the CMS anymore. I get these errors in the console when trying to upload an image:

The last successful image upload was in July.

I have tried different image formats and file sizes, so it doesn't seem to be any of the "usual" image upload issues.

Just so you know, no one in our current team have worked on this CMS, so we are a little lost as to how everything has been setup. Hoping you can point us in the right direction, so we can fix this.

Thanks in advance,

Patrick

---

Cofoundry version: 0.12.0.0
Auto updates: On
Server: Azure
Dotnet version: dotnet 8

[HeyJoel]

My first thought would be what changed in July?

In addition you'll need to find out what the exception is, to do that you'll first need to know how errors are being logged. Cofoundry has a basic error logging plugin, but it might also have been set up with other standard .NET logging providers instead.

Lastly, it's worth knowing what Cofoundry imaging plugin is being used and what version.

[patrick-alpcot]

Thanks for the speedy reply, Joel!

It looks like there is no logging set up (in Azure at least). I'll try to get someone to look into this properly, and I'll get back to you.

Regarding the imaging plugin. This is what I found:
<PackageReference Include="Cofoundry.Plugins.Imaging.SkiaSharp" Version="0.6.0" />
<PackageReference Include="SkiaSharp.NativeAssets.Linux.NoDependencies" Version="2.80.2" />

It was version 0.5.0 before. This change and an upgrade dotnet 8 seems to have been made between July and now, so the culprit probably lies somewhere within these changes :)

If anything looks funky with the imaging plugin please let us know, otherwise I can try to get someone to see if they find some logs, or at least setup some logging.

[HeyJoel]

It's been a while since I looked at skiasharp in linux but SkiaSharp.NativeAssets.Linux.NoDependencies package wasn't something I recognised. Docs state that it's only required for certain distros so may not be a problem, and if you're able to resize images fine then it probably isn't the issue, but something to note.

Anyway, let's start with the exception message/stack and work from there.

[patrick-alpcot]

Okay, great. Thanks again.