I'm still struggling with this one...I have tried the configuration changes suggested to try and connect to the engine on unRaid. I also us the Crashplan Desktop Docker image and everything seems to indicate that the engine on unRaid is hung trying to upgrade from 4.2 to 4.3. So, if I try to connect remotely with the configuration changes suggested, I get the splash screen that says 4.3 (I'm assuming because the Windows instance updated successfully) and that is as far as it gets, it just hangs there and I have to kill it in the task manager. If I try going through RDP to the Crashplan Desktop Docker, it then shows 4.2. As mentioned earlier and it hangs the same way as trying to connect remotely. I did end up renewing the Docker image and was able to get it to start fresh and saw a message in the Crashplan window when I was trying to login that it was busy upgrading and that was when it locked up and starting showing this same behavior. So, at this point, I'm left thinking that the Crashplan engine in the Docker image isn't completing the upgrade for some reason. Any suggestions on where to go from here? Thanx!
I've got the exact same issue. I've gotten it to work a few times but the service keeps terminating itself and it won't start back up. Not sure what to do from here, everything was working fine for the longest time.
[CONTAINER] CrashPlan & CrashPlan-Desktop
in Docker Containers
Posted
I've got the exact same issue. I've gotten it to work a few times but the service keeps terminating itself and it won't start back up. Not sure what to do from here, everything was working fine for the longest time.