Michael_P

Yes, the only way to get it to service start is to remove it, delete the CrashPlanPRO folder in appdata then re-install. Then, if the container is stopped and re-started it gets stuck in the loop again.

Here's the logs Service Logs.zip

Hello! I've gone and mucked something up and I hope you can help. I originally had a WHS 2011 box backed up with CrashPlan Home, I've since built a new server using Unraid and migrated to CrashPlan Pro via the docker app and adopted the WHS 2011 backup successfully. It was working fine for a month, no troubles. However, in building my VM to host the WHS 2011 server so my windows clients can continue to backup to it, I had to move some of the vdisks around to better make use of my cache drive. To do that, I needed to bring down the array and thus the dockers - I moved the vdisks successfully and re-started the array, however the CrashPlan docker container did not come back up. I monkeyed with it a bit, and decided it was best to just delete the container and re-install. This worked and the webgui came to life and asked for my user id and password, then mentioned that it was a new device (because I deleted the files in the appdirectory) and if I'd like to replace a device, which I did. However, after skipping the file transfer portion of the process it begins to transfer settings at which point it asks for the user credentials again - that part fails with the message "Unable to sign in. Unknown error." If I try to restart the container, the service will no longer start and just sits in a crashplan service starting loop (according to the log). I do notice that Cod42 has mentioned changes on their website, so it may be on their end and I'm chasing my tail, but any help is appreciated!