faxio

Figured out Rocket.Chat... https://github.com/malko/Rocket.Chat.Docs-1/blob/master/3. Installation/4. Manual Installation/Configuring SSL Reverse Proxy with Nginx.md

This is amazing! had been putting this off for a while. Just finished setting everything up. The only thing I can't get working with Letsencrypt is Rocket Chat. Can anyone get me with this? Is there a proxy-conf template for Rocket Chat? Thanks!

Thank you!!! Why isn't that in the wiki/docs? or is it?

Change the VM's network bridge from virbr0 to br0, or whatever you named your public bridge in unraid's network setup. Hi! I'm having the same issue. However, I only see virbr0, no br0. Can't seem to find anything about how to fix this anywhere. Please help! Thanks!

I was referring to a share on the raid that's set to use the cache drive. I ended up telling my MacOS clients to not write these files to network shares.... https://support.apple.com/en-us/ht1629 This definitely did the trick. Now after I write files to my share, it changes to green after the mover runs at night (or I manually run it). I also had to delete the actual folder (with the name of the share) from the cache drive. It does. My friend has a cache pool setup and all his shares (including appdata) are "protected". I ended up setting up Backup appdata. Everything seems ok now. Other than having some file corruption on a Lightroom library. But that's another story. Just want to thank you guys for the knowledge and help! Much obliged.

OK. So, I just created a test share, set it to use cache: yes, copied 4 PDFs in there, looked at the log and saw that the PDFs were moved properly. However, the orange warning still appeared next to the test share. I then browsed the share's content via the unRAID web GUI and noticed that they were now on Disk1 except for a hidden folder (".AppleDB" which I think MacOS creates). A hidden file: ".DS_Store" was moved with the rest of the PDFs. Is there a way to have the mover move those files/folders as well? Is this a permissions issue?

Sorry, I'm still very confused. What can I do about these shares "not being a valid source" and/or about mover skipping them??? Is mover not working for me? Not sure what I should do at this point. Not sure how CA Backup affects my shares being protected or mover executing properly. Sorry if I'm not understanding. Thanks for your help.

Attached! Thanks guys! unRAID-diagnostics-20160613-2017.zip

If this is the case, my log files show that my appdata share (which is set to Use cache disk: Yes is being skipped by the mover. logger: skipping "appdata" I've read through this. However, things aren't working the way they're supposed to. This is installed and I get " No Warnings Found"

Hello all, I need help trying to solve an issue with a couple of my shares and understanding the Mover function. Sorry if this appears to have been covered several times before but I what I've read in other threads didn't seem to help whatsoever. I have two shares that are reporting this warning: One called "Archive" and the other "appdata". The Archive share was originally created to NOT use cache. However, at one point, it was enabled then later disabled. I read through some of the threads here and tried a few different solutions. First, I tried using the "Move" button which didn't do anything. Tried waiting a few nights to see if it would go away. Then I tried creating a new share and COPYING the files and deleting the old shares to no avail. The new share shows that it's using 0B on the cache drive. The Appdata share is set to use cache but as I understand it, contents are supposed to be moved nightly or by manually evoking the mover with the move button. Is this correct? When I read that, I decided that I would like my Archive share to use cache after all as I keep a photo library on there that I use regularly (Photoshop Lightroom) if it means better throughput. Does it? This is my first unRAID box (built in Jan 2016) 10 Drives including parity + 1 cache drive. v: 6.1.9. Any help that I could get on any of this would be greatly appreciated. Thank you!