[[Support] knex666 - Nextcloud]

On 1/2/2024 at 1:18 AM, knex666 said:

Did you find errors in the log file, can you provide one?

yes the Docker Container manages updates.

 

cheers

 

nextcloud.log

[[Support] knex666 - Nextcloud]

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.

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

On 12/1/2022 at 8:40 PM, Airmaster said:

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 251.43 kB · 0 downloads

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

[Unassigned Devices Preclear - a utility to preclear disks before adding them to the array]

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

[Issues with shutdowns + cache drives]

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.

[Issues with shutdowns + cache drives]

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.

[Only see VLAN interface on VMs, not dockers]

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.

 

 

 

[[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)]

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;
    }
}