geefle

Here they are: nashorn2-diagnostics-20260531-1415.zip

Hi, Yesterday I noticed that warning in my cache pool yesterday. The pool consists of a SATA and an m.2 SSD. The system works normally as far as I can tell. I did a scrub and it did not find an error. I also rebooted the system to install 7.3.1 and the status staid the same (did not expect it to change, but you never now). I am not sure what to do now. Should I replace the drives? Geefle

great thanks I googled the issue and searched the forums but this did not pop up.

Hi, today I updated from 7.1.2 to 7.1.3 and since then I cannot access the internet from the server. I can access the server like normal but when trying to access the internet fro the server, to check for docker updates for example, it does not work. I ruled out DNS and the server can access local network addresses. Just nothing online. I then found that when I turn the Docker service off I can access the internet from the server. I did not make changes to any docker related settings before or after the update. I am not sure what the problem is. Attached are my diagnostics. I hope someone can help me. Cheers, Mav nashorn2-diagnostics-20250607-1824.zip

@frank. I run a backup script that boots the other server using WOL. I wanted to also mount the drives via script but could not find a way to do that. That would be my preferred option the script would mount the drives run the backup dismount the drives and shutdown the server

Hi, I am on Unraid 7.0.1 I have SMB mounts to another machine for backup. To save energy I only turn on that host when the backup job is running. I now noticed that the syslog spams this message every 10 seconds or so. Apr 9 19:11:03 <Unraid hostname>key.dns_resolver: <BACKUP hostname>: No address associated with name I figured out that it caused by the SMB shares. So I unmounted the drives. The message still repeats in the syslog. Even when I removed the shares completely the message appears. It only stoops after a reboot. This looks to me like a bug. Did anyone encounter similar behavior? Cheers, Geefle

Thanks I will post my issue in their thread.

Hi, I am on Unraid 7.0.1 I have SMB mounts to another machine for backup. To save energy I only turn on that host when the backup job is running. I now noticed that the syslog spams this message every 10 seconds or so. Apr 9 19:11:03 <Unraid hostname>key.dns_resolver: <BACKUP hostname>: No address associated with name I figured out that it caused by the SMB shares. So I unmounted the drives. The message still repeats in the syslog. Even when I removed the shares completely the message appears. It only stoops after a reboot. This looks to me like a bug. Did anyone encounter similar behavior? Cheers, Geefle

I updated the HA container today and during the removal process of he container Unraid became unresponsive. The GUI would not respond I could not connect via SSH but pinging was possible. I had a similar situation a couple of weeks ago but the system recovered itself after an hour or so. A friend who is a Linux expert says that this a happen when the RAM is maxed out the kernel is trying to recover by killing the process that causes the issue. Today though even after 4 hours the system did not recover so I power-cycled it. I downloaded the diagnostics to try to find out what caused the issue but I am not sure where to start. If someone can give me some pointers that would be great. I attached the diagnostics. nashorn2-diagnostics-20241222-1758.zip

I figured it out. I got myself confused and configured nginx to access vaultwarden using https. whihc obviously is not possible. When I changed that to http it worked.

i have the same problem, I tried to follow @dswede43 guide but I either got an error saying I run a newer version then I am upgrading to or I got a php warning. at one point trying to go back to the start and installing version 24.0.0 the docker container disappeared from unraid. I reinstalled it from the previous apps and now when I try to run the updater command I get the error "could not open input file: /config/www/nextcloud/updater/updater.phar" I am really not sure what I am doing wrong. What can I do to fix this?

I have the same problem, I have vaultewarden running behinf nginx and both are on br0 I still get a bad gateway response. I now enabled custom networks in docker but that did not help either. One thin I noticed is that docker custom network setting is set to Docker custom network type: ipvlan could that be the problem?

Hi, I am relatively new to Unraid and the whole forward proxy config topic confuses me. I have an Unraid server and am running various docker containers (Vaultwarden, Nextcloud, onlyoffice, etc) that need an SSL certificate. I don't want to expose the server to the internet so I created my own CA and client certificate. I also installed nginx to be able to address these services separately with subdomains. I also created an SSL certificate that has all my subdomains in the SAN field. I could not find documentation on how to install them in Unraid so I can use them with the docker containers. I appreciate any help you can provide. Cheers, Mav

I have an Unraid NAS for a couple of months now. I do not want it to be accessible from the outside to minimize the risk of being hacked Among other things I installed Vaultwarden in a docker container and that#s when my problems started vaultwarden needs https, and to enable this you need a reverse proxy. So I installed Nginx and configured it to get a let's encrypt certificate. For that the NAS needs to be visible from outside. I looked into creating my own CA and SSL certificates and ran into one problem after another. I think now I amat a point where I almost figured it out but I hit a wall. So I created a CA and a certificate, that has all my subdomains in the SAN entry. I installed the certificate chain on the Unraid srever and also on my clients so now when I access the Unraid GUI the connection is secure. I also added the certificate to Nginx and configured the connection for vaultwarden to use it. Nginx is running on 192.168.0.84 Vaultwarden on 192.168.0.82:4545 the DNS (using pihole) entry vaultwarden.home points to 192.168.0.84 When I now access the URL https://vaultwarden.home I get the error bad gateway. I have no idea why this is not working. When I access vaultwarden using http://192.168.0.82:4545 I hope someone can help me or point me in the right direction. Cheers, Mav

Thank you for the quick reply. I will look into that. Just out of curiosity: Is that a Linux bug then?