May 17, 20251 yr 1 hour ago, Flubster said: Haven't tried downloads, I will later when it's finished catching up. Thanks so much for the fork. While I relied on ChatGPT to walk me through downloading, building and then using your fork, I can confirm that with your fork I'm seeing the best of both worlds -- fast uploads between 2-300mbps and downloads between 300-400mbps!!! Assuming there's no downside, I'm hoping this can get merged into the main build soon
May 17, 20251 yr Obviously the latest version of crashplan is 11.5.0 so this shouldn't be changed on the main repo, that should be the latest version. This maybe intentional by crashplan or could just be a bad release. Every other release seems to nag when it's out of date with crashplan attempting to auto update (and failing as it should on the container) every day. 11.4.0 doesn't. I find this suspicious. But I have raised a support request.
May 23, 20251 yr HelloI am having this message when connecting to the console - Unable to connect to destination for 5.5 daysWhat can I do? I restarted the docker, it seems to be running, logs are clean.
May 23, 20251 yr 4 hours ago, michael123 said:HelloI am having this message when connecting to the console -Unable to connect to destination for 5.5 daysWhat can I do? I restarted the docker, it seems to be running, logs are clean.Check this post: https://forums.unraid.net/topic/59647-support-djoss-crashplan-pro-aka-crashplan-for-small-business/page/54/#findComment-1554378 and follow the quotes backwards.It just seems to do that every now and then. Well, it does recently, anyway...
May 24, 20251 yr 10 hours ago, Free Man said:Check this post: https://forums.unraid.net/topic/59647-support-djoss-crashplan-pro-aka-crashplan-for-small-business/page/54/#findComment-1554378 and follow the quotes backwards.It just seems to do that every now and then. Well, it does recently, anyway...But it is not running now -- says it can't connect
May 24, 20251 yr Today I got error '400'I entered the url in my browser, and got the same error 400[ is there an easy way to copy/paste the url? I just entered character by character..]
May 27, 20251 yr Since I updated a docker, CrashPlan is doing 'synchronization'. But soooo slow, I have 12TB and for a couple of days it merely accomplished less than 20%Some kind of throttling, but the issue is that there is no backup for these 2 weeks. I am running good old physical backup on external hard driveI tried to look for alternatives, but for this price (10$ per month) I could not..Is there anything else that integrates with unRAID for more or less same price? Edited May 27, 20251 yr by michael123
June 3, 20251 yr On 5/17/2025 at 12:14 PM, Flubster said:Obviously the latest version of crashplan is 11.5.0 so this shouldn't be changed on the main repo, that should be the latest version. This maybe intentional by crashplan or could just be a bad release. Every other release seems to nag when it's out of date with crashplan attempting to auto update (and failing as it should on the container) every day. 11.4.0 doesn't. I find this suspicious. But I have raised a support request.Any fix yet? I'm still using your fork with great success
June 4, 20251 yr no response to the ticket. I haven't tried 11.6.0, which the latest image is on which may have actually fixed it.
September 15, 2025Sep 15 Not honoring memory limit?--memory=6144M via Extra Parameters fixed it ignoring the template limit.24gb is my machine memory and I set the docker limit to 6144 via the max memory setting in the template.Other dockers are what I set.CrashPlan v11.6.0Docker Image v25.07.2CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS16af8e353fba storagenode 3.03% 227.5MiB / 4GiB 5.55% 108MB / 88MB 1.17GB / 137MB 71d44575bebc68 storagenodebig 2.18% 226MiB / 4GiB 5.52% 181MB / 124MB 1.58GB / 158MB 783f7ff220871c myst 0.75% 88.7MiB / 1GiB 8.66% 361MB / 397MB 2.33GB / 9.72MB 16f10223b89d2a CrashPlanPRO 73.40% 780MiB / 23.43GiB 3.25% 27.5MB / 34.3MB 2.24GB / 3.14MB 208
September 18, 2025Sep 18 On 1/24/2023 at 10:27 PM, Djoss said: You can use the "Tips and Tweaks" unRAID plugin to increase the number of watches. The plugin shows the current number, along with the number used.There is no recommended values, since it depends directly on the number of files you backed. Using the plugin, try to increase the "Max User Watches" and then see how it goes.I'm getting an "exceeding inotify's max watch limit" error from crashplan, yet I have the max watches set at 750,000, and only 7707 currently in use.Any other suggestions?
December 16, 2025Dec 16 I'm unable to start the Crashplan docker. Currently I'm migrating files so I know my space usage went up significantly. And I just had an issue with the Crashplan docker running some high CPU usage that bogged down the system. I tried to stop the docker, but it wouldn't stop. So I restarted the server. Since rebooting I'm getting "[logmonitor ] ERROR: CrashPlan is exceeding inotify's max watch limit. Real-time file watching cannot work properly. The inotify watch limit needs to be increased on the host." With the Tips and Tweaks plugin, I've upped the max number to 2090000000. I don't think it can go any higher because if I increase the number any more the settings don't change even if the number is increased. Current Inotify SettingsMax User Watches = 2090000000Current User Watches = 351Available User Watches = 2089999649Max User instances = 128 This is a heck of a lot higher than it used to be, but Crashplan still won't start. It gives an execution error. When I look at the log for the docker container it has an error that I show above. It has couple other warnings, which I assume aren't causing the problem. (Here is a snippet showing those.)[xvnc ] Could not find any render nodes[xvnc ] Failed to initialize DRI3 extension[xvnc ] Mon Dec 8 20:01:08 2025[xvnc ] vncext: VNC extension running![xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660)[xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900[xvnc ] vncext: created VNC server for screen 0[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x14fddaa509b5 for event 2[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x14fddaa509b5 for event 3[supervisor ] starting service 'nginx'...Thoughts on how to fix this?
December 16, 2025Dec 16 1 hour ago, tnorman said:I'm unable to start the Crashplan docker. Currently I'm migrating files so I know my space usage went up significantly. And I just had an issue with the Crashplan docker running some high CPU usage that bogged down the system. I tried to stop the docker, but it wouldn't stop. So I restarted the server.Since rebooting I'm getting "[logmonitor ] ERROR: CrashPlan is exceeding inotify's max watch limit. Real-time file watching cannot work properly. The inotify watch limit needs to be increased on the host."With the Tips and Tweaks plugin, I've upped the max number to 2090000000. I don't think it can go any higher because if I increase the number any more the settings don't change even if the number is increased.Current Inotify SettingsMax User Watches = 2090000000Current User Watches = 351Available User Watches = 2089999649Max User instances = 128This is a heck of a lot higher than it used to be, but Crashplan still won't start. It gives an execution error. When I look at the log for the docker container it has an error that I show above. It has couple other warnings, which I assume aren't causing the problem. (Here is a snippet showing those.)[xvnc ] Could not find any render nodes[xvnc ] Failed to initialize DRI3 extension[xvnc ] Mon Dec 8 20:01:08 2025[xvnc ] vncext: VNC extension running![xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660)[xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900[xvnc ] vncext: created VNC server for screen 0[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x14fddaa509b5 for event 2[xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x14fddaa509b5 for event 3[supervisor ] starting service 'nginx'...Thoughts on how to fix this?A couple hours later:I had a thought and decided to change the Max Memory setting in the docker's more settings area. I think I had this same issue when I installed this docker and I think that was how I actually fixed the issue mentioned earlier. I ran into an issue while doing this change. For some reason, when my changes were being rewritten, the docker would fail to be created and the error notification said a port was already in use. I checked my list of ports, it wasn't being used by another docker, but for some reason the docker thinks it is, so I also changed the ports being used in the docker. This allowed the docker to be correctly written. Now the docker is running again. So, I'm not sure if I ever really needed to change the inotify settings.
January 2Jan 2 CrashplanPro container starts and runs but the container logs just show the crashplan engine starting and restarting over and over again. I opened a shell in the container to look at /config/log/service.log.0 and it shows this error:[01.01.26 19:22:59.801 ERROR main com.backup42.service.CPService] Error starting up, org.bouncycastle.crypto.fips.FipsOperationError: proportionate test failed STACKTRACE:: org.bouncycastle.crypto.fips.FipsOperationError: proportionate test failed at org.bouncycastle.crypto.fips.FipsStatus.moveToErrorStatus(Unknown Source) at org.bouncycastle.crypto.fips.ContinuousTestingEntropySource.getEntropy(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.getEntropy(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.init(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.<init>(Unknown Source) at org.bouncycastle.crypto.fips.FipsDRBG$HashDRBGProvider.get(Unknown Source) at org.bouncycastle.crypto.fips.DRBGPseudoRandom.lazyInitDRBG(Unknown Source) at org.bouncycastle.crypto.fips.DRBGPseudoRandom.getSecurityStrength(Unknown Source) at org.bouncycastle.crypto.fips.FipsSecureRandom.getSecurityStrength(FipsSecureRandom.java:102) at org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider.getDefaultSecureRandom(Unknown Source) at org.bouncycastle.jcajce.provider.BaseSignature.engineInitSign(Unknown Source) at java.base/java.security.Signature$Delegate.engineInitSign(Unknown Source) at java.base/java.security.Signature.initSign(Unknown Source) at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source) at com.code42.crypto.declarative.C42CryptoCertificateApi.generateCertificate(C42CryptoCertificateApi.kt:91) at com.code42.crypto.declarative.C42CryptoCertificateApi.certBuilder$lambda$0(C42CryptoCertificateApi.kt:46) at com.code42.crypto.declarative.C42CertificateBuilder.generateCertificate(C42CertificateBuilder.kt:60) at com.backup42.service.CPService.createNetworkLayerConfig(CPService.java:832) at com.backup42.service.CPService.constructPeerControllers(CPService.java:782) at com.backup42.service.CPService.start(CPService.java:456) at com.backup42.service.CPService.main(CPService.java:1417) Complete service.log.0 is attached for this startup. Anyone seen this before and have any ideas how to resolve?Application: CrashPlan Application Version: 11.8.0 Docker Image Version: 25.12.4 Docker Image Platform: linux/amd64 CrashPlanPRO_service.log.0.txt
January 5Jan 5 Author On 1/1/2026 at 10:32 PM, Homerr said:CrashplanPro container starts and runs but the container logs just show the crashplan engine starting and restarting over and over again. I opened a shell in the container to look at /config/log/service.log.0 and it shows this error:[01.01.26 19:22:59.801 ERROR main com.backup42.service.CPService] Error starting up, org.bouncycastle.crypto.fips.FipsOperationError: proportionate test failed STACKTRACE:: org.bouncycastle.crypto.fips.FipsOperationError: proportionate test failed at org.bouncycastle.crypto.fips.FipsStatus.moveToErrorStatus(Unknown Source) at org.bouncycastle.crypto.fips.ContinuousTestingEntropySource.getEntropy(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.getEntropy(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.init(Unknown Source) at org.bouncycastle.crypto.fips.HashSP800DRBG.<init>(Unknown Source) at org.bouncycastle.crypto.fips.FipsDRBG$HashDRBGProvider.get(Unknown Source) at org.bouncycastle.crypto.fips.DRBGPseudoRandom.lazyInitDRBG(Unknown Source) at org.bouncycastle.crypto.fips.DRBGPseudoRandom.getSecurityStrength(Unknown Source) at org.bouncycastle.crypto.fips.FipsSecureRandom.getSecurityStrength(FipsSecureRandom.java:102) at org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider.getDefaultSecureRandom(Unknown Source) at org.bouncycastle.jcajce.provider.BaseSignature.engineInitSign(Unknown Source) at java.base/java.security.Signature$Delegate.engineInitSign(Unknown Source) at java.base/java.security.Signature.initSign(Unknown Source) at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source) at com.code42.crypto.declarative.C42CryptoCertificateApi.generateCertificate(C42CryptoCertificateApi.kt:91) at com.code42.crypto.declarative.C42CryptoCertificateApi.certBuilder$lambda$0(C42CryptoCertificateApi.kt:46) at com.code42.crypto.declarative.C42CertificateBuilder.generateCertificate(C42CertificateBuilder.kt:60) at com.backup42.service.CPService.createNetworkLayerConfig(CPService.java:832) at com.backup42.service.CPService.constructPeerControllers(CPService.java:782) at com.backup42.service.CPService.start(CPService.java:456) at com.backup42.service.CPService.main(CPService.java:1417) Complete service.log.0 is attached for this startup.Anyone seen this before and have any ideas how to resolve?Application: CrashPlan Application Version: 11.8.0 Docker Image Version: 25.12.4 Docker Image Platform: linux/amd64 CrashPlanPRO_service.log.0.txtIs this on a new install ? Or the container already worked in the past ?
January 8Jan 8 Author This might be caused by an issue on the host. Did you try to reboot the server ?
January 9Jan 9 Yes, there have been several reboots while trying to solve this issue. I also did verify that my Crashplan Pro account is in good standing. I normally use Chrome, but have also tried to open this in Firefox with no luck either.Attached is a pic of what I get, including the copy/paste sidebar.
January 14Jan 14 If I just delete the docker and then delete the docker image (hitting the X under the title name as if adding a new one), is there anything else that I should clear from the system in order to prepare for a clean download and install of the docker?I ask because I did try this when I was first having the issue, but it all seemed to install the docker and run with the same issue so it seems like there is something on my Unraid that is missing or corrupted that is causing the failure. And to verify - is there anything, beside the docker itself, that is needed for the CrashplanPro docker? (I saw one random post about an nvidia driver that is spurring this question.) I just want to try a fresh install again but eliminate any variables first.
January 15Jan 15 I tried a fresh install by:removing the docker image in Unraiddeleted the appdata directory (renamed it to CrashPlanPro_bad)pulling a new image from Appsconfiguring with my account and system information (username, password, max memory)When the container starts and I look at the logs, I see this over and over again:[supervisor ] service 'CrashPlanEngine' exited (with status 0).[supervisor ] restarting service 'CrashPlanEngine'.[supervisor ] starting service 'CrashPlanEngine'...is there anything else that needs to be deleted/moved/renamed other than the CrashplanPro directory in the appdata folder? crashplan.txt Edited January 15Jan 15 by Homerr
January 15Jan 15 Author So is the engine failure caused by the same problem seen in /config/log/service.log.0 ?
March 14Mar 14 On 1/15/2026 at 4:24 AM, Djoss said:So is the engine failure caused by the same problem seen in /config/log/service.log.0 ?Yes. Still having this issue. text error warn system array l.txt
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.