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,
Server – tried both Windows Server 2022 and Linux
Version - 2025-08-11 and 2026-05-25
We were testing a new version (2025-08-11) with a Halcust that we had migrated from the existing ...
Hi,
years ago we used to have the email and conference module. Did not need it so we dropped it.
We hav recently implemented global users, which are all named users and therefor seem to need a m...
