zero_koop

I didn't get a response in that thread, but I was able to solve the problem myself. I've not used it before so I had to do some research, but I was able to fix the permission problem by running the Tools > New Permissions tool on my Nextcloud share. I don't know what caused the issue in the first place, but it is solved for now. Thanks for your help, but does NOT appear to be a DirSyncPro issue!

Hello. I am also seeking assistance for an issue involving NextcloudPi and DirSyncPro dockers. I started with the DirSyncPro help thread, but after some investigating we think the issue may stem from NextcloudPi. I have NextcloudPi installed on a share called "Nextcloud" with nothing else on the share. The issue I am facing is that DirSyncPro can no longer see my phone camera files that I've backed up to the directory /mnt/user/Nextcloud/nextcloud/data/username1/files/InstantUpload/Camera. I used to be able to see these files and DirSyncPro would copy them to another location automatically, but something changed and DirSyncPro can only see down into the level of: mnt/user/Nextcloud/nextcloud/. Looking at the permission for some of the directories in the Nexcloud share I found: root@Tower:/mnt/user/Nextcloud# ls -l total 3 drwx------ 1 root root 808 Aug 16 18:06 bin/ drwxr-xr-x 1 101 102 440 Sep 5 09:55 database/ drwxr-xr-x 1 root root 288 Mar 11 2022 etc/ drwx------ 1 root sshd 1496 Mar 7 2022 ncp/ drwx------ 1 sshd sshd 776 Mar 7 2022 nextcloud/ My helper in the DirSyncPro thread wondered why the user and group are "sshd" for the nextcloud/ directory. The sshd user and/or server process is a bit beyond my understanding of Linux. But I suppose my first question is: does this output look right? ------------------------- edit: solved, for now I've not used it before so I had to do some research, but I was able to fix the permission problem by running the Tools > New Permissions tool on my Nextcloud share. I don't know what caused the issue in the first place, but it is solved for now and I'll probably return to the thread if it happens again. --------------------------- edit 2: after I made this fix above, DirSyncPro worked again, but before I started up Nextcloud again I decided to update Unraid to 6.11.1 and apply the latest docker update for NextcloudPi. Unfortunately these actions have resulted in breaking Nextcloud. I don't know which of these 3 actions broke Nextcloud, but now I get the error: I am doing a little more testing/research, but I'd be curious to know if it is possible to downgrade the NextcloudPi docker.

Perhaps. I am using NextcloudPi.

Good idea! So... the results I got are confusing: When I set the DirSyncPro "Source Directory" to "/mnt/user/Nextcloud/nextcloud/data/" (three levels lower than what I want) I was not able to see any folders when viewing the "/sourcefiles" folder within the DirSyncPro app. However, when I set the DirSyncPro "Source Directory" to "/mnt/user/Nextcloud/nextcloud/data/usename1/files/" I was able to see the folders beneath it within the DirSyncPro app! So I was able to see down to "/Nextcloud/nextcloud/data/username1/files/InstantUpload/Camera". While poking around in another docker that I have installed (CrashPlan) I notice that app also cannot see down past the "/mnt/user/Nextcloud/" level. Perhaps this speaks to a larger issue with my Nextcloud share, but I'm not sure where to turn to next if it is, besides maybe a permissions issue. ------------------ update: this is the output of the "ls -l" command at the "mnt/user/Nextcloud" level: root@Tower:/mnt/user/Nextcloud# ls -l total 3 drwx------ 1 root root 808 Aug 16 18:06 bin/ drwxr-xr-x 1 101 102 440 Sep 5 09:55 database/ drwxr-xr-x 1 root root 288 Mar 11 2022 etc/ drwx------ 1 root sshd 1496 Mar 7 2022 ncp/ drwx------ 1 sshd sshd 776 Mar 7 2022 nextcloud/ I'm not super familiar with Linux commands, this looks like only the file owner has any permission to the /nextcloud folder. Not sure if that is a problem or not. As far as I know the DirSyncPro docker is also running as the root user.

My docker settings are: Container Path: /sourcefiles Host Path: /mnt/user/ So basically DirSyncPro can see all of my shares including the share named Nextcloud. And it can see a single folder level down into that share until it stops strangely. But if you are asking if the share is located on the cache or not I have "use cache pool" set to "no". Also of potential note is: I have never been able to use Windows Explorer to browse the contents of the "nextcloud" folder on the "Nextcloud" share. I've always received a "you do not have permission to access" error. I wonder if this permission issue, which never affected DirSyncPro is now affecting the docker.

Hello. I am having an issue with DirSyncPro. Things were working fine the last time I checked (early August), but when I try to run the Analyze step I get an error saying the source folder doesn't exist. Sure enough, if I modify the job to re-pick the source folder I can browse down a few levels to /sourcefiles/Nexcloud/nexcloud but there are no files or folders beyond that. However, there actually are files and sub-folders there and I've verified that not only with Nextcloud, but with the terminal command line. The folder I want to select is: /sourcefiles/Nextcloud/nextcloud/data/username1/files/InstantUpload/Camera Within that folder are all of my recent photos synced using Nextcloud. Why can't DirSyncPro see these folders anymore? I double checked all of my docker settings but can not figure out what needs to change as it had been working fine for months if not years.

Leave it to me to finally ask about an issue just after it has been resolved. That's great! But this has been an issue for a while for me. So either this is just a coincidence or I'm referring to another issue...

I have a question about what keeps happening whenever a new version of the docker is published. Every few weeks I'll check in on the docker and notice that it is eating up 50-60GB of space! For what it's worth, the space is taken up by files in this folder: (\appdata\CrashPlanPRO\conf\tmp) Whenever this happens, I check to see if there are updates to CrashPlan docker and 100% of the time there is. And if I pull up the CrashPlan WebUI I see some sort of error saying the app couldn't be updated. So I update the docker and it resolves the issue (tmp files are deleted). But sometimes (before I fix this docker) this causes issues because it uses up so much space on my cache drive that Plex and other dockers start failing. I'm wondering if this is expected behavior, or do I have something on CrashPlan misconfigured. Or, as a last resort, can I sign up to be notified when new CrashPlan updates are pushed. I realize that the issue may actually reside in CrashPlan servers demanding use of the new version, and isn't directly tied to the actual docker being updated.

Thank you so much, I found the culprit! And thanks to everyone else as well, I really appreciate it. The files that were taking up space were in my Deleted Files bin in Nextcloud! Roughly 26GB of deleted files. Nextcloud is relatively new to me so I didn't know it was keeping my files like that. I need to look for a setting that auto-deletes after 30 days, but otherwise I'll have to remember to empty my recycling bin. 😜

I cannot reconcile a few of these numbers. What I don't know is if this is normal or not. Here are some stats: Cache drive 1 size: 128GB Cache drive 2 size: 240GB filesystem: btrfs reported "size" on Main screen: 184GB what is this about? Shouldn't it just be 128GB? as per below: 98+29.5= ~128GB reported "used" on Main screen: 98GB reported "free" on Main screen: 29.5GB reported utilization for drive 1 in the popup system warnings: 97% how is this calculated? 98/128 = 76% or 98/184 = 53%, neither of which are close to 97% What if I told all of my shares to NOT use the cache drives, then invoked mover? Would that clear them out and would doing that be helpful in diagnosing the situation? Just to confirm my earlier calculations, I browsed to the "cache" network drive, used Windows Explorer to calculate the size of everything in the folder and the total was 55.6GB.

Here is the Diagnostics. tower-diagnostics-20210718-0827.zip

@Squid I wonder if your advice in this thread also applies to me: I am using btrfs with mismatched drives sizes (128GB and 240GB). I still haven't confirmed which raid type I am using (can't figure out how to check, but I most likely used the default RAID1). But UnRAID is reporting 30GB free and I can only find ~63GB of files on the cache drives. Is it possible that my cache storage space is only ~93GB?

Indeed, results show the only share using the cache currently is the appdata. Using Windows Explorer to calculate the size of each folder adds up to 63GB. But that is still quite a bit lower than the 96GB used being reported by Unraid. Still trying to figure out how to account for the difference. I believe I'm using RAID1, but I'm trying to confirm that... Forgot to mention, using Unraid 6.9.2

My cache pool is reporting 83% utilization out of (96GB used, 30GB free). I can't figure out what is taking up so much space. It's possible that Plex's appdata folder is simply using up all the space, but I've tried to find the folder(s) that use that much space and I can't find it. The way I have my shares setup is like this: appdata: prefer cache several data shares like photos, music, etc.: Yes Cache other shares: No When I browse my cache files I see the appdata folder (as expected) and the docker.img file (10GB). I occasionally see files from the other data shares (music, photos, etc.) but those get moved off and if I invoke mover they move right away. So everything seems to be working correctly, but why is my appdata folder reporting so much usage? I have 4 dockers that utilize the appdata folder: CrashPlanPro dirsyncpro nextcloudpi plex The first few don't use much space. I've looked for the biggest folders within Plex and the best I can come up with is about 50GB of usage. Is there something I can do to ensure my disk utilization is being reported accurately?

I've been using this Docker for a few months now and I am really happy with it's stability (and the features of Nextcloud). I have a question about updating Nextcloud. Should I be able to use NCP to update from version 20.x to version 21.x of Nextcloud? In NCP, I have it checked to "Automatically apply Nextcloud updates". And the System Info page says I am currently running Nextcloud version 20.0.8.1 (and NCP v1.36.3). I'm not too familiar with Nextcloud yet but when I check their website it says the current stable version is 21.0.2.

Nextcloud has stopped running for me and I'm still trying to understand why. The last log entry was a warning: This was a couple days ago and it might have been the day that I enable auto-updates in the NCP Maintenance interface. Just prior to that event are a lot of other System log entries in the same minute or 1 minute prior (10:56 to 10:57). I don't know what the entries refer to but a lot seems to have happened in those last 2 minutes. But I can't log into any Nextcloud interface to try and fix things, restarting the Docker doesn't help. I don't mind reinstalling the docker, but I'm trying to understand what went wrong. edit: I think I might know what happened, but I can't be sure because I went ahead and reinstalled the docker already. Every once in a while my Unraid server will switch IP addresses from 192.168.68.XXX to another XXX. I'm not sure why this happens, it usually doesn't affect anything except my bookmark for my Plex interface, but I guess this could become a real issue for this app so I'll have to look into that, but I don't think it is a NPC issue. edit 2: Well, my Unraid server just did it again (changed IP addresses) and yep that seems to be the issue I had previously. Trying to access the app on the new IP address results in an "Access through untrusted domain" error. But after updating the docker settings to the new IP address it works again.

Thanks for the other suggestions. I went ahead and tried out NextCloudPi. Right now I'm very impressed with it's capabilities and performance, but for now I'm not opening it up to being accessible off the network (not the biggest priority for me at this time). There were times during the setup that I wondered if I should be pursuing a more simple solution, but I eventually got it working. I do suggest it for others who are seeking a solution, but I am still in the phase of testing it's stability and reliability. In other words, does it get 100% of my photos or will it miss a couple once in a while? If I end up changing my mind I'll be sure to look further into the other solutions suggested.

Actually I'm not having that issue, but you clued me into where to find them. My datadir is already set to "/data/nextcloud/data", so I was able to use the Unraid Terminal interface to browse to my Camera Upload files! So they are there, but I cannot use Windows Explorer to browse to those files. When I try to open the /data/nextcloud folder, Windows Explorer says that I do not have permission. I'll have to learn more about setting permissions, but if you could tell me if that is fixable or not I'd appreciate it. edit: removing my other comments because after playing around with Nextcloud I am very impressed with it's ability to sync content back and forth from my phone. The web interface is very responsive and downloads are quick. I'm happy for now as I test the stability of the platform. Thanks for your help!

Thanks, I'm following you. Changing the ports to 801 and 4431 worked. I'm basically up and running. I have my phone syncing my photos to the server (my first use case). In configuring Nextcloud, I setup a new, empty Share as the Data folder and the docker threw a bunch of folders/files in there during setup. However, am I wrong to assume that I should be able to find those synced photo files by browsing that Share? I don't see them in any folder.

Well you hit the nail on the head! I never saved the Job File at all! Haha, didn't realize I had to do that. Anyway, at this point I assume that was the issue. I'll come back if it happens again. Thanks.

I'm having an issue where my Job got deleted. At this point I'm assuming the whole docker is getting reset for some reason. Maybe it doesn't have write permission to save the settings/Jobs that I'm creating? Here is what I know: I set up a job a couple months ago, tested it, then enabled a daily Schedule, then I checked a couple days later to ensure the scheduled job was successful. It was successful so I assumed it was safe to leave it be. Now I'm noticing that it stopped working a while ago and the whole Job is gone. Any ideas? Here are the settings I think are important (let me know if you need more): Data Directory: /mnt/cache/appdata/dirsyncpro Source Directory - Read Only: /mnt/user/

I'm having trouble getting this docker to install. Upon Applying the template settings it downloads and extracts the necessary files, and then I get this in the Command section: Upon reading the thread above, I tried changing WebUI setting from "https://[IP]:[PORT:443]/" to "https://192.168.68.114:443/", but that didn't work and I don't think that is necessary, right? Anyway, it seems like it is saying Port 80 is in use? If I look at the Docker allocations it does not show Port 80 being used by my other Dockers (unless 8080 counts for DirSyncPro?). I'm not real familiar with how ports work, but can I just change the ports to whatever I want? I noticed some people above were using 801, 4431, etc.

This looks like it will do the trick, and potentially solve a few other file sync issues I have! It looks like it supports automatic upload. Do you know if I can set it to only upload when charging or other conditions like that? Also, I'm not seeing a price (other than for the Enterprise version) so I'm assuming it is free? I'm happy to pay for software, but not looking to subscribe to a service. Thanks!

Now that the Plex Camera Upload feature is going away, I’m looking for a replacement app to move photos from my Android phone to my Unraid Server. I've looked through Unraid apps in the past, but didn't find anything that stood out to me as definitely having that capability. I’m sure I could implement a multi-step process of uploading to the cloud (something I do not want to do) and then downloading to my server on occasion, but that sounds time consuming and inconvenient. Does anyone have any suggestions for a direct transfer between the two? I suppose the solution would have to include an app for Android and for Unraid. Bonus points if the solution allows me to upload photos from outside the local network.

Well my two highest priority backup sets are uploaded successfully now, but unfortunately my third backup set (which is my largest - movies, etc.) seems to have started over. It says 1TB remaining and estimates 75 days to complete. I need to find a way to actually browse my uploaded files online to see what could possibly be missing from this set. Edit: it is finished backing up now, so it only took another day or two. I didn't get a chance to see which files it was backing up that got lost in the transfer. Who knows, but all is good now. Thanks for your docker Djoss!