Jump to content

Fraih

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fraih

  • Rank
    Member
  1. I just got a SSD Crucial MX500 and is hotter than my other disks (idles at 45C). If I increase the global temperature threshold my other HDD in UD will not report warnings when they should. Is the individual atributes/warnings in the roadmap for future plugin releases? Thank you!
  2. Yeah, but I wanted to avoid disabling that attribute on my unnasigned mechanical disks
  3. It's a shame... But as long as the SSD works as expected I guess it's not too bad. It would be nice to be able to desactivate the attribute 197 having the disk as unnasigned device, hopefully the plugin will be updated with that feature some day...
  4. Any news about this? My MX500 is arriving in a couple of days and I know I will have this problem, but it was a good deal and the performance is close to the Samsung drives. Any script to turn off the warnings as unnasigned device (keeping the monitoring of other unnasigned devices on). Thanks!
  5. Happy Birthday!!!! Please let me know if I get the badge!
  6. Okay, so it is not possible to do that with the docker from this post, right? I might try what you say.
  7. Until yesterday I had never been able to reach qBittorrent GUI through ZeroTier. Maybe I did something else, but I will switch it back to "yes" later when I get home and I will try again to see if the problem comes back by only changing that...
  8. Okay I fixed it, I had everything correctly configured in ZeroTier, but I am using NordVPN and this provider doesn't allow port forwarding. In the qBittorrent docker I had the variable "STRICT_PORT_FORWARD = yes" and that was messing up everything, I turned it off and now I can access perfectly with ZeroTier from outside my LAN!
  9. Hello, yesterday I found out a confict between ZeroTier and qBittorent, I can't access the webUI of the binhex-qbittorrent docker while I am connected to ZeroTier from outside my LAN (the connection just times out). I can access any other docker's webUI just fine with this configuration, but it doesn't work for qBittorrent (same unRaid ip, and port 8080). Could it be because the qBittorrent docker is running with the Privoxy instance activated? Although most of my other dockers are pointing to Privoxy via proxy config (Sonarr, Radarr...) and I don't have any problem accessing them. Any idea of how could I fix this? Thanks!
  10. I still haven't figured out my problem despite changing a bunch of stuff in my router. But yesterday I found out another problem, I can't access the webUI of the docker qBittorrent from Binhex when I am connected to ZeroTier from outside my LAN. I can access any other docker's webUI just fine, but it doesn't work for qBittorrent (same unRaid ip, and port 8080). Could it be because the qBittorrent docker is running with the Privoxy instance activated? Although most of my other dockers are pointing to Privoxy via proxy config (Sonarr, Radarr...) and I don't have any problem accessing them. Any idea of how could I fix this? Thanks!
  11. Hey opticon, thanks you for your answer. So if I understood correctly, connecting to my router is not possible through the docker of this thread, and all those variables and routes you posted are for the docker you are working on, right? Another thing I didn't get is, when you talk about my firewall, do you mean the firewall configuration of my ISP router? Is my router able to see the docker subnet 172.16.0.0/16? Thanks again!
  12. Hello, I spent a bunch of hours trying to figure out something. I installed the ZeroTier docker, configured it and I can access my unraid server and its dockers perfectly, but I can't access my router. My configuration is as follows: Physical LAN net is 192.168.1.0/24 (being my router: 192.168.1.1 and my unraid server: 192.168.1.2). The ZeroTier net is 192.168.2.0/24 (being my unraid server: 192.168.2.2 and my outside-LAN laptop [Windows 10 client]: 192.168.2.55) I have the following managed routes in ZeroTier and I can access to the unraid server from my outside-LAN laptop with through IP's: 192.168.1.2 and 192.168.2.2, so that seems fine: 192.168.1.0/24 via 192.168.2.2 192.168.2.0/24 (LAN) The problem is that from my laptop I am unable to reach my router (192.168.1.1). I can ping the router from the docker terminal, but I cannot connect to it from the ZeroTier client side. Am I missing something during the configuration process? I believe that this ZeroTier docker should allow me to connect remotely to my router, am I wrong? Thanks!!!