UnKwicks

@Adeon, I have the same issue since 3 month. My setup is completely different beside the PSU. I have a Seasonic FOCUS PX as well (with 550 Watt). Did you already change the PSU and did that help? As MoBo I run a ASRock J5005-ITX with embedded Celeron.

I can not really help you with the RAM but I want to do a build with the GIGABYTE C246M-WU4 as well. Where did you get it from? I am currently not able to find it anywhere.

This did not work. What finally works for me is: chown 1000:0 -R /path/to/mount/point

@Sycotix, Thank you very much for the video. But I got the same Problem running the elasticsearch container @waymon mentioned. Ist there any solution getting elasticsearch work?

did you configure the aliasgroup1 variable?

@d8sychain, I got the same problem. I am on unraid 6.10.3. I tried also to run the container priviledged but nothing helps. Do you have any advicy for us?

If this solution is not working for you anymore when you did an update of unraid OS then open /root/.ssh/known_hosts and remove the old host entry to your sftp server there After that, start over with these two commands from the description above. Then it should work again.

Thanks for those feedbacks. The temp is pretty consistant at 52. But anyway. I check how to get a better airflow to cool them down. But I do not expect to bring the temps lower than 45. Thanks!

Hello I have an array of 5 disks and I am not sure if maybe my drive temperatures are getting too hot. These are my drives: Parity - WDC_WD120EFAX-xxxx (sdf) - active 52 C (disk is hot) [NOK] Disk 1 - WDC_WD120EFAX-xxxx (sde) - active 51 C [OK] Disk 2 - WDC_WD120EMFZ-xxxx - active 52 C (disk is hot) [NOK] Cache - WDC_WDS500G1R0A-xxxx (sdb) - active 46 C [OK] Cache 2 - WDC_WDS500G1R0A-xxxx (sdc) - active 44 C [OK] The WDC_WD120EFAX is designed to operate between 0 and 65 degree celsius. What do you think, May I increase the warning threshold and still be safe? Is it ok to run at an average of about 50 to 55 degrees on the long term? Thanks for your advice

Is it possible to have the Backup not in a .gz or .tar.gz file but just 1:1 copied? Also without the folder with current date. This would save a lot of disk space when backing it up further with duplicati. To let duplicati do the versioning magic I just need a copy of the appdata folder as it is

Hey Thanks! Did the update and the dashboard is working again. Also it fixed that my Dashboard was not able to show CPU load bars. Now this is working as well.

I have a problem that my folders do not appear on the Dashboard. It worked for a short time some weeks ago and then it stopped working. Is there any setting I am missing that disables the folders on the Dashboard? I reinstalled Docker Folders to check if this helps but it did not.

🤨 I am blind. Sorry, got it.

no idea anyone?

Where do I find the command to create the keyfile?

Thanks for that info. No idea where the terminal window was but I rebooted and the messages are gone. Thanks!

Hi I have installed several docker containers. (16 in summary) Now I realized that my syslog is flodded with error messages referencing two of my docker containers ("linuxserver/nextcloud" and "zabbix/zabbix-agent2"). Here a short example: Sep 12 22:55:57 MyServer nginx: 2020/09/12 22:55:57 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/" Sep 12 22:56:00 MyServer nginx: 2020/09/12 22:56:00 [error] 11912#11912: *829201 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local" Sep 12 22:56:02 MyServer nginx: 2020/09/12 22:56:02 [error] 11912#11912: *829210 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local" Sep 12 22:56:10 MyServer nginx: 2020/09/12 22:56:10 [error] 11912#11912: *824237 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/token HTTP/2.0", upstream: "http://unix:/var/tmp/nextcloud.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/nextcloud/" Sep 12 22:56:12 MyServer nginx: 2020/09/12 22:56:12 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/" Sep 12 22:56:13 MyServer nginx: 2020/09/12 22:56:13 [error] 11912#11912: *829249 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local" Sep 12 22:56:14 MyServer nginx: 2020/09/12 22:56:14 [error] 11912#11912: *829260 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local" The mentioned client IP is the IP of my local client. Where do these messages come from and how could I solve this problem? Thanks!

thanks for your reply. I am aware of the go file. My question is more how to safely do it. I tried manually to add the location part to the emhttp-server.conf of nginx but my customization does not even survive a nginx reload. So I need to solve this problem first, how to add this part to the server block of the nginx conf. Next step would then be to keep the change to persist on unraid reboot via go file.

Hi for my Monitoring with zabbix I want to call the stub_status of nginx. I saw that the stub_status module is already installed but no location is set. Therefore I have to add this location to the nginx config. #nginx_status location /nginx_status { stub_status; allow 10.0.0.111; deny all; } Does anyone know a way how to do this safely and persists after reboot? Thanks for any idea