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?

The system has been running fine for about 4 weeks, and since middle of last week I keep having that effect where the system is not reachable. the last instance was sometime today. When I connected a monitor to the NAS I could see the logon prompt and interact with it. It would tell me when the logon was incorrect. When it was correct (presumeably) nothing happened. Since the issues from March, I have the syslog mirrored to the flash drive. I attached it in addition to the diagnostics. Can anyone see what is going wrong? At the moment this is so unreliable It is unusable. nashorn2-diagnostics-20220605-1408.zip syslog(3).zip

Now that I stopped the pi-hole container, the system has been running without a problem. I wonder if it could be a ram problem

Diagonostics nashorn2-diagnostics-20220314-2123.zip

The server just crashed again. Suddenly all the fans spun up and I could not reach it. This time there was a weird message in sys log at ~17:16 I now turned off the pihole docker container, since this is the only thing I changed today. Still any ideas are welcome. syslog(1)

Hi My server is a couple of weeks old. I am almost done setting everything up and it has been running stable for over two weeks. Suddenly it is not reachable over the network. Plugging in a monitor does not show a picture. Because I experienced this before I mirrored the syslog to flash: Mar 14 11:47:10 host kernel: ret_from_fork+0x1f/0x30 Mar 14 11:47:10 host kernel: ---[ end trace 391c513f82e9a404 ]--- Mar 14 13:52:58 host webGUI: Successful login user root from 192.168.0.206 Mar 14 14:06:55 host emhttpd: spinning down /dev/sdf Mar 14 15:19:54 host emhttpd: read SMART /dev/sdb Mar 14 16:41:53 host kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021 Mar 14 16:41:53 host kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 14 16:41:53 host kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 14 16:41:53 host kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Because today I installed pihole, I can pinpoint the time it stopped working pretty well around 16:30. The Syslog does not seem to contain any info that is helpful. Does anyone have any idea how I can have more info in the logs?

Hi, I am using unraid for a little over a month now. and finally my setup is almost done. I now created a couple of users and granted them access to shares. Now I wanted to map network drives in Windows(11) with one of those users. Windows keeps saying the password is incorrect. I triple checked and reset the password twice now always copying it from my password manager. I then tried to login to the Unraid GUI just in case it's a windows problem. There I also get an error that the password is incorrect. Any ideas what I am doing wrong? Cheers

Thanks for the quick reply. Sounds good. Still can you tell me where in the logs I can see that?

Hi, every time I boot I get MCE Erros reported from the fix common problems plugin. I then installed the Nerd plugin as suggested but I cannot find the location of the MCE log. Just to makes ure I posted my diagnostics. I appreciate any help. nashorn2-diagnostics-20220224-1744.zip

Danke, hab zwar etwas gebraucht um die ewreiterte Ansicht zu finden aber jetzt weiss ich was Du meinst.

Hallo, ich bin auch in dieses Problem gelaufen, bin ganz neu auf unRaid und bin noch sehr unerfahren. Wie kann ich den Parameter im MariaDB container angeben?