Fraih

Moderators
  • Content Count

    21
  • Joined

  • Last visited

Posts posted by Fraih

  1. 5 hours ago, alexacallmebaka said:

    Did we ever figure out what the issue was here? I am experiencing the same problem.

    Hello, I don't remember I did anything else than changing STRICT_PORT_FORWARD to no, but binhex already said that it shouldn't affect anything. I have ZeroTier as a host and qBittorrent as a bridge.

  2. Hello @Squid, I am one of the Spanish translators and I have a question regarding this plugin. I understand that the phrase in the Docker tab "Do not overlap with autoupdate" means that the frequency shouldn't overlap with the Plugin update check frequency. Am I wrong? Thanks!

     

    Edit: Also, to have it perfectly translated you should include in the file the words Disabled and Custom (to match the gender correctly), and I don't know why but the different days of the week are not being translated.

  3. 8 hours ago, Gonzalo said:

    Hola, añadi un disco al array para hacer unas pruebas, cuando lo he eliminado me dice no instalado, pero no se si tengo que hacer un Parity check para que se elimine el error.

     

    Gracias.

    Antes de nada, si quieres guarda una captura de pantalla para saber exáctamente como tienes configurado el array (la posición de cada disco). Luego, como ha dicho @chris1bass, tienes que ir a Herramientas > Nueva configuración y seleccionar todos los discos que quieres mantener en "Conservar las asignaciones actuales" antes de dar a Aplicar. Tras esto asegurate de que todos los discos sigan en su posición correcta en el panel Principal e inicia el array (se iniciará la reconstrucción de la paridad).

    • Thanks 1
  4. On 10/17/2019 at 3:12 PM, Hoopster said:

    Crucial says this is normal and there will be no firmware fix.  I actually read the Crucial statement on this.  They say this is normal in SSDs.  No other SSD on the planet has this issue (including other Crucial models), but, somehow it is "normal" on the MX500.

     

     

    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...

  5. On 6/19/2019 at 5:14 AM, fluisterben said:

    You could try and install a debian minimal VM, then install ZeroTier on that. For me that works, I can remotely access router, and all that resides in the same LAN, from the zerotier instance on that VM, as long as I have it allow access to and from ZeroTier on the VM's firewall..

    Okay, so it is not possible to do that with the docker from this post, right? I might try what you say.

  6. 10 hours ago, binhex said:

    I hate to say this but that is highly unlikely to be the cause of your issue, all that flag does is runs a small bit of code to grab an incoming port from PIAs API, that's it, and as you are not using pia it will do nothing and skip it.

     

    Sent from my EML-L29 using Tapatalk

     

     

     

    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...

  7. On 4/18/2019 at 1:58 PM, Fraih said:

    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!

     

    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! :D

  8. 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!

  9. On 4/4/2019 at 10:03 AM, Fraih said:

    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!

     

    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!

  10. 5 hours ago, opticon said:

    I'm currently working on a ZT docker that will allow you to route to internal networks, I'm testing it in bridge mode (container with it's own IP). It's a fork of someone else's which I'll write a config for UnRAID. It's a best effort thing only right now and I'll try to finish it asap.

     

    One thing I discovered while testing my docker, as your internal network clients usually get an DHCP IP Address from your router. Your router actually has no idea about the ZT network. So you'll need to log onto your firewall and create a route to send all ZT network traffic to the IP Address of your docker container. i.e

     

    # Variables

    Internal Network: 192.168.1.0/24

    Internal router: 192.168.1.1

    Container IP: 192.168.1.11

    ZeroTier Network: 172.16.0.0/16

    ZeroTier Container IP: 172.16.12.50

     

    # ZeroTier Managed Route

    Destination: 192.168.0.0/24     (ZT's network)

    Via: 172.16.12.50     (ZT container IP)

    Now click on the Spanner icon for your device in the ZT Web console and click 'Allow Ethernet Bridging'

     

    # Firewall Router rule

    Subnet: 172.16.0.0/16     (ZT Network range)

    Gateway: 192.168.1.11     (ZT Container IP Address)

     

    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!

  11. 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!!!