mashuto

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by mashuto

  1. Hah, Thank you so much! I was banging my head against this for so long and that just worked right away. I was under the impression that it was supposed to be for my gateway/router, which is 192.168.1.1, and I also figured since it seemed to work fine in docker for windows that it was correct. Anyways, much appreciated, thanks!
  2. Well, I'm back. I could not figure out why I was getting such slow speeds. I tried a number of things but just couldnt get any of my torrents running at an acceptable speed. Most of the time they seemed to hover around 15-20kB/s. So, I decided to go back and try a docker toolbox (instead of docker for windows) configuration again to see if I could at least get back to the speeds I was expecting and speeds that are acceptable. However, no matter what I do, I cannot access the webui of deluge. As far as I can tell everything is configured correctly. I am even using the exact same run command I was using and had no problems with on the docker for windows version. I cannot get the webui from local host, I cannot access it from the docker machine ip 192.168.99.100:8112. I added a third bridged adapter to the docker machine vm to get it on my regular subnet, cant access the webui from there either. I used kitematic to install the non vpn deluge container and I had no trouble accessing the webui there. Really could use some help and hope I didnt just miss something obvious. I set it to debug again and took another supervisord.log file, and am attaching my run command. docker run command.txt supervisord.log
  3. Its much appreciated, but I am just not sure any of these apply to me. For the incoming port, I am using PIA, I have strict port forward enabled, and am using NL as my endpoint. My upload speed is set to 2500kB/s which my internet should be able to handle just fine, but just like download speeds, I have yet to see uploads go over 200 or 300 kB/s total. Rate limit overhead is not enabled (left at default from the container). I am using NL as my endpoint which should have decent enough bandwidth, especially because its the same endpoint I was using before when I used to get better speeds. And I do not believe the disk is badly fragmented, but I will defragment it just in case, though I cant imagine it would slow me down to less than 10% of the speeds I used to get. Since it appears as though I have the container set up right, I am wondering if it actually is the container or if its something related to using docker for windows over the older docker toolbox. I tried to go back to docker toolbox to test, but it is such an amazing pain to try access docker toolbox containers on the local network when running it on windows since it defaults the machines to a different subnet (and cant access on localhost either).
  4. I appreciate it, but doesn't seem to have done anything. Individual torrents are still only running at like 20-30 kB/s even with a decent number of peers connected (close to 100). Incidentally, I can't seem to get rid of the ltconfig menu item even though I have removed the plugin... I am really not sure if this is related to the container itself or has something to do with docker for windows, but it really is very slow for me right now and I can't figure out why.
  5. Hello there, I just wanted to first say thanks for this excellent container. I was running a full ubuntu vm for this before and couldn't figure out how to get a kill switch up and running for the vpn and this is just much simpler... well, outside the issues I had getting docker to run on windows server 2016. So, I see there has been some discussion recently about slow speeds. I wanted to chime in and say I am experiencing the same. I was using an older version of the container (dont remember the exact version) that I know hadn't been updated in a while and I was using it via docker toolbox. But there was some weird configuration stuff and actually acessing a docker toolbox container on my network was a real pain. So I saw that docker for windows was finally available for win server 2016 and I switched. Overall much happier, other than the slow speeds. With the old container on docker toolbox I could often max out my downloads at 2-3MB/s, but with this new one I dont think I have seen higher than 350KB/s. My internet connection is 75mb/s so the download speeds seem really low. I have messed with the bandwidth settings and as per recent discussions, I have confirmed that rate limit ip overhead is not and has not been checked. I am also using pia and am pretty much using default settings (at least the example settings from the github or docker pull page). As per instructions, I enabled debug mode, restarted and let it run for a few minutes and am attaching my supervisord.log file with user and password x'd out. supervisord.log