Comments on: Synology NAS: Running CrashPlan in Docker Container

By: Bobby Meneses

Bobby Meneses — Mon, 18 Dec 2017 06:06:58 +0000

Can’t seem to get the Client to connect anymore, wondering if it has to do with the new updates?

By: tagyoureit

tagyoureit — Wed, 30 Aug 2017 06:48:56 +0000

In reply to Alex. try 'chmod 444 /var/lib/crashplan/.ui_info' to make the file read-only.

By: chris

chris — Thu, 24 Aug 2017 02:38:31 +0000

Hi, any plans to make a crashplan for small business docker now that Crahsplan home is discontinued ?

By: Alex

Alex — Tue, 01 Aug 2017 08:27:19 +0000

In reply to Steve.

Hello,

I too get a new GUID every time the container restarts which is fustrating however once i update the .ui_info on the client computer i can connect. Its also worth checking ui.properties as sometimes it resets aswell.

By: Steve

Steve — Tue, 01 Aug 2017 00:55:36 +0000

Hi excellent article.

The setup has been working perfectly for me, although I’m experiencing an issue when the container restarts.
On container restart a new GUID is generated at /var/lib/crashplan/.ui_info (I’m guessing this shouldn’t be the case) and my crashplan client no longer connects. I then proceed to update the GUID in the crashplan client, but it still gets a timeout when connecting.

Has anyone else experienced this, or have I missed a step in the setup process?