makkish

My use case for this is that uptime kuma connects to proxy server (installed as a container on Debian, not Unraid) through a VPN tunnel so the traffic is filtered through a firewall. The firewall rules are however the same, no change there. I tried a restart and recreation of the continer, no difference. A couple of minutes ago I did a restore of the VM that runs proxy server and all started working again, this points to some change after the latest version, in my use case at least. I will dig some more and see if I can find something else.

Hi, I am using http with user/pw as envs (HTTP_PROXY_USER/HTTP_PROXY_PWD)

Hello! After updating to latest proxy-server I keep seeing this in logs, WARNING Access denied: access denied: destination address 10.0.41.11 is not allowed by filter prefix 10.0.0.0/8 I can't seem to find where to allow specific networks/hosts. Anyone with and idea?

Hello, I am seeing this problem as well when I am on 6.11.5, on one of my two unraids. If I go back to 6.10.3 the problem disappears and everything works fine. I have had this problem on all 6.11.X and I always had to roll back to 6.10.3. When the problem arises, around 4 AM, all docker and VMs are missing on the dashboard. The server kind of works, but not completely. I can't even download Diagnostics, it's just stuck on collecting logs. I also see the following in the logs which match the time pretty good, Dec 1 03:46:31 unraid01 kernel: traps: lsof[20478] general protection fault ip:14710dae84ee sp:c1321d13210db561 error:0 in libc-2.36.so[14710dad0000+16b000] Dec 1 03:59:20 unraid01 kernel: traps: lsof[12947] general protection fault ip:151c2d9224ee sp:75ab240d9cab0f3c error:0 in libc-2.36.so[151c2d90a000+16b000] Dec 1 04:16:12 unraid01 kernel: traps: lsof[24904] general protection fault ip:14af0616b4ee sp:965b46bd90838f67 error:0 in libc-2.36.so[14af06153000+16b000] Dec 1 04:31:44 unraid01 kernel: traps: lsof[26965] general protection fault ip:14b5a75c44ee sp:4050197e3a84082e error:0 in libc-2.36.so[14b5a75ac000+16b000] Dec 1 04:32:13 unraid01 kernel: traps: lsof[29523] general protection fault ip:153d668114ee sp:2b9458963a4a01db error:0 in libc-2.36.so[153d667f9000+16b000]

I resolved it by removing dynamix.ssd.trim from /boot/config/plugins. After the deletion I could install it again. I guest it became inactive somewhat when upgrading to 6.11 and after a downgrade it could not install since there was a file in the plugins folder. Ping @kaiguy @jlficken

Hello! Did we ever find a solution for this? I am experiencing the same error.

I encountered the same error when I tried to purge an old worker. I got the following suggestion from Guy in the Discord channel, which resolved it: 1) Stop Machinaris container in Unraid Admin UI 2) Delete only this file: /mnt/user/appdata/machinaris/machinaris/dbs/machinaris.db 3) Start Machinaris container in Unraid Admin UI 4) Wait about ~3-5 minutes for everything to start and get re-populated. Then try clicking around in Machinaris WebUI.

Hi, Well, now I feel a bit stupid. Of course I had it in the configuration, I did not think of what it meant when I installed it the first time. I removed everything with MQTT/HomeAssistant and the queries stopped. Thank you!

Hello, First of all, thanks for a great plugin that opens many doors. One question, I can see in the pihole logs that as soon as I start the container it starts querying hassio every second. Why is that?

Yes, I have added the disk as a 2nd vDisk location It has nothing to do with UD then I guess. Thanks for the clarification. I just figured out another issue, despite the warnings of CRC errors, SMART appear as healthy on the dashboard: I guess I should continue my issues in another forum instead, since this seem to have nothing to do with UD.

Hello! I am not completely sure that this is a UD problem, but i'll start here. I have a SSD mounted as a UD, this is then passed through to a VM. Everything works fine but the SSD is giving me CRC errors (SMART attribute 199), and this is fine. It's not critical and I am planning to replace it at a later time. However, I have toggled notifications off for just attribute 199 but it does not "take". I still get notifications, /boot/config/smart-one.cfg [KINGSTON_SA400S37960G_XXXXXX] smEvents="5|187|197|198" Device settings I am on Unraid 6.9.1 and UD 2021.03.20. Have any one else encountered this? Like I said, I am not sure if this is a UD or Unraid issue. Thanks!

Thank you for the suggestion. It gave me the option to open a link that way, It did however not help for me neither.

Hello, First of all, thank you very much for your work in this. I do have some problems with the icons, for some reason they are not images that I can right click. I can see the "broken icons" but I have no option to open the link in a new tab when I right click. This happens on different browsers. The API connection works fine in general, I still get the data as expected.

Hello, I can confirm that my scheduled parity check did not pause either. I changed the settings and then back, the .cron look correct but it did not pause anyway. It did however pause correctly if I set "Use increments for Unscheduled Parity Check" to Yes. Edit: I'm on Unraid 6.8.3 and Parity Check Tuning 2020.05.11

The plugin does not seem to honor the tuning schedule. I have my parity check to pause at 4:30AM, but when I woke up today the parity check was still running. I can see the following in the log at the time it was supposed to pause, 2021-01-02 04:30:01 5 unraid01 CROND exit status 126 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Edit: 4:30AM not PM.