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.
Is it possible to use the parameter --skip-register-on-import with multiple registers, either by using a comma-separated string or by specifying this parameter multiple times in parameters.txt?
Thi...
