Hi @Kuki. Thanks for the pointer - that fixed it I already had my client configured (I have a virtual machine just for that and I hadn't changed it, so thought it was OK). But the issue was the "/ffp/crashplan/conf/my.service.xml" file needed amending again. Thanks very much for the helpKuki wrote:@nasingtom:
Have you done the adjustments desrcibed in post #1 under "=== Configuration ==="?! This was my problem after a reinstall because I forgot it, due to the missing numeration as a necessary installation step.
Once I did that and connected from my client VM, I was able to connect and adopt the NAS account within crashplan; and everything is working great (woohoo)
All I need to do now is carry out the same process on my other NAS (I backup to 2 NAS boxes) to make that one work as well.
Really keeping my fingers crossed that someone works out how to disable the automatic update process before the next update is available.
Thanks to everyone for their help in resolving this, and for your continued support of this great product - You are all stars....