This happend with one of the automatic Cloud Nodes updates in April and yes, correct way to fix it is to copy the executable from oldver folder into cloudnode folder and rename it according to the content of run-cloudnode.sh script.
Hi there,
We are looking at a new version for our customers – version 2025-09-08. We have setup a test server and then login to this from a client machine, these are Windows 11 client machines.
...
