Need basic help with installation - need more details

[bgmess]

I am fairly new to Linux and Docker. I need more instructions that those given in the quick start:

Launch the CrashPlan PRO docker container with the following command:

docker run -d
--name=crashplan-pro
-p 5800:5800
-p 5900:5900
-v /docker/appdata/crashplan-pro:/config:rw
-v $HOME:/storage:ro
jlesage/crashplan-pro

Where do I enter the above commands?

Is this all I need to do?

Any tips would be greatly appreciated. Not sure how to begin. I have installed Docker on the Synology NAS, but that's as far as I got.

Thanks, Brian

[excalibr18]

Hello Brian, I'm a Synology user as well and was using Patters' CrashPlan package before migrating to the Docker image. Since you're new to Linux, I'll assume you haven't used an SSH client like PuTTY. You'll need to download that before you get started. You can get it here: http://www.putty.org/

Here's how I got jlesage's crashplan pro docker image up and running on my Synology and adopted my existing backup set created from when I was using Patter's CrashPlan package (EDIT: This reflects my personal setup [I have a Synology DS1515+ running DSM 6.1.5 and Docker package version 17.05.0-0367; I have a single volume and it's set up with Synology's SHR-2 RAID configuration] and is intended to be a step-by-step example of how I deployed the docker image on my system. Your individual Synology setup may differ from mine, so please understand that your deployment of the docker image may differ as a result.):

From Synology DSM:

1. Open Package Center.
2. Stop Patter's CrashPlan package if you are migrating from it.
3. Install the Docker package from the Package Center interface (this you already did).
4. Close Package Center.
5. Open Docker.
6. Click 'Registry' on the list to the left (below 'DSM').
7. In the search bar at the top of the Docker window, enter jlesage and click the 'Search' button. You should see jlesage/crashplan-pro at the top of the list. Highlight it and click the 'Download' button. Leave the tag as latest in the 'Choose Tag' window that pops up and click the 'Select' button.
8. You should now see a '1' pop up to the right of 'Image' below 'Registry'. Let your Synology complete the download (it's a 499 MB download).
9. Once the download is complete, open Control Panel from the DSM interface.
10. Click on 'Terminal & SNMP' from Control Panel.
11. Click the box next to 'Enable SSH service'.
12. Open PuTTY.

From PuTTY:

1. In the 'PuTTY Configuration' window, enter the local IP address (192.168.xxx.xxx) for your Synology where it says 'Host Name (or IP address)'. Then click the 'Open' button, which will open up a Terminal Session.
2. Enter the username and password at the prompt for a user with Admin privileges.
3. Enter the following command to get 'root' access: sudo -i Press Enter. Enter your password again and press Enter.
4. Quick note about PuTTY: if you highlight the code blocks on this site and copy with Ctrl+C, you'll paste in PuTTY with the Right-Click Mouse Button instead of Ctrl+V.
5. You will need to create the /docker/appdata/crashplan-pro configuration folder manually by entering the following command: mkdir -p /volume1/docker/appdata/crashplan-pro Press Enter.
6. Create the Docker container image by entering the following command at a minimum (there are other environment variables you can introduce if you see fit or necessary - just check jlesage's documentation on those specifics) as a single continuous string (no line break) and let it do its thing: docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro The reason we are doing this through SSH/PuTTY is because the Synology Docker program won't let you map Volume1.
7. At this point your Docker container has been created. You can now close your PuTTY session window.

From Synology DSM:

1. Uncheck the box next to 'Enable SSH service' in the 'Terminal & SNMP' window in the Synology DSM interface.
2. Open Docker.
3. Click 'Container' from the list on the left. You should now see a 'crashplan-pro' entry with it showing as 'Running'.

From your Web Browser:

1. Log into the CrashPlan PRO container GUI by pointing your browser to your IP address of the synology at port 5800 (http:\\192.168.XXX.XXX:5800)
2. Sign into your CrashPlan account through the web GUI you just accessed.
3. The following assumes you were using Patters' CrashPlan Package initially and you need to 'adopt' the backup.
4. Click the 'Replace Existing' button to start the wizard.
5. Skip 'Step 2 - File Transfer'.
6. Once done with the wizard, go to your 'Device Details' and click 'Manage Files'. Since we mapped the Synology's 'Volume1' to the Docker Container's 'Volume1', the Docker CrashPlan-Pro Container should automatically see and recognize the files/folders previously backed up by Patters' CrashPlan Package (assuming you were using it).
7. Perform a backup and the system will make sure it is the same by scanning all the files and making sure everything matches. If done correctly you shouldn't need to re-upload everything to CrashPlan's servers.
8. You can close the browser window and you’re done! As long as the Docker Container is up and running, you’ll be backing up to CrashPlan. Any changes to your backup set like adding new folders to your backup will be done through the web GUI.

I hope this helps you get up and running!

[jlesage]

You can also look at Synology's documentation: https://www.synology.com/en-global/knowledgebase/DSM/help/Docker/docker_container

[beagleboy1010]

Thank you for the step by step instructions. I am a new to docker too. Everything installed and all working fine :) cheers

But I have a problem when I do a restore to the original folder, nothing restored? is this something to do with folder structures? Please help?

many thanks

[excalibr18]

I haven't yet had to restore from within the Docker Container, but I'm fairly certain the reason the restore doesn't work is because Volume1 is being mapped as Read Only: -v /volume1/:/volume1:ro

If you change the -v /volume1/:/volume1:ro portion of the docker run command to -v /volume1/:/volume1:rw then it should allow the restores.

@jlesage: is that correct? would the user need to remove the docker container and re-create it with the read/write tag?

[jlesage]

Yes that's correct @excalibr18. Re-creating the container with the R/W permission for the volume would allow the restore to work properly.

[beagleboy1010]

Perfect! Thanks guys All working properly now

[Slartybart]

Is there a way to map other external drives, as most of my Crashplan files are on drives other than the Volume 1 internal disks? Thank in advance for any help

[jedinite13]

I am having problems connecting with the web service. After running the command and going to the webpage I get Code42 cannot connect to its background service. Retry

If I create the container via the UI it works but I can't create the storage volume to map to /volume1 where all my data is contain in different shares. Any guidance would be appreciated.

Also, as a note, I used the default instructions and it's moved all my files on CrashPlan to Deleted. so be careful when setting $HOME:/storage as your location if you already have a backup set. I am not sure if I am going to have to just upload everything again 2.1TB or if it will de-dup and mark the files as not deleted.

[jlesage]

@Slartybart, yes it's possible. You just need to map additional folders to the container (using the -v argument).

[jlesage]

@jedinite13, did you follow instructions indicated at https://github.com/jlesage/docker-crashplan-pro#taking-over-existing-backup? Basically, if path to your files (as seen by the container) is different between your old and new installation, you need to re-select your files using the new paths. Old paths would be marked as "missing", but that's not a problem. Once you perform the backup, nothing will be re-uploaded because of deduplication.

[excalibr18]

@Slartybart The Synology maps USB external drives as volumeUSB# where # corresponds to a separate physical USB external drive. If you only have one USB external drive connected, then it'll be mapped as volumeUSB1 by default.

If you're looking to mount the entire USB external drive (in a similar way as Volume1 internal disks are mapped), then you can use -v /volumeUSB1/usbshare/:/usbshare:ro when setting up the container.

[excalibr18]

@jedinite13 The Synology UI won't allow you to map Volume1, which is why you need to do it via the command line.

As for not being able to connect to the background service, try doing this:

1. Remove the crashplan-pro docker container. You can do this from the Docker GUI interface on the Synology.
2. Delete all the contents of /docker/appdata/crashplan-pro/ (including all the sub folders). You can do this from Synology's FileStation if you're logged in with an admin-level account, otherwise you'll need to do it from the command line logged in as root. Make sure you don't actually remove the crashplan-pro/ folder. If you did you'll need to re-create it.
3. Create the Docker image again starting from step 6 under "From PuTTY".

That has seemed to worked for other users (see https://github.com/jlesage/docker-crashplan-pro/issues/14)

[excalibr18]

One other thing to be aware of: if on the Synology you are experiencing the iNotify Max Watch Limit issue, please refer to this solution: https://github.com/jlesage/docker-crashplan-pro/issues/23

Also be aware that you'll have to repeat setting the max watch limit in /etc.defaults/sysctl.conf each time the DSM downloads and applies an update.

[aagrawala]

@excalibr18 & @jlesage Totally AWESOME, folks! Thank you so much! Just followed the instructions instead of fussing with the client app on my MAC.

I have the following questions... Kind of dumb ones I think ;-)

1. We don't need the MAC or local client anymore, correct?

2. Can we delete the java JRE packages from the 'public' folder that we used to download per Patter's procedure?

3. Can we uninstall the CrashPlan Home (Green) package from Synology DSM?

4. With this Docker Package solution, looks like we don't need to install the CrashPlan Pro package from the Package Center in Synology DSM, correct?

Once again, thank you! Anil

[excalibr18]

1. We don't need the MAC or local client anymore, correct?

Correct. I had the local client installed on my Win10 machine and after going with jlesage's docker solution, I no longer need to use that machine. I just need any machine on my local network with a web browser to access the docker container's web GUI.

2. Can we delete the java JRE packages from the 'public' folder that we used to download per Patter's procedure?

I would assume this is correct, however when used Patter's package I always opted to use the system Java, not Patter's internal one.

3. Can we uninstall the CrashPlan Home (Green) package from Synology DSM?

Assuming you upgraded you CrashPlan subscription to the Pro/Small Business plan, and jlesage's docker solution is confirmed to be working for you (i.e. you have adopted your backup set and it is working correctly), then I don't see a need to keep the CrashPlan Home (Green) package.

4. With this Docker Package solution, looks like we don't need to install the CrashPlan Pro package from the Package Center in Synology DSM, correct?

Correct. With this Docker solution, you don't need the packages from Patter's.

[aagrawala]

@excalibr18 Thanks for responding so quickly to my questions.

Another Question: My migration worked fine per the above instructions and the backup is running now looking at the web GUI. However, I cannot seem to browse the files and/or folders that have been backed up using "Manage Files". I can see that volume1 is listed, but browsing under it can't seem to find my file structure that's set up for backup. Any tips?

Thank you in advance! Anil

[excalibr18]

To make sure I understand you correctly, are you saying that when you click "Manage Files" in the GUI, there's nothing listed under volume1? Or are there folders listed, but you just can't find the folders you are backing up?

Did you map volume1 using -v /volume1/:/volume1:ro or -v /volume1/:/storage:ro

[aagrawala]

Folders listed but can't find my folder structure from my Synology Home directory that I have selected to be backed up. See the attached snapshot showing what's under volume1

[excalibr18]

What were the folder paths for your backup when you were using Patters' package?

If you scroll down in that window, do you see any folders with a check mark next to it?

[aagrawala]

Something like this as shown in the attached from the old client app on my computer saved a few years ago

[aagrawala]

Web GUI shows that the backup is running and the files that are new and hadn't been backed up for the last 25 days (yes, I hadn't done this upgrade for so long after the backup had stopped) are being backed up (can't see the files that are being backed up themselves... Just from the size of the backup remaining

[excalibr18]

OK this helps. In this case using the screenshot from the old client app, when you scroll down in the "Manage Files" window you should see a "photo" folder in the list. If you click on that "photo" folder, then you should see the various Year folders you had selected in the old client to back up. Each of the Year folders should have a check mark next to it.

For example, I selected my entire "Archives" and "Documents" shared folders that reside in Volume1. When I scroll down in "Manage Files" this is what it looks like:

[aagrawala]

Ah, LoL, I didn't notice the scroll bar to the right side in the GUI and thought those were the only folders what I sent you :-) I do see all the other folders when I scroll down.

Thanks a million for your help. And, sorry for bugging you for this silly thing and taking up your time.

Best, Anil

[excalibr18]

No worries. Glad it's all sorted out and working for you! The new GUI for CrashPlan Version 6 is less intuitive than the one before it unfortunately.

[lenny81]

Thanks for the installation steps. I've just transitioned to the docker from Patter's solution. Everything went well and the container is running CP pro, however I can't access the web gui. I've followed this step: "Log into the CrashPlan PRO container GUI by pointing your browser to your IP address of the synology at port 5800 (http://192.168.XXX.XXX:5800)" and replacing the XXX.XXX with my synology server address. I get a 'Can't connect to a server' message. Am I missing something obvious?

Any suggestions would be appreciated.

[jlesage]

Which parameters did you give to the docker run command? Did you mapped the port (-p 5800:5800)?

[excalibr18]

@lenny81: Are you accessing the web GUI of the Docker on the same LOCAL network as the Synology?

[lenny81]

I'm trying to access it on the same network as the synology.

jlesage: No idea. I'm pretty clueless with all this. I can't remember which guide I used to set it up or how I check if I mapped the port... how do I check this?

[jlesage]

Using the Synology UI, you can access the container's advanced settings and then there is a "Port Settings" tab where you can see the port mappings.

[lenny81]

Thanks for the reply. Under details -> Port settings I can see port settings for ports 4243 and 4242 but not 5800 which I guess it means it’s not mapped. Is there a way I can map them now or will I need to reload the container?

On 9 Feb 2018, at 9:32 pm, Jocelyn Le Sage <[email protected] mailto:[email protected]> wrote:

Using the Synology UI, you can access the container's advanced settings and then there is a "Port Settings" tab where you can see the port mappings.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-364409923, or mute the thread https://github.com/notifications/unsubscribe-auth/AildC-2TlUvRZywfuJwc2ebUqHoBulw2ks5tTCyygaJpZM4RRA40.

[excalibr18]

You can either delete and re-create the container with the correct port mapping from the command line; or stop the container from within the Synology Docker GUI, click the Edit button, go to Port Settings, and change the port to be 5800.

[lenny81]

Thanks for the help jlesage and excalibr18, I ended up deleting and reinstalling the container using your guide above excalibr18 and it's all working fine now.

[halteach]

@excalibr18 Excellent job! Up and running in less than 30 minutes (It took this long because I didn't follow your instructions in the order they were written!)

Thanks

Hal refugee from Patters CrashPlan packages for Synology NAS""

[kmstrs]

@excalibr18 From the command line I got this: "Error starting userland proxy: listen tcp 0.0.0.0:5000: bind: address already in use." It starts if I use 6000:6800, but then I can't connect to the web UI using port 6800 I tried changing the port to 5000:5800 from the gui, and then I'm getting "Local port 5000 conflicts with other ports used by other services". I have no other Docker containers running. "netstat -pna" shows "tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 10090/nginx: worker" Anyone else see this?

EDIT: Seems that the DSM web interface itself was using 5000:5001. I changed it in Control Panel->Network->DSM Settings to 4000:4001 and then the Crashplan Pro Web interface worked.

[jlesage]

When you add a port mapping, the first port is the one on the host side and the second one if the one on the container side. Container side should always be the same (5800). So you could set something like XXXX:5800, where XXXX is any port not already in use on the host.

[bigtfromaz]

Port 5000 is the default port used by the Synology administrative web site.

Tom Hebert 480-788-6601

From my phone, so this message may be more terse than normal

---

From: kmstrs [email protected] Sent: Wednesday, February 21, 2018 9:30:24 PM To: jlesage/docker-crashplan-pro Cc: Subscribed Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

@excalibr18https://github.com/excalibr18 From the command line I got this: "Error starting userland proxy: listen tcp 0.0.0.0:5000: bind: address already in use." It starts if I use 6000:6800, but then I can't connect to the web UI using port 6800 I tried changing the port to 5000:5800 from the gui, and then I'm getting "Local port 5000 conflicts with other ports used by other services". I have no other Docker containers running. "netstat -an" just shows tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN

Anyone else see this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-367564249, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRoLxGwFLGxC9PFZ2dVLNcYUsxEFDks5tXO1ggaJpZM4RRA40.

[bgmess]

When following the directions, I get an error after executing:

docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

I get the error:

:~$ docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2fvar%2frun%2fdocker.sock/v1.29/containers/create?name=crashplan-pro: http://%2Fvar%2Frun%2Fdocker.sock/v1.29/containers/create?name=crashplan-pro: dial unix /var/run/docker.sock: connect: permission denied.

See 'docker run --help'.

What do I need to do to give it permission?

Thanks,

Brian

From: excalibr18 [mailto:[email protected]] Sent: Tuesday, January 2, 2018 3:12 PM To: jlesage/docker-crashplan-pro [email protected] Cc: bgmess [email protected]; Author [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

Hello Brian, I'm a Synology user as well and was using Patters' CrashPlan package before migrating to the Docker image. Since you're new to Linux, I'll assume you haven't used an SSH client like PuTTY. You'll need to download that before you get started. You can get it here: http://www.putty.org/

Here's how I got jlesage's crashplan pro docker image up and running on my Synology:

From Synology DSM:

1. Open Package Center.
2. Stop Patter's CrashPlan package if you are migrating from it.
3. Install the Docker package from the Package Center interface (this you already did).
4. Close Package Center.
5. Open Docker.
6. Click 'Registry' on the list to the left (below 'DSM').
7. In the search bar at the top of the Docker window, enter jlesage and click the 'Search' button. You should see jlesage/crashplan-pro at the top of the list. Highlight it and click the 'Download' button. Leave the tag as latest in the 'Choose Tag' window that pops up and click the 'Select' button.
8. You should now see a '1' pop up to the right of 'Image' below 'Registry'. Let your Synology complete the download (it's a 499 MB download).
9. Once the download is complete, open Control Panel from the DSM interface.
10. Click on 'Terminal & SNMP' from Control Panel.
11. Click the box next to 'Enable SSH service'.
12. Open PuTTY.

From PuTTY:

1. In the 'PuTTY Configuration' window, enter the local IP address (192.168.xxx.xxx) for your Synology where it says 'Host Name (or IP address)'. Then click the 'Open' button, which will open up a Terminal Session.
2. Enter the username and password at the prompt for a user with Admin privileges.
3. Enter the following command to get 'root' access: sudo -i Press Enter. Enter your password again and press Enter.
4. Quick note about PuTTY: if you highlight the code blocks on this site and copy with Ctrl+C, you'll paste in PuTTY with the Right-Click Mouse Button instead of Ctrl+V.
5. You will need to create the /docker/appdata/crashplan-pro configuration folder manually by entering the following command: mkdir -p /volume1/docker/appdata/crashplan-pro Press Enter.
6. Create the Docker container image by entering the following command at a minimum (there are other environment variables you can introduce if you see fit or necessary - just check jlesage's documentation on those specifics) as a single continuous string (no line break) and let it do its thing: docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro The reason we are doing this through SSH/PuTTY is because the Synology Docker program won't let you map Volume1.
7. At this point your Docker container has been created. You can now close your PuTTY session window.

From Synology DSM:

1. Uncheck the box next to 'Enable SSH service' in the 'Terminal & SNMP' window in the Synology DSM interface.
2. Open Docker.
3. Click 'Container' from the list on the left. You should now see a 'crashplan-pro' entry with it showing as 'Running'.

From you Web Browser:

1. Log into the CrashPlan PRO container GUI by pointing your browser to your IP address of the synology at port 5800 (http:\192.168.XXX.XXX:5800)
2. Sign into your CrashPlan account through the web GUI you just accessed.
3. The following assumes you were using Patters' CrashPlan Package initially and you need to 'adopt' the backup.
4. Click the 'Replace Existing' button to start the wizard.
5. Skip 'Step 2 - File Transfer'.
6. Once done with the wizard, go to your 'Device Details' and click 'Manage Files'. Since we mapped the Synology's 'Volume1' to the Docker Container's 'Volume1', the Docker CrashPlan-Pro Container should automatically see and recognize the files/folders previously backed up by Patters' CrashPlan Package (assuming you were using it).
7. Perform a backup and the system will make sure it is the same by scanning all the files and making sure everything matches. If done correctly you shouldn't need to re-upload everything to CrashPlan's servers.
8. You can close the browser window and you’re done! As long as the Docker Container is up and running, you’ll be backing up to CrashPlan. Any changes to your backup set like adding new folders to your backup will be done through the web GUI.

I hope this helps you get up and running!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-354888938 , or mute the thread https://github.com/notifications/unsubscribe-auth/Aha2YPXKawAZHkLOgNQQG6H9xqRX8E5nks5tGqmYgaJpZM4RRA40 . https://github.com/notifications/beacon/Aha2YJ8BGk8A8XIdbrrpoQUTv_RrrtAuks5tGqmYgaJpZM4RRA40.gif

[excalibr18]

Did you type sudo -i before you ran the docker command?

[bgmess]

Great catch…I typed sudo -1, not i.

I’ll try that again.

Brian

From: excalibr18 [mailto:[email protected]] Sent: Monday, March 5, 2018 4:09 PM To: jlesage/docker-crashplan-pro [email protected] Cc: bgmess [email protected]; Author [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

Did you type sudo -i before you ran the docker command?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-370600592 , or mute the thread https://github.com/notifications/unsubscribe-auth/Aha2YI7IPsmMEorLxjCERHaiWs82m9nHks5tbcVwgaJpZM4RRA40 . https://github.com/notifications/beacon/Aha2YF_mECKMsyHrrh67U0WisB9US8N-ks5tbcVwgaJpZM4RRA40.gif

[bgmess]

That worked…thanks.

How do I choose which files on my Nas I want to backup? I seem to be missing that part.

Regards,

Brian

From: excalibr18 [mailto:[email protected]] Sent: Monday, March 5, 2018 4:09 PM To: jlesage/docker-crashplan-pro [email protected] Cc: bgmess [email protected]; Author [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

Did you type sudo -i before you ran the docker command?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-370600592 , or mute the thread https://github.com/notifications/unsubscribe-auth/Aha2YI7IPsmMEorLxjCERHaiWs82m9nHks5tbcVwgaJpZM4RRA40 . https://github.com/notifications/beacon/Aha2YF_mECKMsyHrrh67U0WisB9US8N-ks5tbcVwgaJpZM4RRA40.gif

[excalibr18]

You can do that from within the CrashPlan GUI. Log into it via your website browser and look for a button called "Manage Files". From there it will show a directory listing from which you can select from using check boxes.

[bgmess]

I can’t thank you enough. Your instructions were perfectly clear, and the process worked flawlessly.

Thanks!

Brian

From: excalibr18 [mailto:[email protected]] Sent: Tuesday, March 6, 2018 9:02 AM To: jlesage/docker-crashplan-pro [email protected] Cc: bgmess [email protected]; Author [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

You can do that from within the CrashPlan GUI. Log into it via your website browser and look for a button called "Manage Files". From there it will show a directory listing from which you can select from using check boxes.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-370831165 , or mute the thread https://github.com/notifications/unsubscribe-auth/Aha2YN6rb2n8_V6CdbDgTI5dLPHhPq84ks5tbrMHgaJpZM4RRA40 . https://github.com/notifications/beacon/Aha2YF9_30Ulxk3SWVXWhavXazxCJnH6ks5tbrMHgaJpZM4RRA40.gif

[beBerlin]

Thanks for the article. The description also helped me a lot. Unfortunately, I still have a problem.

I see the "CrashPlan Web GUI Interface" but I can not log in. See photo in the link: Can someone help me? https://www.dropbox.com/s/oqt0mgf3wze9i8z/Ohne%20Titel.jpeg?dl=0

[excalibr18]

Try following the steps in the Readme section: https://github.com/jlesage/docker-crashplan-pro/blob/master/README.md#device-status-is-waiting-for-connection

[jlesage]

Also, make sure you are running the latest version of the container image.

[dmase2]

I'm having a problem connecting to the crashplan-pro servers. I get the same message as beBerlin above. I've tried clearing the cache and deleting the appdata directory per other suggestions. I am able to ping the crashplan servers from the NAS. Any other ideas?

[jlesage]

Are running the latest version if the image?

[dmase2]

Yes.

[excalibr18]

@beBerlin & @dmase2:

1. Can you confirm you are able to log into CrashPlan's web interface (https://web-eam-msp.crashplanpro.com/login/#/login)?

2. Have you tried completely removing the container and deleting everything within the /docker/appdata/crashplan-pro folder on the Synology and starting over?

[dmase2]

Yes, I have a windows computer that backs up with no problems from the same network. I just confirmed again that I can access the web site with no issues.

I have removed the container and deleted the docker/appdata/crashplan-pro directory with no success.

Just to confirm, I'm on version 6.7.0.4503.

This is my startup script for the container. I'm running it from an SSH connection.

docker run -d --name=crashplan-pro1 -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=3072M -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

I notice that there is a green unlock icon to the right of the Crashplan for Small Business logo in the upper left is that normal?

[excalibr18]

@dmase2: So when you get to the part of the guide that says:

From your Web Browser:

1. Log into the CrashPlan PRO container GUI by pointing your browser to your IP address of the synology at port 5800 (http:\192.168.XXX.XXX:5800)
2. Sign into your CrashPlan account through the web GUI you just accessed.

Are you saying that your the CrashPlan PRO container is not accepting your CrashPlan login credentials?

You mention you have a Windows computer that backs up with no problems. Are you paying for multiple devices on your CrashPlan account? I know they switched to a per-device payment structure when they dropped CrashPlan Home.

As for the green padlock, yes it's normal: EDIT: the padlock will be "locked" if you are using the SECURE_CONNECTION environment variable. It'll be "unlocked" if you aren't using it.

[dmase2]

when i address the container via http://192.xxx.xxx.xxx/5800 I get the first part of the log in screen for crashplan pro where I can enter email. When I enter the email address, I get the following after a minute or so.

When I log in from my windows machine, after entering the email address I get a new dialogue box for entering my password.

The following is the icon I referred to earlier, note it is in "unlock" position.

Thanks for the help.

[jlesage]

Look at /volume1/docker/appdata/crashplan-pro/log/service.log.0 to have more details about the failure.

The icon in unlock position is normal when you connect over http: it means that the unencrypted connection to the UI succeeded.

[dmase2]

From the service.log.0 this appears to be the problem area. Is the unresolved address on the server side or on my side?

[03.15.18 15:13:54.953 WARN DefaultGroup .code42.messaging.peer.PeerGroup] PG::DefaultGroup PeerException attempting to connect. RemotePeer-[guid=42, state=CONNECTING]; Session-null e=com.code42.peer.exception.PeerException: IOExcepton opening remote session. guid=42, remoteLocation=TargetAndProxyLocation [DIRECT -- target=[[[email protected]:443(server)], pbKRequestable=true]], timeout=30000, e=Unexpected Exception in connect() for remoteAddress=central.crashplanpro.com:443, java.nio.channels.UnresolvedAddressException

[jlesage]

On yours. Run the following commands on your host to see if the address can be resolved in both cases:

nslookup central.crashplanpro.com

docker exec crashplan-pro1 nslookup central.crashplanpro.com

[dmase2]

dns problem from docker?

[dmase2]

@jlesage I added "--net=host" to the script and it now seems to be working. Able to log in and crashplan is beginning the sync. Thank you for the docker image and the help. Do you have a shareware contribution method in place? Doug

[excalibr18]

Donation link for jlesage is here:

[jlesage]

@dmase2, if setting the network mode to “host” fixes the issue, then you seems to have an issue with your docker setup.

Maybe this can help? https://forum.synology.com/enu/viewtopic.php?t=109640 https://www.google.ca/amp/s/amp.reddit.com/r/docker/comments/64tst6/synology_nas_docker_networking_problem/

[dmase2]

@jlesage Neither link seemed to help. I have already tried completely unloading docker and re-installing it from scratch. I'm not sure how to apply the second link's solution to my situation. It seemed like a temp solution anyway.

[PNMarkW2]

I've followed the step and it seems to be running, but I can not get to the container GUI. When I try to go to 192.168.xxx.xxx:5008 I get the message "This site can't be reached. 192.168.xxx.xxx refused to connect". I'm sure I'm missing something simple, yet I verified that I set the port correct, I've checked the firewall setting, clearly, I can get to the NAS since I setup CrashPlan, and run other apps there like Plex.

Any thoughts?

[jlesage]

By default, the port is 5800, not 5008. Did you mapped the port to another one? Which docker run command did you use?

[PNMarkW2]

As I said, a simple mistake. No, I didn't change it, I was just typing it wrong, several times and in multiple places. :-)

[jlesage]

Then more information is needed to determine the problem: The parameters of the container (the complete docker run command you used to create the container or the output of docker inspect) and the container's log (docker logs).

[PNMarkW2]

Sorry if I wasn't clear, the only problem I had was that I mistyped the port multiple times. Once you pointed out that mistake on my part and I corrected it, I was able to log in. Totally human error on my part.

I do have one question though, I saw this once but can't find it now, what file and setting do I need to modify to adjust the size of the backup? I've been bitten before by CrashPlan only backing up part of a collection because of that.

[jlesage]

Not sure to see what you are talking about. Normally there is no file that need manual modification.

[PNMarkW2]

Things seem to be up and running for the first time since the start of Feb, and I thank you for the effort getting this up and running plus sharing it.

However, I now get this message regularly. I've looked for a file or setting that I could tweak, but I haven't found one yet. Any thoughts from the experts? I've found the program crashed a couple times and had to restart it.

[jlesage]

Here you go: https://github.com/jlesage/docker-crashplan-pro/blob/master/README.md#crashes--maximum-amount-of-allocated-memory

[buffoon]

I've been attempting to get this running for about a week now with no luck. I hope I'm missing something simple here. I've deleted the container and the config multiple times and I'm always stuck on the screen with this prompt:

my docker run command is:

docker run -d --name=crashplan -p 5800:5800 -e USER_ID=65534 -e GROUP_ID=65534 -v /mnt/config/Docker/crashplan:/config:rw -v /mnt/config/Vault:/storage:ro jlesage/crashplan-pro

The only error in the service.log.0 is that it can't find the .ui_info file (it never deos get created):

[03.18.18 11:25:02.880 ERROR main ackup42.service.ui.UIInfoUtility] Unable to find a file to read the address, token, and port out of due to IO, check that the file is readable?, java.io.IOException: Unable to create parent folders for .ui_info file. folder=/.crashplan STACKTRACE:: java.io.IOException: Unable to create parent folders for .ui_info file. folder=/.crashplan at com.backup42.service.ui.UIInfoUtility.setUIConnectionDetails(UIInfoUtility.java:99) at com.backup42.service.CPService.writeUIInfoFile(CPService.java:1407) at com.backup42.service.CPService.start(CPService.java:668) at com.backup42.service.CPService.main(CPService.java:2064)

When I use the nslookup command I get this:

tmp # nslookup central.crashplanpro.com nslookup: can't resolve '(null)': Name does not resolve

Name: central.crashplanpro.com Address 1: 216.17.8.5 eam-msp.crashplanpro.com Address 2: 216.17.8.56 central.crashplanpro.com

service.log.0 file:

service.log

[jlesage]

Looks like a permission issue. Are you sure that the user you specified can write to /mnt/config/Docker/crashplan?

[buffoon]

As far as I can tell that user/group has full read/write/execute permissions to that folder. It is able to write all the other data in that directory.

[jlesage]

Can you provide the output of the following commands while the container is running (run on host):

docker inspect crashplan

docker exec crashplan cat /etc/passwd

Also, can you try to run the container without mapping /config?

[buffoon]

Thanks for looking into this. Here is the output of the inspect and cat commands: docker inspect.txt cat.txt

Without mapping the /config directory, I get the same result. The service.log.0 without mapping is here: service.log

[jlesage]

Ok I found a bug that cause the issue you are seeing. It is caused by the user ID you use, which matches another user in /etc/passwd. I will fix that. As a workaround, you can edit /defaults/passwd in the container and remove the line containing the user nobody (id 65534). Then restart the container.

[buffoon]

That did it thanks!

[beBerlin]

@excalibr18 I have reinstalled the container "jlesage / crashplan-pro". And previously deleted all folders.

I can also log in to https://web-eam-msp.crashplanpro.com/login/#/login?to=%2Flogin%2F%23%2Flogin.

And that's why I do not understand why I can not log in to the web GUI jlesage / crashplan-pro.

Who can help me?

[jlesage]

Can you clarify the issue? Which error are you getting exactly?

[beBerlin]

See photo in the link: https://www.dropbox.com/s/oqt0mgf3wze9i8z/Ohne%20Titel.jpeg?dl=0

[jlesage]

Can you provide the log/service.log.0 log file? You can find it on the host in the folder you used to map /config.

[beBerlin]

https://www.dropbox.com/s/w9kswibhqzsl3m1/service.log.0?dl=0 I hope that's the right file?

[jlesage]

On which system are you running the container? The problem seems to be that central.crashplanpro.com can't be resolved.

You can confirm if the host is able to resolve by running:

nslookup central.crashplanpro.com

And confirm if the container is also able to resolve (also run the command on the host):

docker exec <name of your container> nslookup central.crashplanpro.com

[beBerlin]

I use DS918 +. I did not understand the other instructions. can you put it another way? or help others?

[jlesage]

Are you able to access the NAS via SSH? You first need to enable the SSH service (https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/system_terminal) and then use PuTTY (https://www.synology.com/en-global/knowledgebase/DSM/tutorial/General/How_to_login_to_DSM_with_root_permission_via_SSH_Telnet). Once connected, you will be able execute the 2 provided commands.

[beBerlin]

I have executed the commands. See image. https://www.dropbox.com/s/inocihhdmy1neen/Ohne%20Titel%203.jpeg?dl=0

[bigtfromaz]

This is bit of a guess but I see that from the DiskStation nslookup received it’s reply from a DNS server it reached using IPv6. If your container is connected to a bridge network, check to see if the bridge has IPv6 enabled.

From: beBerlin [email protected] Sent: Sunday, April 8, 2018 11:34 AM To: jlesage/docker-crashplan-pro [email protected] Cc: Tom Hebert (HCI) [email protected]; Comment [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

I have executed the commands. See image. https://www.dropbox.com/s/inocihhdmy1neen/Ohne%20Titel%203.jpeg?dl=0

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-379571688, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRuFsGZSdaxg3ZCo-ql4KqpjKIVSYks5tmlgBgaJpZM4RRA40.

[jlesage]

So at least we confirmed that the container is not able to resolve the DNS name. Can you provide the output of the following commands:

cat /etc/resolv.conf

docker exec crashplan-pro cat /etc/resolv.conf

[beBerlin]

Enclosed the commands:

https://www.dropbox.com/s/yyh2nd4swzy6ei5/Ohne%20Titel%204.jpeg?dl=0

[jlesage]

So it seems that DNS resolution has to be done over IPv6 on your network. And since IPv6 doesn't seem to be enabled for your container, it's not possible for the latter to reach CrashPlan's server. Which router are you using?

@bigtfromaz, is there a setting to enable IPv6 in Synology?

[beBerlin]

FRITZ!Box 6490 Cable

https://www.dropbox.com/s/7q5zjx7hvu4jps2/Foto%2011.04.18%2C%2006%2045%2002.jpg?dl=0

[bigtfromaz]

Yes. When you create a bridge network you can select “Enable IPv6” . It seems to require an IPv4 address range for all bridge networks. IPv6 is optional.

It appears that the Synology does not support autoconfiguration. So using a local subnet would be in order. Something like fd01:10:1000:1000::/64 would be in order. They call it a subnet but in context I think they mean prefix.

It also asks for an IP range which I suspect will be used as a pool of addresses to give to container that are added to the network. Here is an example of a 32 bit subnet carved out 64-bit prefix. An example here might be fd01:10:1000:1000:1000:1000::/32 . You could probably use the prefix for this as well.

The gateway must be set in the same subnet, something like be fd01:10:1000:1000::1 .

I haven’t played with this at all but it should work pretty much the same as an IPv4 bridge network. Synology support might be helpful in this regard.

With that said, it may be easier to use the host network rather than a bridge. The container should get a unique address and a correct gateway address when IPv6 autoconfigures. NAT is not used in IPv6. It should be secure.

@jlesage do know of a small container I can deploy with just linux/bash in order to do some testing???

Bigtfromaz

From: Jocelyn Le Sage [email protected] Sent: Tuesday, April 10, 2018 5:13 PM To: jlesage/docker-crashplan-pro [email protected] Cc: Tom Hebert (HCI) [email protected]; Mention [email protected] Subject: Re: [jlesage/docker-crashplan-pro] Need basic help with installation - need more details (#34)

So it seems that DNS resolution has to be done over IPv6 on your network. And since IPv6 doesn't seem to be enabled for your container, it's not possible for the latter to reach CrashPlan's server. Which router are you using?

@bigtfromazhttps://github.com/bigtfromaz, is there a setting to enable IPv6 in Synology?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/34#issuecomment-380286256, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRoW1gC-BrTcpDIq5Rdd8fI9k0OStks5tnUp_gaJpZM4RRA40.

[jlesage]

@beBerlin, so it seems that your solutions are:

• Check your router settings to see if there is anything that would block DNS resolution over IPv4.
• Try to configure a separate bridge with IPv6 enabled.
• Switch the network mode to "host" instead of "bridge".

@bigtfromaz, you can use an ubuntu baseimage, like ubuntu:16.04. There is probably a baseimage for any distro you want.

[beBerlin]

Thank you for the great help. But I do not know how to make the settings.

[bigtfromaz]

I will try.

From you previous post I know that your container is not receiving a public address. Without one, it can't talk to the internet.

So I first want to confirm that your host machines are being assigned public addresses.

Let's start there. On your host machine, please run an ifconfig, or on a PC run an IPCONFIG command. One of my sandbox machines looks like this:

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . : myDomain.com IPv6 Address. . . . . . . . . . . : 2600:8800:e00:1620:xxxx:xxxxxxxx:xxxx Temporary IPv6 Address. . . . . . : 2600:8800:e00:1620:5044:b90f:6577:7bc7 Temporary IPv6 Address. . . . . . : 2600:8800:e00:1620:9870:1209:40e9:9835 Link-local IPv6 Address . . . . . : fe80::c19b:5c07:fc1b:6489%12 IPv4 Address. . . . . . . . . . . : 192.168.x.x Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::1:1%12 192.168.x.x You will see addresses that begin with "f", e.g. fe80. These are private addresses and no traffic to or from those will traverse the internet. We first need to check that you are receiving a public address, e.g. 2600:8800:e00:1620:xxxx:xxxxxxxx:xxxx . In this case my ISP has assigned this 64-bit prefix to me. 2600:8800:e00:1620. It leaves me with 64 bits to use here for local subnets and addresses (about 4 gig).

Please run the ifconfig (Linux) or ipconfig (Windows) command on one or more physical machine and send the results.

[damaverick82]

Hello,

I changes my crashplan pro installation on my Synology a few months ago from the Patters version to the lesage docker version.

Everything seems to work fine except for one thing. The docker instance seems to find a lot more data then possible. I have a 716+ Synology with 2 3TB disks in raid 1 with about 400GB of data. The lesage docker client from crashplan says it needs to backup 141TB of data and therefore never finishes. (even when I deselect a lot of data) The Patters version did see the right amount of data.

I already configured the docker from scratch. I even configured crashplan completely from scratch by removing everything online

[jlesage]

Did you mapped /storage/ to /volume1/ ? If yes, make sure you didn't selected any docker related folders.

[jlesage]

More specifically, /volume1/@docker should not be selected.

[damaverick82]

Ah thanks, that did the trick for me. There was indeed a docker folder mapped. Although in my case is was on volume2 :)

[beBerlin]

@bigtfromaz I used Mac, what's the command on the Mac? with "ipconfig" appears: "usage: ipconfig where is one of waitall, getifaddr, ifcount, getoption, getpacked, getv6packet, set, setverbose "

[jlesage]

@beBerlin, is your Synology also act as your DNS server? If yes, check https://github.com/jlesage/docker-crashplan-pro/issues/79

[bigtfromaz]

I not a Mac expert but I suspect the command would be ifconfig: []https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man8/ifconfig.8.html

Do check out #79 but also send the listing I requested above. If you only have IPv6 then, unless you have a static prefix, you will want to use the host network rather than a bridge network. IPv6 does not use NAT so you can't access the internet with a private address.