Wildcat76

IT WORKED! I deleted the /mnt/user/appdata/CrashPlanPRO directory and restarted the container and all is well. I'm starting a new backup from scratch just to be sure. Thanks for your help, DJoss! 🙌

By "Remove", do you mean remove that text from the Config Directory line in the container settings, or do you mean entirely delete that directory from the file system?

Circling back around on this. Any ideas as to what may be causing my issue? Thanks again for your help.

Yes, I believe so. Screencap of settings attached.

CrashPlanPRO cannot connect to its background service. I'm at my wit's end. I've had this issue for 5 months and I haven't been able to configure my client in that time. I finally have had a couple of days where I could deep dive on it but I'm coming up empty. Full disclosure: I'm no Linux/UNRAID/CL master by a long shot. What I haven't been able to do is restart the "engine", even after several uninstall/reinstall cycles. At least, I don't think I've been able to. My command line skills are a 2 out of 10, at best, but I was finally able to at least get to the engine logs. I've attached the error log. Does anybody have any ideas as to what's going on? I really want to get this back up and running. engine_error.log