SilverRubicon
-
Posts
55 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by SilverRubicon
-
-
I've updated the container with the recent update and now I only get a black screen when using the web VNC viewer. Already tried forcing an update of the container and restarting it, any other ideas?
I had the same problem. Not sure why this only happens to a few of us. If I perform a clean install (remove everything including container, image, and app data), I see the login screen. If I enter my login information it states 'information is incorrect', immediately disconnects from VNC and is dead from that point forward. Not sure if it's just VNC that is dead or if Crashplan is unresponsive. I can see CP running in top and I can login on the CP website. So I know that my login info is correct.
Finally managed to get this to work. Must have been user error. Or maybe installing 50 times pays off.
-
Yep, CP started to update itself and that breaks the container. I removed the auto update functionality until I can fix it, so please update.
I thought it was just bad timing on my part. I also tried disabling autoupdate and didn't have much success. I did remove all traces of my CP install (image, container, config, etc) and reinstalled your docker image. I run in the same problems I had when I disabled autoupdating. Unable to login, able to login but when adopting my server things stop working, endless reconnection loops. Generally just a nightmare.
I'll just wait for you to update the docker image with the new crashplan. I imagine you're getting tired of it as well. 90% of the time the UI is unnecessary, I just decided to dive back in at the wrong time.
-
Try to open the webgui of crashplan using Edge... Guessing you are using Chrome or Internet Explorer ? Maybe using Kaspersky as a virus scanner ?
It's not the browser but the update of Crashplan on UnRaid. I have tried three different browsers and two different VNC clients. All black screen. It's the update of the Crashplan application that is causing the problem. Not sure exactly what the issue is as there are few errors in /mnt/user/appdata/CrashPlan/log/upgrade.1435813200460_403.1461089974843.log. I assume that updating the application is still not supported without updating the docker image.
-
I can't get started with Crashplan. I'm running 6.1.9 and Crashplan installs ok but when I start it I get a black screen which say is is logged in but won't do anything
I quit using Crashplan and this docker image awhile ago because it became too much work. Tried it again today (as I need to start backing up again) and thought "This is awesome!". Everything came up, vnc client worked, perfect. Then I assigned a VNC password with the variable, restart the docker image, and I now have a black screen. The Crashplan splash screen stated "upgrading" prior to the black screen of death so maybe I just have unbelievably bad timing and Crashplan has updated their software in the last hour. Either way, I also have the black screen but I like what has been done with the docker image.
Ok, reinstalled and everything worked. Crashplan once again upgraded itself and now I'm back to the black screen. Now I remember why I quit using this.
-
Let's indicate this docker will need constant updates by the creator for it work properly. I "think" my engine is running but I'm unable to connect to it and I don't have time to learn how to create my own dockers.
i think the best plan of attack is to have a single Crashplan docker container that is slimmed down version of a lightweight linux. Standalone, single instance. That way everything can be updated as it should be by Code42. As long as Crashplan on linux is supported, this docker will work.
I know very little about Docker, but I'm going to try and get this working on my own. If I do, I'll share what I find.
This is fairly easy to modify to get started...
https://github.com/gfjardim/docker-containers/blob/master/crashplan-desktop/install.sh
-
After 5 years of trouble free use of CrashPlan and unRAID it's turned into a nightmare. My server stopped backing up about 2 weeks ago. Fought through the client and server connection issues and now I have this in my server logs...
07.10.15 11:56:35.274 INFO W721685851_Authorize com.backup42.service.peer.Authorizer ] AUTH:: Authority address: central.crashplan.com/216.17.8.11 [07.10.15 11:56:35.288 INFO W721685851_Authorize com.backup42.service.peer.Authorizer ] AUTH:: Error = CPErrors.Global.CPC_UNAVAILABLE : [central.crashplan.com:443] [07.10.15 11:56:35.295 INFO W721685851_Authorize com.backup42.service.ui.UIController ] UserActionResponse: LoginResponseMessage@958050516[ session=697590079208731733, errors=[CPErrors.Global.CPC_UNAVAILABLE : [central.crashplan.com:443]] ]{} [07.10.15 11:56:35.296 INFO W721685851_Authorize com.backup42.service.peer.Authorizer ] AUTH:: *** END *** Failed after 1min 0sec [07.10.15 11:57:25.304 INFO W771295025_SystemWat ckup42.service.peer.CPCAutoRegisterRetry] Remove AutoRegister retry system check, no longer needed. [07.10.15 11:58:25.307 INFO W771295025_SystemWat om.backup42.service.peer.CPCConnectCheck] Disconnect from CPC after 1min 0sec [07.10.15 11:58:25.308 INFO W771295025_SystemWat com.backup42.service.peer.PeerController] DISCONNECT and REMOVE CPCIs anyone else having trouble connecting to the CrashPlan servers?
I have connected! This is trying my patience.
-
I can't believe this hasn't been caught by anyone else, but there is an error on line 460 in the script
mover_pid=`head -n 1 /ver/run/mover.pid`
it should be
mover_pid=`head -n 1 /var/run/mover.pid`
As far as I know, no implementation of unraid has a /ver directory.
[CONTAINER] CrashPlan & CrashPlan-Desktop
in Docker Containers
Posted
I built my own docker container using your source on github. It works fine. Maybe Code42 has changed something between the last time you built yours and when I built mine. You should just be able to recreate it and have it work.