yeahokay

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by yeahokay

  1. Hi Binhex. I've still not quite managed to make this work perfectly. My deluge speeds appear to be hard limited at 1.1 MiB/s. Theoretically, my connection should be able to sustain speed ~10 times this. The connection appears to saturated at this current level. There is next to no deviation from this speed when a well seeded torrent is added. It feels like there is a bandwidth hard limit set somewhere. I tried changing the Global Bandwidth Limits. Interestingly, this does not affect speeds. Setting a limit at less 300 KiB/s and Deluge still pulls data at my 1.1 MiB/s. I've tried changing these settings through with the docker instance stopped updating core.conf (after removing all backups) and then restarting the instance. I've tried changing through the webUI and the thin client connection. Through each attempt Global bandwidth limits don't seem to affect my speeds. I'm at a bit of a loss on what else I can test. There are no red flags in any of the logs. Any suggestions on what else I could look into would be greatly appreciated! Thanks again for you efforts in producing this and providing ongoing support to the community! A rehash of other troubleshooting I've attempted - I've tried to work through each of the items you've identified in Q6 here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Upload rate set to 3/4 of my theoretical max GCM cipher used ItConfig installed. Both enable_incoming_utp and enable_outgoing_utp are disabled. Rate limit overhead disabled. VPN endpoint should be ok - I can use a different (windows based) machine on the same network, connect to the same endpoint, and max out my connection (over wifi) Disk fragmentation not an issue - new disk. Not writing to an array/using unraid Router shouldn't be an issue considering over wifi it's faster and it's a top of the line netgear
  2. Thanks binhex. How I tested: On my desktop (windows), connected to my network via wifi, I compared the torrent speed whilst connected to the same vpn server delugevpn is using. I did this by opening up qbitorrent and without touching the ports, compared the speed for the same torrent file I was using to test speeds in delugevpn. (server was off so I wasn't downloading between them). speedtest.net on my server via lan is ~ 95Mbps, on my desktop over wifi it's ~35Mbps Ubuntu torrent max download speed on my server using delugevpn is currently ~1.2 MiB/s, compared to ~3.0 MiB/s on my desktop (connected via wifi and using the same VPN) I have tested other torrent files as well and they are maxing out at the same speed.
  3. Apologies, user error I'm sure. And I think there are two people asking about ports simultaneously which may be confusing things. This is the port information I used in the generation of my docker container. docker run -d \ --cap-add=NET_ADMIN \ -p 8112:8112 \ -p 8118:8118 \ -p 58846:58846 \ -p 58946:58946 \ With VPN enabled, I'm unable to update deluge to use port 58846 as the incoming port. From your comment, that sounds like normal behavior. I have established port forwarding through my VPN provider (Torguard) for 58846, 58847, 58946. Updating the deluge incoming port through the webui to 58847 shows that the port is active and I'm connectable. However, my speeds are ~10% of my theoretical max. And testing that vpn server on the same network over wifi on my desktop, I get speeds 3 times faster. As my server is connected via ethernet i would expect speeds to be considerably higher. I've tried to work through each of the items you've identified in Q6 here: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Upload rate set to 3/4 of my theoretical max GCM cipher used ItConfig installed. Both enable_incoming_utp and enable_outgoing_utp are disabled. Rate limit overhead disabled. VPN endpoint should be ok - I can use a different (windows based) machine on the same network, connect to the same endpoint, and max out my connection (over wifi) Disk fragmentation not an issue - new disk. Not writing to an array/using unraid Router shouldn't be an issue considering over wifi it's faster and it's a top of the line netgear The only thing I can think of is that there is something wrong with my port config. Again, appreciate your response, and any other ideas would be greatly appreciated!
  4. Thanks for the fast response binhex. I seem unable to use the 58846 port. When I select that as the incoming port (either in the thin client or by manually updated core.cof), the deluge thin client tells me that the active port remains at 58847. When I change the incoming port to 58847, the active port stays at 58847. Could that be something to do with a setting on Torguards end? This is a fresh install so there shouldn't be anything using that port. I've now forwarded the 58847 port with Torguard as well, so the test active port passes however my speeds are still at 10% of my max. Do the OpenVPN/IPtable rules depend on the use of 58846 port? Any other advice to troubleshoot the issue would be greatly appreciated! This is so frustrating because I feel I'm so close!
  5. Firstly, Binhex thank you for all your hard work! I'm attempting to set this up on a fresh install of Ubuntu Server 18.04LTS. I am using Torguard as my VPN provider. I have the latest delugevpn image up and running, connecting successfully to a Torguard server. I can access the WebUI and I have connected to a thin client session with Deluge 2.0.3. I have forwarded the ports for the particular server I'm connecting to in the Torguard client portal, and the correct ports appear to be open when checked on https://www.portcheckers.com/ for that server. In Deluge webui I've changed the incoming port to one of the forwarded ports (58946). The thin client identifies that this is the Active Port. I've installed the itconfig plugin and disabled the options as recommended in the FAQ. I think a port issue still exists. My download speeds are ~10% of my theoretical max and the Deluge thin client identifies a 'port issue' in the bottom right hand corner of the window. Has anyone managed to get this working successfully with Torguard? What am I missing? I've been beating my head against the wall for a couple of days trying to find the solution to this, so any help is appreciated! Logs: Docker settings - https://pastebin.com/gujS2HTQ Supervisord - https://pastebin.com/ptdCphtz Deluge logs - https://pastebin.com/nEH1STcw