Greyberry

it has everything to do with http and https, because (A) i have the proper rules in place: location ^~ /.well-known { # The rules in this block are an adaptation of the rules # in `.htaccess` that concern `/.well-known`. location = /.well-known/carddav { return 301 /remote.php/dav/; } location = /.well-known/caldav { return 301 /remote.php/dav/; } location /.well-known/acme-challenge { try_files $uri $uri/ =404; } location /.well-known/pki-validation { try_files $uri $uri/ =404; } # Let Nextcloud's API for `/.well-known` URIs handle all other # requests by passing them to the front-end controller. return 301 /index.php$request_uri; } and (B) the warnings do not occur, when i use https behind the reverse proxy.

I am using the linuxserver.io nextcloud container behind a reverse proxy using NginxProxyManager. to reduce overhead i wanted to use the http connection behind the reverse proxy instead of the https connection (is on the same machine, does not really matter.) but whenever i use the http connection i get this warning in the settings overview: I investigated the ./nginx/site-confs/default.conf configuration of this container, but i dont see there being made a difference between http and https, so ... what gives?

Ich hatte es leider auch zu spät gemerkt, aber die Karte kommt mit einer NEUEREN firmware als die hier angeboten. Habe jetzt auch die ältere Firmware drauf. 🤦‍♂️

Ich habe genau die selbe Karte gekauft. Gibt es hierzu einen (kurzen) Guide wie man die Firmware updaten kann?

I did not realise that the backup "only" contains the appdata folder. I thought there would be settings files and such. I had the appdata still in place and could install the containers with "previous apps" without the need for a backup, thanks! 🙂

Ouch! I got the appdata in place. Is there a way to restore my templates/countainers as they were from the backup?

Ok with 6.11.5 i run into the mover bug that is not moving symlinks. It is already known and described here: This SHOULD be solved in 6.12 but is not for me apparently.

I reverted to 6.11.5. The mover is working now, but i get a lot of warnings in the ssh session: Specified filename [path_to_file] does not exist.

Hi, I am in the process of upgrading my single cache drive (xfs) to a newer cache setup, and therefore i wanted to offload all data to my main array. Unfortuantelly this process can't be finished because the mover is not able to move files any more and always stops after some files. (System is running in safe mode already, docker and vm manager is turned off in settings) Starting the Mover root@SERVER:~# mover start mover: started file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo 2nd attempt after "mover stop" in a 2nd window: root@SERVER:~# mover start mover: started file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/run file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/supervise/lock file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/supervise/control I am on version 6.12.3 is there anything i can do to complete the process? Also note, that a lot of the data did move, but the docker folder remains unmoved. server-diagnostics-20230816-2254.zip

Thank you! 🙂 Now I know. Sometimes it is faster to do it via terminal or look into the diagnostics when you have that opened anyway.

You couldn't do that on my machine, could you? I wanted to know how you knew FROM THE LOGS the errors were from disk1. yeah disk1 (data-disk) is corrupt, so I think it is better to rebuild the data from parity.

You saw the ATA errors in the syslog. What i wanted to know is, how do you know that these are related to disk1? (and not parity disk?) Apr 3 19:21:28 SERVER kernel: ata3.00: failed command: READ FPDMA QUEUED Apr 3 19:21:28 SERVER kernel: ata3.00: cmd 60/28:58:10:12:1e/02:00:e3:00:00/40 tag 11 ncq dma 282624 in Apr 3 19:21:28 SERVER kernel: res 40/00:60:38:14:1e/00:00:e3:00:00/40 Emask 0x10 (ATA bus error) Apr 3 19:21:28 SERVER kernel: ata3.00: status: { DRDY } Apr 3 19:21:28 SERVER kernel: ata3.00: failed command: READ FPDMA QUEUED Apr 3 19:21:28 SERVER kernel: ata3.00: cmd 60/d0:60:38:14:1e/02:00:e3:00:00/40 tag 12 ncq dma 368640 in Apr 3 19:21:28 SERVER kernel: res 40/00:60:38:14:1e/00:00:e3:00:00/40 Emask 0x10 (ATA bus error) Apr 3 19:21:28 SERVER kernel: ata3.00: status: { DRDY } Apr 3 19:21:28 SERVER kernel: ata3: hard resetting link Apr 3 19:21:29 SERVER kernel: ata3: SATA link down (SStatus 0 SControl 300) Apr 3 19:21:34 SERVER kernel: ata3: hard resetting link Apr 3 19:21:39 SERVER kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 3 19:21:42 SERVER kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 3 19:21:42 SERVER kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out Apr 3 19:21:42 SERVER kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Apr 3 19:21:42 SERVER kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out Apr 3 19:21:42 SERVER kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Yes I know. But: Doesn't it make more sense to do a DISK-REBUILD (parity --> data) instead of a correcting parity-check? (data --> parity) Because in this case it is more likely that the data is corrupt and the parity is in tact.

Thank you for your reply. I also see them in the syslog, but how do I know that this is in fact disk1? (Not that I don't belive you, but so that i can debug it for myself in the future.) If disk1 (data-disk) is the problem, wouldn't it be better to remove disk1 from the array and start a new sync/repair process from parity once the issues are resolved? instead of doing a correcting parity check, which would write the corrupt data from the data-disk to parity.?

Hi. I had a failing drive a view days ago. 24 errors on the write collumn indicates that the disk went offline immediatly, so it had not a lot of time to corrupt the data fortunatelly. After seeing this i swaped the disk with a new one and rebuilt the data from parity. Note that i did use the array while this process was going on. There were no errors or what so ever in the syncing process, so i thought I am good but out of curiosity initiated a parity check. The parity check finished today, and throw 1024 errors. Now I don't know if the corrupt data is on my freshly inserted disk, or on the parity disk. What should I do now? Since I am using only two drives in the array (one data, one parity) it is therotically possible to see which files are effected. How can I see, which ones? server-diagnostics-20230404-1254.zip

How can I run a script when a certain peer connects / disconnects? I want to add a route to its LAN, but can't use the option "LAN <---> LAN" because it has no certain endpoint. i get the intention of an endpoing beeing mendatory in the GUI, but it should not be necessary as long as one peer can connect to another.

Hi volks, Is there a way to make a port of a server-socket of a docker container only available for another docker container? I have an application behind my reverse proxy, and do not want it to be exposed to my LAN, but only to the reverse proxy, which is also running on the same unraid-machine. I guess it involves a separate docker-network and fixed ips within it for the docker containers. Can we do this on unraid? Or is there an even easyer solution I do not think of? happy holidays

This would be a welcome addition and quality of life improvement. Would be cool if it could avoid portnumbers that are already taken by another docker-application.

My Unraidserver unfortunately has only 8GB of RAM not upgradeable and is always on 90+ usage. Half of it is gets eaten up by tmpfs (or /dev/shm) which is barely used if at all. So i wanted to reduce its size. How can I do that?

I want to have that back, too! Happy if someone has the answer to this question.

Hello, Sometimes when I have to do some maintenance on the server or a certain docker-service, it would be useful to see if there are any connections currently using the shares or docker-container. I do not want to interrupt someones work. Is there any way to do this? netstat or something? regards

Could you go into more detail on how you did it? I still can not get it to work. What do you mean with labels? Don't the containers show up automatically? I thought that is what its for?

regarding the Chromium docker-image: is there a way to use its webdriver like described here: https://github.com/dgtlmoon/changedetection.io/wiki/Fetching-pages-with-WebDriver ?

Best dashboard I used so far. How do i use the "docker API" feature with unraid? when i place my unraid IP in, the applications do not load. Do i have to enable the docker API somewhere in Unraid?

Is there a way to run a win installation on this, without fiddeling with extra comments in winPE?

confirmed. 🙂 working again. Thanks!