Speckle Server 2.26.3 startup error: unsupported CPU (Ubuntu 24.04)

[RafaelMayer]

Hey everyone, how’s it going?

I’m trying to upgrade my Speckle Server to version 2.26.3, but I’m running into an error as soon as the service starts.

Here’s the error log:

{"@l":"Error","err":{"type":"Error","message":"Could not load the \"sharp\" module using the linux-x64 runtime\nUnsupported CPU: Prebuilt binaries for linux-x64 require v2 microarchitecture\nPossible solutions:\n- Ensure optional dependencies can be installed:\n    npm install --include=optional sharp\n- Ensure your package manager supports multi-platform installation:\n    See https://sharp.pixelplumbing.com/install#cross-platform\n- Add platform-specific dependencies:\n    npm install --os=linux --cpu=x64 sharp\n- Consult the installation documentation:\n    See https://sharp.pixelplumbing.com/install",

Has anyone else encountered this issue?
I’m currently using version 2.23.11, and I noticed the error starts appearing from 2.25.8 onwards.
Upgrades up to 2.25.7 work fine without any issues.

Here’s the output of lsb_release -a, in case it helps:

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.3 LTS
Release:        24.04
Codename:       noble

Output of uname -m:

x86_64

[RafaelMayer]

I found what was causing the issue in my case.

It’s probably not something that will happen to everyone, but here’s a tip.

This problem occurred because this instance was running inside a VM on Proxmox, and I had configured that VM not to have full access to the host’s CPU.
Once I changed that setting in Proxmox, everything was fixed.

To verify it, I ran the following command:

lscpu | grep "Model name"

and got this output:

Common KVM processor

which confirmed what I suspected.

Error messages like the ones below can be related to this CPU limitation:

• “Unsupported CPU: Prebuilt binaries for linux-x64 require v2 microarchitecture”
• “Operation is not supported on this platform”

After fixing the CPU configuration in Proxmox, the command output became:

AMD Ryzen 5 1600 Six-Core Processor

and the problem went away.