Airmaster

nextcloud.log

Nextcloud was stuck in maintenance mode, so I changed the value to false. I am now getting the message : Nextcloud will be updated to version 28.0.1 I thought that the version would be updated as part of the docker. There is an update button, but it doesn't do much. What should I do to get Nextcloud working again? I did remove and re-add the docker, but same message.

I used the docker instead and it worked great. My conclusion is that this plug-in is buggy.

I am trying to pre-clear on unraid 6.11.5 using the plugin (Unassigned Device Preclear 2022.09.02). I keep getting the a post-read verification fail with "Low memory detected". All of them VMs are stopped and I have 128 GB of RAM with 6% utilization. This has happened twice. Any thoughts on what is wrong? server-diagnostics-20221201-2033.zip

Well, I just decided that if it was already moved off, I would take each cache disk and put them on my PC. I "deleted" the partition for each drive, but did not add partition and reformat. I also made the array not auto-start and then added in the new cache drive and formatted it. Odd that it said the old drives were okay, but it said that they had an unknown format. Problem seems to be gone and the computer shuts down properly. I am currently moving stuff back.

I am running unraid 6.8. I am having problems shutting down, and problems with the cache system. Here is the the background: 1. Having problems with two drives of the 4 drive cache pool, occasionally getting remapped sectors, so I decide to replace them. 2. Shut down VMS 3. Set all drives to use cache. Cache files are now on array, cache is pretty much empty. In the middle, realized I forgot to shut down dockers so I did that, but stuff moved anyway. 4. Swapped one of the two SSDs I wanted to replace, started the array. Kept getting that it was finding extents 1. This fills up the syslog file in the other drive that wasn't replaced. I decide to replace that as well. Unraid get stuck on shutdown, last message is "Turning off swap". I wait several hours and this message is still there. 5. Did hard reset, and then array rebuilds after 20 hours. Still getting the "extents" messages, endless. I decide I am going to remove the pool, I try and shut down the array, but it never gets past the unmounting phase. I don't have any terminals open, nor screens. Also, VMs and Dockers still disabled. 6. I decide to open up a terminal and do a powerdown. Same result as before, error turning off swap. One thing I should mention, I have tried to generate a diagostics file before, but it never generates. I don't know if its the browser or not. Can someone provide me with some advice? Could the cache drives be causing the problem? What happens if I remove them all? Can I use that as a way to reset the pool? Maybe I could reformat them on my windows machine.

I am starting to use VLANs and I could use some help. Essentially, the VLANs only appear on the VM config screen, not on the docker one. A colleague of mine has no such issue and both appear on his. I have four LAN ports built onto my motherboard. I am using two of them, eth0 and eth3. eth0 is an access port (not a trunk) and it is what I use to access unraid. I have decided to put the VLANs on eth3. As you can see below, these vlans only appear under VMs, not dockers. I could use some help in identifying why. Again, my colleague sees them on both.

Well, no responses, so I just went into the Ubunto VM, and used ufw: sudo ufw allow 25565 sudo ufw deny out from any to 10.99.3.10 That seems to work. Allows Minecraft in, and blocks access to Unraid.

I did find this thread, but some of the advice makes no sense. Once recommendation was to use a separate subnet and block traffic at the router between them, but my access to Unraid shares are on the connection to the same subnet (10.99.3.x) that the VM is on, and that doesn't pass through the router. It isn't like I can't assign a 3.x address to the router, if I want to be able to bridge it to the VM.

It seems regardless of vibr0 or br2, its not possible to prevent a VM from accessing a Unraid network share, unless you set them all to secure or private. Is this the case?

I would like some advice in securing virtual machines so that they cannot connect to Unraid network shares or my LAN. My configuration PFSense on its own computer, with three NICs, WAN, LAN (10.99.2.X/24) , and Other (10.99.3.X/24) Unraid w/ 4 NICs, one on LAN (10.99.2.10, br0) and one on Other (10.99.3.10, br2), Other is directly connected to the PFSense machine, no switch UBuntu VM, currently on br2 PFSense rules (plan to port forward 25565 to whatever IP the Minecraft server has) Block access from Other to LAN Allow access from Other to All One concern I have is that the VM can access Unraid through 10.99.3.10. Is this an issue? Can you block this access? I don't have SMB installed on UBuntu, and plan to run Minecraft from a non-administrator (I hate calling it that, but UBuntu seems to not really have a root, just a sudo). Another option I have seen is to use vibr0, and I know that it is supposed to deny network access, but allow outgoing WAN. The documentation isn't clear if I can port forward to it so that is supports Minecraft (incoming WAN). Also, what subnet does vibr0 use, 10.99.2.x, or 10.99.3.x. I didn't see where it was configured, just that it was automatically created. Any problems with either solution, vibr0 or br2?

Thanks...I have been waiting, but just got two more errors. I guess I will order a replacment.

Today, I received two message for the same cache drive (see below). I currently have 4 cache drives, I guess is two drives, each with a mirror, all about 240 GB. Anyway, I am thinking I should replace the drive with errors. Do you agree? If so, could I just pull the drive with errors and just replace it, considered its mirrored, or do I need the follow the advice on the wiki? If so, on replacement of the cache drive, do I just hit the mover button after formatting and adding the drive as a cache? Unraid Cache disk SMART health [187]: 17-04-2019 11:37 Warning [ROOKS-SERVER] - reported uncorrect is 4 SanDisk_SDSSDA240G_154996402750 (sdc) Unraid Cache disk SMART health [5]: 17-04-2019 11:37 Warning [ROOKS-SERVER] - retired block count is 2 SanDisk_SDSSDA240G_154996402750 (sdc) Data, RAID1: total=224.44GiB, used=182.72GiB System, RAID1: total=32.00MiB, used=64.00KiB Metadata, RAID1: total=2.00GiB, used=459.52MiB GlobalReserve, single: total=127.00MiB, used=0.00B

I would like some help with understanding my problem. First, I have things "working" but it bothers me that following the video from Spaceinvader didn't quite work. As I mentioned, I followed the instructions. When I point myself to the subdomain, I get the nginx default page. Somehow it isn't seeing the subdomain redirection. I followed some other instructions, and they mentioned that I can create a file in appdate/letsencrypt/nginx/site-confs directory, and I did so with the name nextcloud. I can't seem to get it to properly work using the same method with sonarr, as I get a bad gateway message. So, the questions I have are: 1. Why does it not work with proxy-confs (note that I tried to use port 444, and also the IP in proxy_pass, no difference). 2. What is the secret sauce to get sonarr working the same way as I got nextcloud working, or to properly get it to work in proxy-confs Hopefully this wasn't answered before, as I did search and read quite a few posts. File: appdata/letsencrypt/nginx/site-confs/nextcloud server { listen 443 ssl; server_name nextcloud.domainname.org; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://10.99.2.10:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } File: appdate/letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } }

Well, I moved my bz files from the previous install to the USB licensed drive and then ran it, upgraded back to 6.4, and now it seems like it is running fine.

I popped in my old beta USB drive (switched to another one before I upgraded) and it boots up just fine. I wonder if its a 6.4 thing or something wrong in configuration. Either way, I am currently down, as I don't have a license to start the array and I am not sure what to do with my licensed USB drive...what do I change?

I move the computer to a new case, and I am having problems since it seems to just shut off ethernet and it won't recognize drives. I took out all cards and unplugged, and also rebooted with no dockers enabled in both gui and console mode. In gui mode, it can't load the configuration page, just page not found. I am attaching the diagnostics, maybe someone can help. rooks-server-diagnostics-20180127-1939.zip