Leifgg

The CrashPlan Desktop container is currently not working, it needs to be updated to version 4.4.1 since it doesn’t update itself as CrashPlan container does. The Windows client is your option at this moment.

It’s probably not as easy as updating the app in the container, the folder mappings inside the container is also likely needed to be updated as well.

Check that the changes in my.service.xml on the server is done. If they are ok leave the CrashPlan Docker running and don’t update it! It must have been able to auto updated 4.4.1 to work. You can check the logs on the server. Check that ui.properties on your PC is ok. Copy the .identity file and the .ui_info file to your PC and change .ui_info file. Reboot your PC and try again...

NTFS is supported, is it mounted? My plan is to do a guide about it in CrashPlan doc as soooon I get some time.

Nothing to do until the maintainer of the Desktop Docker is able to update it latest version and do any changes needed to get it working again.

That’s because the CrashPlan Docker has auto updated itself to 4.4.1 and the CrashPlan Docker Desktop doesn’t.

Since CrashPlan 4.4.1 is now publicly available at their home page I have made an update to the Setup Guide (v1.1) that is linked in my signature. The changes made are only related to the Windows client and how the .ui_info and the .identity files are managed as mentioned in previous posts. But there are still some problems! As long as your CrashPlan Docker is running you will be able to connect with the Windows Client and it will survive a reboot of the PC as well but the .ui_info and the .identity files gets updated as soon as the CrashPlan Docker is restarted making it impossible for the Windows Client to connect again until you manually copy and modify the files. If anybody have some brilliant ideas on how to fix that pls let us know....

Thanks for your feedback guys! The guide will be updated with the latest changes when time permits. My intention is also to include info on how to backup to/from other sources like a USB disk and another unRAID server.

I have been in contact with CrashPlan and they say that 4.4.0 for Windows 64 bit will be available within a week or two.

Updated the both ui_info and ui.properties and still having issues connecting Here's some logs from the docker Crashplan: Thanks for this! Have you been able to find a direct download link for Windows 64 bit version as well?

I have submitted a ticket to CrashPlan support asking for a download link to the Windows version 4.4.0 but no reply yet…

Testing the update right now. Have you been able to find 4.4.0 for download?

CrashPlan has released version 4.4.0 and the CrashPlan Docker will be automatically updated. http://support.code42.com/Release_Notes/CrashPlan_For_Home/4.4.0 It looks like this release is incompatible with version 4.3.0 since the CrashPlan Desktop Docker no longer can connect to the backup engine. It seems be the same for the Windows client. I haven’t been able to locate version 4.4.0 for download on CrashPlan yet. Has anybody else found it?

Dockers should not be affected by the changes from 6.0 to 6.1, only some plugins. Just updated from 6.0.1 to 6.1.2... forced me into an update of crashplan 4.3 from 4.2. Great work here! Thanks. I have the advanced extra paramater in both crashplan and desktop dockers... is this correct? It appears to be working. The extra parameter "--volumes-from CrashPlan" is only needed in the CrashPlan Desktop Docker.

You are almost there….! The folder you are looking for is unRaid. That folder is mapped to your folder Q located in the share called Other. So just browse for the unRaid folder in the MakeMKV file dialogue.

yes, if I can watch the splash screen not progress, then I have logged in. Yes version 4.3.0. Yes that splash screen just sits there indefinately. I don't see the "can't connect to engine" message. I am running out of ideas… You could check the available space for the Docker.img so that you not are running out of space (Settings, Dockers) just to be on the safe side. Have you tried to uninstall the CrashPlan Desktop Docker (including its image) and reinstall it again?

Not that much that could/should go wrong with the CrashPlan Desktop Docker. Assume you able to connect with Remote Desktop and login with the username ubuntu. After that you should see the CrashPlan splash screen. It should display version 4.3.0 in the lower left corner. Is this where you get stuck? Also check your CrashPlan Desktop Docker settings. Should be as the pic on page 5 in the tutorial located in my signature.

Haven’t done this move myself but here are some thoughts… Regarding permission I believe that it should be Owner ID 99 and Group ID 100 however I believe that this is taken care of when you install this Docker (at least for me). Also suggest checking you Docker mapping so that Plex can see your folders and the Plex is setup to match that.

It does. Look in advance settings and set the Variable Name PLEXPASS to 1 in the section Environment Variables. Edit: See update in post below.

You can try with Settings, Display settings, Show banner: Yes and at Custom banner select your banner. Doesn’t work for me on 6.1-rc6 but you can always go to the folder /boot/config/plugins/dynamix and put your banner there.

If the CrashPlan Desktop Docker is unable to connect something must have happened with the CrashPlan Docker. I assume it is running, can something changed your config folder, where is the config folder stored, if it is on the cache drive can it have been moved/changed? You might have a look on the Guide in my signature to see if that can help. The CrashPlan Docker was running. I didn't change anything in my config folder. The config is stored on the cache drive. Nothing was moved/changed. Is it recommended to stop the Dockers before stopping the array? That is the only thing I can think of that may have corrupted something. I just removed both CrashPlan dockers, disabled Docker in my settings, deleted the docker.img file from my cache disk, re-enabled Docker in settings, Re-added both CrashPlan Docker containers. Now the CrashPlan GUI is working again through Remote Desktop. Thanks! Strange! Usually I try to stop my Dockers when re-booting but normally I forget to do that and haven’t had any problems so far and I think I have used it for about 6 months. However CrashPlan do a lot of logging in the config/log folder but I would be surprised if the app wasn’t able to manage that in case of an unexpected shutdown.

If the CrashPlan Desktop Docker is unable to connect something must have happened with the CrashPlan Docker. I assume it is running, can something changed your config folder, where is the config folder stored, if it is on the cache drive can it have been moved/changed? You might have a look on the Guide in my signature to see if that can help.

I don't have another pc, but I just installed the Microsoft remote desktop app on my Android phone and tried it from there. Same results. Thanks, Mark Two more things before I give up on this… You could try to install the Libre-Mate Docker just to see if you can connect to that one. It’s basically the same Ubuntu desktop that has been used for CrashPlan Desktop. If you have the Community Applications plugin search for it there and add it. Set the mappings to something like this: /home/ubuntu/.config -> /mnt/cache/Apps/Ubuntu/Config/ and /home/ubuntu/unraid -> /mnt/user/ Make sure CrashPlan Desktop is stopped and that nothing else running is using port 3389. If you can connect to this with Remote Desktop then there is something wrong with the CrashPlan Desktop. If not you might try using another Remote Desktop app on your PC, (mRemoteNG works for me).

Ok, thanks for that, this makes sense now, but that brings me back to the problem that I'm no longer able to connect to Crashplan Desktop. It was working fine, but then stopped. I didn't change anything, but I did reboot the server. I don't have it set to auto-start, so I started it manually. Here is all that shows up in the log: The log looks about the same on my system so that is probably ok. Did a reboot on my system and have no problem starting the CrashPlan Desktop Docker again and login with remote desktop. Is your Desktop Docker running so it’s only the remote desktop login that fails? Running out of ideas right now… Yes, that's correct, remote desktop doesn't connect. I've tried restarting the desktop docker, but of course that's not helping. One thing that was happening before it stopped connecting is that it would usually take a couple of login attempts before it would work. I'd usually get an error message with the first, and sometimes the second attempt. Sorry I didn't note what the error message was (it wasn't that the password was incorrect though), but anyway now I'm not even getting the login screen. I should also mention that, although this problem started before upgrading, I did just upgrade to Windows 10. I'm really confused here. The upside is that from logging in to the Crashplan website, it appears that it is still making progress with the backup, so I guess that's good, but I wish I could still get to the desktop gui. Don't know what I'll do if I need to change anything or add new directories to be backed up. Appreciate your efforts anyway. Thanks, Mark I normally use Windows 8.1 but just tested from a Windows 10 home PC and I am able to connect from both. Do you have another PC you could try with? Maybe the problems isn’t really related to the Desktop Docker itself, more like something with your PC or network?

Ok, thanks for that, this makes sense now, but that brings me back to the problem that I'm no longer able to connect to Crashplan Desktop. It was working fine, but then stopped. I didn't change anything, but I did reboot the server. I don't have it set to auto-start, so I started it manually. Here is all that shows up in the log: The log looks about the same on my system so that is probably ok. Did a reboot on my system and have no problem starting the CrashPlan Desktop Docker again and login with remote desktop. Is your Desktop Docker running so it’s only the remote desktop login that fails? Running out of ideas right now…