Smith007

For SWAG it was enough to change upstream_port to 8080. Path to conf.yml must be changed manually, or I guess we can wait for official update in Unraid App repository...

Mine has stopped working after update. I have in on port 4000, but behind SWAG proxy. After update SWAG reports "502 Bad Gateway" and in error log "connection refused". Seems like this update broke something?

So it actually works like a charm. All you have to do is to list files you want the mover to skip in a text file, and tell the Mover Tuning plugin to use it. In my case seems it was enough to list: /mnt/cache/NEXTCLOUD/nextcloud.log (not sure, but I reckon it is important to use /mnt/cache/* and NOT /mnt/user/*) Seems it solved the problem with triggering secondary storage, but need some more days to confirm.

I will check hopefully tomorrow and report here.

Thanks! This is amazing - even when Unraid is not doing something, there is a plugin for it . I guess this is what i need:

Thanks for your suggestions re which files to keep on cache. More or less these was my picks too. I was hoping to copy them manually to primary ssd storage and then keep them there, by somehow forcing the mover to leave them where they are. Is that possible?

I have my Nextcloud docker on Unraid and it is working just fine. I'm using it mainly as simple Onedrive replacement, so to keep files. I have Nextcloud data on ssd cache as primary storage, and hdd as secondary; with mover running weekly. I have noticed though, that the secondary storegr if often woke up, even if no changes to data files / file structure are made. I think it is because some internal Nextcloud status or log files are on secondary hdd storage (moved there from cache after maximum a week) and Nextcloud client is simply triggering some read of writes to those "status" files, even if no regular data files are added, deleted or changed. If this is true – two questions: Which Next Cloud files / folders should be kept on cache only (not moved to secondary hdd storage) How to keep the above files out of scope of the mover job. I'm hoping that solving the above two points would wake up secondary hdd storage only in case regular data files are accessed by Nextcloud client.

But I didn't put anything in the Fixed IP Address field... anyway, see the below :). Agreed. I'm happy I got it working exactly the way I wanted it. Thanks again!

Previously it was listening in 192.168.1.10 ports 180/1443. Now it listens on 192.168.1.11 ports 80/443, as I wanted it to... How it is not affecting it anyhow? I must be missing something...

Yes but not sure why you considered them obsolete...

I'm not sure what you mean...

User Script / At First Array Start Only - seems like a good idea?

OK, I figured it out... First I needed to add additional 192.168.1.11/24 IP to default br0. Currently I'm doing in using sh commands, but looking for a way to make this change permanent, in a proper Unraid way - asked a question here. Then, in SWAG settings (or any other container) I defined the following port mappings: and voila - I have SWAG listening on 80/443 native ports, on dedicated IP. Easy enough, all works like a charm . Any disadvantages of this solution I should consider?

Primary IP of my Unraid server is 192.168.1.10 (br0 static IP). I'm adding additional IP to br0 using command: ip address add 192.168.1.11/24 dev br0 How can I make this change permanent, so it stays after Unraid reboot? I know how to do it on generic Linux and probably could find some way on Unraid too, but would like to do it in a proper, Unraid supported way...

But this is to set up "internal" docker IP, isn't it? What I'm missing is how to assign additional docker host IPs, and how to steer containers to bind only to particular host IP (from those additional ones). Or am I mixing it all completely? I know, and apologise. I wanted to start new general topic in Docker Containers forum, but there is no way to post there. Please move my questions to whatever place it fit best. Also - many thanks for helping me .