Marv

Hi, just wondering if someone using this container can tell me how and if you are able to shutdown your server and still be able to wake it up automatically for your recordings? Am I right that this may not be possible using Docker?

Yes it's running behind Ngninx. I did some more research and it seems that there is an overall problem with docker only seeing the IP of the docker0 network. See here for example: https://github.com/jwilder/nginx-proxy/issues/133 https://github.com/docker/docker/issues/7540#issuecomment-250407556 This means that I can't really use the Bruteforce feature shipped with Nextcloud because it's only able to see one IP (172.17.0.1). That's why I disabled it for now in my config.php with 'auth.bruteforce.protection.enabled' => false, How are you dealing with this? Am I the only one seeing this problem here? I also wanted to start playing around with Fail2ban but I think this wouldn't work aswell in a docker environment right? How would I make Fail2ban see the Nextcloud log which is obviously located in a different container.

Ok so I think I found the solution for my problem here: https://blog.bandinelli.net/index.php?post/2016/10/17/Nextcloud%2C-bruteforce-attacks-and-reverse-proxy The problem seems to be that Nextcloud was not properly configured to use as remote address the true remote address and not the address from the reverse proxy But I'm not completely sure if I did everything right. Maybe someone can have a look? I changed the trusted proxies entry and added 'forwarded_for_headers' in my config.php file as follows: 'trusted_domains' => array ( 0 => '192.168.151.10:444', 1 => 'unraid:444', 2 => 'myserver.de', ), 'trusted_proxies' => array ('192.168.151.10'), 'forwarded_for_headers' => array ('HTTP_X_FORWARDED_FOR'), after that I had the problem that on every login to my Nextcloud page (not only the Nginx main site) I got: Warning core Login failed: 'basic auth username' (Remote IP: '172.17.0.1') Info core Bruteforce attempt from "172.17.0.1" detected for action "login". So I also added 'include /config/nginx/proxy.conf;' to my root location in the Nginx cfg: This solved my problem but I don't know if this is the right way to do this because no one else seems to use this line there. # Redirect all traffic to HTTPS server { listen 80; server_name myserver.de www.myserver.de; return 301 https://$server_name$request_uri; } # Redirect all traffic to non-www server { listen 443 ssl; server_name www.myserver.de; return 301 https://myserver.de$request_uri; } # Main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name myserver.de; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_prefer_server_ciphers on; ssl_ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH; # Connection credentials caching ssl_session_cache shared:SSL:10m; ssl_session_timeout 180m; # Disable SSL by enforcing TLS ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # SSL Stapling ssl_stapling on; ssl_stapling_verify on; # Enable HTTP Strict Transport Security applied to all subdomains add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; include /config/nginx/proxy.conf; auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.151.10:444/nextcloud; } }

Hi, I'm using Nextcloud behind Nginx and just recognized that when accessing my main page (e.g. myserver.de) with basic auth I also get a log in the Nextcloud admin settings saying: "Warning core Login failed: 'basic auth username' (Remote IP: '172.17.0.1')" My Nextcloud can be accessed only via myserver.de/nextcloud so I don't really understand why this log entry appears. My Nexxtcloud config.php: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'octl9zzzlzwx', 'passwordsalt' => 'xxxxx', 'secret' => 'xxxxx', 'trusted_domains' => array ( 0 => '192.168.151.10:444', 1 => 'unraid:444', 2 => 'myserver.de', ), 'trusted_proxies' => array ( 0 => '192.168.151.10:443', ), 'overwrite.cli.url' => 'https://192.168.151.10:444', 'overwritehost' => 'myserver.de', 'overwriteprotocol' => 'https', 'overwritewebroot' => '/nextcloud', 'dbtype' => 'mysql', 'version' => '11.0.1.2', 'dbname' => 'Nextcloud', 'dbhost' => '192.168.151.10:3305', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'xxxxx', 'dbpassword' => 'xxxxx', 'logtimezone' => 'UTC', 'installed' => true, 'mail_from_address' => 'xxxxx', 'mail_smtpmode' => 'smtp', 'mail_domain' => 'xxxxx', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpsecure' => 'ssl', 'mail_smtphost' => 'xxxxx', 'mail_smtpport' => 'xxxxx', 'mail_smtpauth' => 1, 'mail_smtpname' => 'xxxxx', 'mail_smtppassword' => 'xxxxx', 'loglevel' => 2, 'maintenance' => false, ); Nginx cfg: # Redirect all traffic to HTTPS server { listen 80; server_name myserver.de www.myserver.de; return 301 https://$server_name$request_uri; } # Redirect all traffic to non-www server { listen 443 ssl; server_name www.myserver.de; return 301 https://myserver.de$request_uri; } # Main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name myserver.de; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_prefer_server_ciphers on; ssl_ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH; # Connection credentials caching ssl_session_cache shared:SSL:10m; ssl_session_timeout 180m; # Disable SSL by enforcing TLS ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # SSL Stapling ssl_stapling on; ssl_stapling_verify on; # Enable HTTP Strict Transport Security applied to all subdomains add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.151.10:444/nextcloud; } } anyone has an idea why this log entry appears? edit: I changed the Nextcloud logging to debug and get the following entries now: Warning core Login failed: 'basic auth username' (Remote IP: '172.17.0.1') Info core Bruteforce attempt from "172.17.0.1" detected for action "login". It seems that my Nextcloud server detects bruteforce when trying to access my Nginx main page. I also noticed that my server responds very slow when logging into Nextcloud and the iOS app reports timeouts aswell when trying to sync.

Thanks a lot. Didn't know about this plugin but it seems to be exactly what I've searched for.

Hi, I'm facing a problem wih two of my Docker containers. Hopefully this plugin can help me out. I have set up my array and all of my containers to autostart after powering on my server (it shuts down at night). Unfortunately some services of my Emby and JDownloader2 containers are not working until I actually restart them one more time manually. For example the Emby container is not able to search for application updates and the auto reconnect function of JDownloader isn't working aswell. I have no idea why this happens. So restarting the containers through the webUI is fixing my issues. My idea with this plugin was it to either use a script that does the 'restarting' for me after each array start or that maybe replaces the unRAID autostart function for the two containers so that they start with a delay or something. Maybe this would solve my problem. As I don't really know how to write such a script. I'd like to kindly ask some of the experts in here to give me a hint or something. Maybe there is also another solution for my problem?

put this in 'custom commands after wakeup' /usr/bin/wget -q -O - localhost/update.htm?cmdSpinupAll=Spin%20Up >/dev/null

Hi, I just migrated from aptalca's nginx-letsencrypt container to the one provided by Linuxserver.io. Everything went fine and I can access my Nextcloud page via https and http just like before. The iPhone App works aswell without any issue again. But my desktop client on my Windows machine reports the following error since switching the container: "Error downloading https://myserver.de/nextcloud/owncloud/status.php - server replied: Not Found" I didn't change anything else but the Nginx container. Does anyone has a solution for this?

Hi, I'm thinking about getting into HDHomeRun using this Docker. Just wondering if it would be possible to use some kind of wakeup script like this right here: https://tvheadend.org/projects/tvheadend/wiki/Wakeup As I can't make changes to the filesystem using TVHeadend in a container. So is this working somehow?

I think I'm experiencing the same issue with the S3 Sleep Plugin. The extra delay after array inactivity is not working as expected. Dec 1 13:01:31 unMARV s3_sleep: command-args=-C 1 -a -c -m 10 -e eth0 -N 0 -b /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/preRun -p /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/postRun -D 2 Dec 1 13:01:31 unMARV s3_sleep: action mode=sleep Dec 1 13:01:31 unMARV s3_sleep: check disks status=yes Dec 1 13:01:31 unMARV s3_sleep: check network activity=no Dec 1 13:01:31 unMARV s3_sleep: check active devices=no Dec 1 13:01:31 unMARV s3_sleep: check local login=no Dec 1 13:01:31 unMARV s3_sleep: check remote login=no Dec 1 13:01:31 unMARV s3_sleep: version=3.0.4 Dec 1 13:01:31 unMARV s3_sleep: ---------------------------------------------- Dec 1 13:01:31 unMARV s3_sleep: included disks=sdb sdc sdd Dec 1 13:01:31 unMARV s3_sleep: excluded disks=sda sde sdf Dec 1 13:01:31 unMARV s3_sleep: ---------------------------------------------- Dec 1 13:01:31 unMARV s3_sleep: s3_sleep process ID 19523 started, To terminate it, type: s3_sleep -q Dec 1 13:01:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:01:31 unMARV s3_sleep: Extra delay period running: 10 minute(s) Dec 1 13:02:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:02:31 unMARV s3_sleep: Extra delay period running: 9 minute(s) Dec 1 13:03:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:03:31 unMARV s3_sleep: Extra delay period running: 8 minute(s) Dec 1 13:04:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:04:31 unMARV s3_sleep: Extra delay period running: 7 minute(s) Dec 1 13:05:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:05:31 unMARV s3_sleep: Extra delay period running: 6 minute(s) Dec 1 13:06:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:06:31 unMARV s3_sleep: Extra delay period running: 5 minute(s) Dec 1 13:07:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:07:31 unMARV s3_sleep: Extra delay period running: 4 minute(s) Dec 1 13:08:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:08:31 unMARV s3_sleep: Extra delay period running: 3 minute(s) Dec 1 13:08:44 unMARV emhttp: Spinning up all drives... Dec 1 13:08:44 unMARV emhttp: shcmd (16150): /usr/sbin/hdparm -S0 /dev/sde &> /dev/null Dec 1 13:08:44 unMARV kernel: mdcmd (56): spinup 0 Dec 1 13:08:44 unMARV kernel: mdcmd (57): spinup 1 Dec 1 13:08:44 unMARV kernel: mdcmd (58): spinup 2 Dec 1 13:09:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:09:31 unMARV s3_sleep: Extra delay period running: 2 minute(s) Dec 1 13:10:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:10:31 unMARV s3_sleep: Extra delay period running: 1 minute(s) Dec 1 13:11:31 unMARV s3_sleep: All monitored HDDs are spun down Dec 1 13:11:31 unMARV s3_sleep: Extra delay period running: 0 minute(s) Dec 1 13:11:31 unMARV s3_sleep: Check TCP/SSH/TTY/IP activity Dec 1 13:11:31 unMARV s3_sleep: Communication state is idle Dec 1 13:11:31 unMARV s3_sleep: Execute custom commands before sleep Dec 1 13:11:31 unMARV s3_sleep: Enter sleep state now even after spinning up all drives the extra delay keeps counting. Does anyone know how to solve this?

I just figured out (at least I think so) what is causing my problem. Besides an 'extra delay after array inactivity' I was also using 'wait for device inactivity' with the ip adress of my LibreELEC vm. It seems that both settings are causing some kind of conflict because when I remove the device inactivity setting the delay option works just fine. Isn't it supposed to use both settings at the same time or is one setting priorized or something?

Hi, I'm using the S3 Sleep Plugin for quiet some time now and always used an 'extra delay after array inactivity' of 30 minutes. Now I noticed that my server goes to sleep already like one minute after my array goes inactive. Did the setting changed somehow from minutes to seconds? Because I didn't change anything in my config regarding this.

I always pipe in on this sort of thing to elaborate. A formatted disk is obviously NOT clear because it has had an empty filesystem written to it. An empty filesystem contains the metadata of the filesystem and a clear disk just has all zeros in every byte. The point of a clear disk is all zeros has no impact on parity. The metadata of an empty filesystem does impact parity, which is why unRAID updates parity when you format a disk you have added to the array. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. If the disk is in the parity array, unRAID treats this write to this array disk just like it does any other write, by updating parity. If you try to add a formatted disk to the parity array unRAID will want to clear it so parity will remain valid. thanks for the explanation. I understand now

Alright, thanks for clarifying

Hi, I was just wondering if the preclear signature gets deleted when formatting a precleared drive using the Unassigned Devices plugin afterwards? So is it safe to preclear a drive, format it with UD and just assign it to the array when needed some day? Or should I just leave it precleared and let unRAID format the drive when adding it to the array?

So with this setting you keep both ports open on your router or just port 80 as the webserver still redirects to 443 (without opening that port on the router)? Or port 443 only? But then this setting would not do anything if I understand this correctly as port 80 is closed anyway I also mapped port 80 from the nginx-letsencrypt container to port 81 on the host because of the unRAID webUI.

No benefit, it's largely down to user preference, yeah I'd be grateful if you posted your config to see what the difference is. Here it is, please feedback what can be better! NgINX docker DHLEVEL = 4096 server { listen 80; server_name server.com web.server.com www.server.com; return 301 https://$server_name$request_uri; #enforce https } server { listen 443 ssl http2 default_server; root /config/www; index index.html index.htm index.php; server_name server.com web.server.com www.server.com ; #add_header Strict-Transport-Security max-age=31536000 always; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; include /config/nginx/proxy.conf; # include /config/nginx/auth.conf; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_protocols TLSv1.2; ssl_ciphers HIGH:!aNULL:!MD5:!3DES:!CAMELLIA:!AES128; ssl_prefer_server_ciphers on; ssl_ecdh_curve secp384r1; ssl_session_cache shared:SSL:10m; ssl_session_tickets on; location / { include /config/nginx/auth.conf; try_files $uri $uri/ /index.html /index.php?$args =404; } location /nzbget/ { include /config/nginx/auth.conf; proxy_pass http://192.168.0.190:6789; } location /sabnzbd/ { include /config/nginx/auth.conf; proxy_pass http://192.168.0.190:8080; } location /nextcloud { proxy_pass https://192.168.0.190:446/nextcloud; } } What's the reason behind this section? server { listen 80; server_name server.com web.server.com www.server.com; return 301 https://$server_name$request_uri; #enforce https } Can you just forward port 80 from your router and keep 443 closed then and still direct all traffic to https?

Read the second post on this thread about best practices. There is an explanation about UD showing the disk temperature. I think in your case this is what is happening. UD is not monitoring your drive so it looks to be spun down. Based on your quick test, the drive is spun up. You need to see what is spinning it up. If UD is showing '*' then it is not monitoring the disk at all. Ok so I added the default script to my disk and now UD aswell shows it as spun up and reports the temperature. Unfortunately I don't use that drive at all and it is empty. So I don't know what keeps it spinning. Is it possibe to add a line to the script somehow that sets a default spin down delay or something? Update: I added '/usr/sbin/hdparm -y /dev/sdf' to the custom commands after wakeup of the S3 Sleep plugin. Seems like the drive stays in standby now.

all WD Reds 4TB each

ok thanks for clarifying. Checked with the commands you posted. Unfortunately the state shows 'active/idle'. This is also shown for array disks when they are in use. 'Standby' is indeed shown for spun down array disks but not for my unassigned device Sorry for my stupidness but I still don't get it

I tried both. Mapping /data to /mnt/disk1/Nextcloud and changing the included/excluded disks aswell but my parity and disk1 still do not spin down when the container is running. I'm using Nextcloud together with Nginex-letsencrypt. Don't know if that's the reason maybe. Are you using it this way aswell? As my guide describes I'm using it with Apache. I was mistaken, apparently I do have it mapped as /mnt/user/nextcloud Do you limit your share to one disk via the share settings then? Will keep /mnt/user/Nextcloud aswell then and try to only include one disk. Is there someone else using it together with Nginex and have the disk mapped to /data spinning all the time? So I made some testing and its only the Nextcloud container that keeps my disks spinning (I removed Nginx temporarily). I also tried including only one disk to the /data share. Is there anything I can do? This issue really drives me crazy because I always let my server go to sleep when the array is inactive. I finally solved it. Modified the logging settings within Nextcloud from everything to only errors etc. Maybe someone else has this problem aswell.

ok, thank you. edit: Are you sure that it is really not spinning? Because when I check out my Preclear Plugin under tools/disk utilities it reports the temperature and marks the drive 'green'.

Can someone clarify this for me please?

I tried both. Mapping /data to /mnt/disk1/Nextcloud and changing the included/excluded disks aswell but my parity and disk1 still do not spin down when the container is running. I'm using Nextcloud together with Nginex-letsencrypt. Don't know if that's the reason maybe. Are you using it this way aswell? As my guide describes I'm using it with Apache. I was mistaken, apparently I do have it mapped as /mnt/user/nextcloud Do you limit your share to one disk via the share settings then? Will keep /mnt/user/Nextcloud aswell then and try to only include one disk. Is there someone else using it together with Nginex and have the disk mapped to /data spinning all the time? So I made some testing and its only the Nextcloud container that keeps my disks spinning (I removed Nginx temporarily). I also tried including only one disk to the /data share. Is there anything I can do? This issue really drives me crazy because I always let my server go to sleep when the array is inactive.

I tried both. Mapping /data to /mnt/disk1/Nextcloud and changing the included/excluded disks aswell but my parity and disk1 still do not spin down when the container is running. I'm using Nextcloud together with Nginex-letsencrypt. Don't know if that's the reason maybe. Are you using it this way aswell? As my guide describes I'm using it with Apache. I was mistaken, apparently I do have it mapped as /mnt/user/nextcloud Do you limit your share to one disk via the share settings then? Will keep /mnt/user/Nextcloud aswell then and try to only include one disk. Is there someone else using it together with Nginex and have the disk mapped to /data spinning all the time?