Boyturtle

Well, that's really annoying!! Fortunately, I don't have a great urgency to restore the missing files, but I would like to fix this problem in case I do in the future. I've been in touch via chat with Crashplan support and have not told them that I run this as a docker (they seem to think it's running on Ubuntu 20.04 server, so just let it slide). I've sent them my logs and I've had the following reply and am unsure if I can proceed further with them without letting on about the docker. "Looking through the logs I'm seeing a consistent message that the restore I/O pipe is not able to get created. Typically this is indicative of a permissions issue of the Code42/CrashPlan app. There are a couple of more common reasons this may occur that I would like to have you check. Please ensure that when you run the Code42/CrashPlan app you're not running it as an admin (sudo.) The app itself should be run from the user space. Where are you restoring the files to? Have you attempted to restore the files to the Desktop directly? When selecting the file permissions on the restore you will choose "current" instead of "original". When selecting the files for restore be sure to allow the calculation to complete fully before starting the restore. If the calculation does not have time to fully complete then CrashPlan will report incorrect estimates for completion times. Can you provide an example of the file you're looking to download? How large is the file?" I'm not sure if the above info is helpful to the devs @Djoss? FWIW, I get the "Preparing Files" sticking for a long time, whether I try to restore from the cloud or local hdd, whether it's current or original file permissions and it happens on the smallest of config files (600kb). All the while "Preparing Files" is showing, all backups stop.

I've got a problem with restoring files and I've been advised by Code42 that I need to delete my cache. To do this, I need to stop the service first. Going into the command console (Control+Shift+C) and initiating the Shutdown, Stop or Exit commands does not stop the service in its entirety, but rather it restarts it. According to Code42 knowledge base, I can stop the service by going to /usr/local/crashplan/bin and running ./service.sh stop, but there is no such command available in that directory; those present are startCrashPlanEngine.sh, restartLinux.sh, startCrashPlanGUI.sh, Code42Service, restore-tool and vars.sh) and I'm a bit reluctant to run these in the event that I might break something. Any suggestions?

Thanks for that, I'm back in now. You are a hero I wonder what happened and how come it's not been picked up yet?

Anyone?

I would really like a bit of assistance here. I've been running this docker, without fault for the last 3 months or so. In the last week, when I went to launch it, the web browser would not connect to the page at all. I hadn't made any changes to any configs, so I'm a bit baffled. I looked at the /appdata/dokuwiki/log/php/error.log and was consistently getting following error [02-Aug-2020 08:02:17] ERROR: unable to bind listening socket for address '127.0.0.1:9000': Address in use (98) [02-Aug-2020 08:02:17] ERROR: FPM initialization failed I restarted the app a few times and found that I now get a blank white page (with no errors showing) so I figure the web service part of the docker has gone a bit tits up. Going back to the same error log (/appdata/dokuwiki/log/php/error.log) I note the following now [02-Aug-2020 08:27:59] NOTICE: fpm is running, pid 331 [02-Aug-2020 08:27:59] NOTICE: ready to handle connections I've had a little look around other error logs and found the following error in the /appdata/dokuwiki/log/nginx/error.log 2020/08/06 22:34:08 [error] 350#350: *7 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Class 'dokuwiki\plugin\config\core\Setting\Setting' not found in /app/dokuwiki/inc/deprecated.php:61 Stack trace: #0 /app/dokuwiki/inc/load.php(38): require_once() #1 /app/dokuwiki/inc/init.php(200): require_once('/app/dokuwiki/i...') #2 /app/dokuwiki/doku.php(36): require_once('/app/dokuwiki/i...') #3 {main} thrown in /app/dokuwiki/inc/deprecated.php on line 61" while reading response header from upstream, client: client.ip, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "server.ip:280" There seems to be an entry here every time I start the docker. To be honest, I'm not sure if I'm even looking in the right places for the right errors, but would appreciate some pointers to getting this fixed. Tia

I would love step by instructions on both please. This could be very useful for me in understanding how dockers work and could help with other dockers I have too. Does option 2 above involve writing to the etc/fstab file of the docker to make it persistent? Can you please clarify something for me; when I bash into a docker, am I in effect going into the docker that lives in /mnt/user/system/docker/docker.img? Please excuse my ignorance here, as I'm still very much trying to get my head around how dockers/containers work.

I'm trying to personalise this and change the logo from the chef's head and shoulders to something of my own choosing. I assume that I have to bash into the docker and place a .png file somewhere but have no idea where to put it or how big I need to size it and I guess I'll need to change a setting in a config file to use my image, but I don't know where to start with that either. I've not been able to find anything on the github page. Can anyone here help please?

I'm having a problem with auto uploader from my phone. Pictures and files are uploading twice, causing a file upload conflict and each time I have to select which I've I want to keep. What's seems to be happening is that the files are uploading via the domain ([email protected]) and the server IP address ([email protected]). I'm not sure if it's relevent, but I'm using letencrypt reverse proxy. What's the best way to resolve this please?

I've taken your advice and changed the font. I've also done as you've asked and pm'd you the debug output

I can't see Settings>Credits. Here's a screenshot of my Settings menu Sent from my ONEPLUS A6013 using Tapatalk

No, unfortunately.

Thanks, I tried that first, before I posted here. I am able to access the unraid UI from my phone. I can access the plugin UI by either typing in x.x.x.x:2379 or xx.unraid.net:2379; both which go to the Controlr web portal on https. If I type in the same addresses with 2378, (the default port number on plugin config page), it resolves to the https pages, so I guess https it is being forced. I have no ad-blocker on my phone, but I do use Pihole as DNS which is supposed to block ads across the network.

I'm on the same LAN and not on a guest network. I am able to ping the server from my phone Sent from my ONEPLUS A6013 using Tapatalk

The same, No servers available 😞

I've had your app for several months now and I haven't been able to get it to work as I keep getting the "No servers available" notification when adding server details. I've been too busy to deal with this until now, but I would dearly like to get it fixed and working, so your help would be greatly appreciated. The automatic search just passes my server IP, and the manual does not find it either I have tried port 2378 which is listed in the plugin. I have tried port 80 which is accessible from my LAN (although it resolves to xxx.unraid.net). I have tried with both the Secure switched on and off on all combinations above. I have upped the timeout to 10000 I an running 6.7 and 4.10.0

I'd love to see this too. Any idea when you'll be doing the tutorial?

Ownership was set to root:root. I changed it recursively to nobody:users, changed the destination in Device Preferences>Destinations and it is now block syncing. Hooray!! Although it seems to be working correctly now, can you please confirm that these permissions settings are correct? Thanks for the heads up and guidance btw, it's really appreciated :-)

I didn't originally, but Fix Common Problems plugin brought it up as an error for me, so I changed it. It still didn't work after this. Just in case cache was causing the issue, I stopped the container and cleared it before starting the container again, but this didn't work either. In Device Preferences>Destinations, I thought I might delete the archive on that ext hdd and start again, but the app would not let me delete it. Briefly after this, the hard drive was visible on the main page and began to sync, but then returned with the same error of Archive missing- backup location not available.

Of course it is. What a doofus I am. Too little sleep and too much going on make me do silly mistakes! Thanks for the pointer. Have you any idea how I can get the container to mount the ext hdd? I've mapped the /media drive to /mnt/disks. When I go to Device Preferences>Destinations and click on the drive to change location, it sees the drive in the dialogue box (and sometimes sees the backup archive, but not always), but after selecting the drive, it still shows as archive missing as per the above screen grab.

/storage isn't present in the Manage Files section though, so I am unable to access it

Unfortunately, the rest has not been plain sailing. When logging into my account and following the instructions to take over existing backup, very few of my files are present and the folder structure in the Manage Files section does not contain many of the the contents of the mapped location, so I can't add them to the selection. I copied across from my old desktop to /mnt/user all the data that I previously backed on the desktop and I more or less kept the folder structure. I should have about 1.3 tb in one set, instead I have less than 4MB. The folder /storage doesn't show in the folder list under root in the Manage Files section. The only time I could see /storage was when I looked to restore files. I could not see the ext hdd when attempting to restore from disk, so I mapped it to /mnt. This was found in device preferences, but when I tried to access it, I got an error saying the archive was missing and the location was not accessible. The integrity of my data is still ok, I have it all on the original desktop. When I go back to the desktop and transfer CrashPlan there, it all works fine and all the file structure is fully in place and non of my data is missing. It is also able to see the hard drive backup archive and read/write to it. I have installed and removed this container many times to no avail. Please someone tell me what I've been doing wrong.

Well that's annoying. After trying lots of different things, it's boiled down to my password somehow not being recognised in the container, but working at the Crashplan. I dumbed down my password and I'm now in. Hopefully the rest will be plain sailing :-)

OK, so I'm a bit of a noob with unRAID and dockers and still finding my way around. I already have CPP working on my desktop; I migrated some 6 months ago from home and all is peachy. I've installed the CrashPlanPro docker, made changes to memory (upped to 5120m), it now starts, but I can't log in. The password is correct (I've tried it on the CP site) I've chatted with Code42 guys, did a netcast test to ports 443 and 4287 on their servers (which passed), so they say that everything is ok their end. I've reinstalled the docker a couple of times, with the same result each time (I also deleted the /mnt/user/appdata/CrashPlanPro folder each time before installation). Folder ownership of contents of /mnt/user/appdata/CrashPlanPRO is all set to nobody:users. my.services.xml "authority" grep is <authority address="central.crashplanpro.com:443" hideAddress="true" lockAddress="true"/> I'm getting quite wound up about this now, any suggestions about fixing any simple setting that I may have overlooked would be greatly appreciated

Great that you've got it going. I'd like to do the same thing on the unraid server I'm about to build. Is there any chance that you can do a step by step tutorial here to show the way? Thanks