![]() ![]() Later versions of libtorrent tries to mitigate this to some degree by caching DNS lookups and, when shutting down, using the cached responses rather than risking the OS cache has expired requiring a new online lookup. If you have connectivity issues to your DNS server, or have lots of names that are not in any close DNS caches, it may take a long time to perform the lookups. in this quote from lead-dev Arvid:ĭNS lookups are synchronous (although done on a separate thread). Sometimes even when restarting you get the same IP many times in row and other times not - which was a problem for me back in the day at a couple times, where one or two IPs went down from the ones in the DNS list.ĭeluge doesn't do anything, and it's libtorrent-rasterbar that control this, and it seems it does some caching in later libtorrents sometimes, e.g. Anyway, your best bet is imho to do as you do, and drop the url and select a good IP, that stays up and has good speeds. my provider rewrote there server-software because got overloaded often because of it. udp trackers etc, where libtorrent sometimes can be finnicky and as with port-forwarding you will theoretically get faster speed, because of better connectability/sharability/unchokability lol in smaller not so popular swarms.Īnyway, most everybody uses dante socks5 server as backend, and that have generally known to having some performance problems with udp/uTP, e.g. Btw, as torguard proxy includes VPN if i'm not mistaken, and even includes port-forwarding, then might be something to think about changing to a deluge with openvpn docker, which in my experience works better sometimes with e.g. Sorry no solution or real help to offer, and just wanted to say I have seen that too, a couple of years ago before changing to VPN, but with deluge 1.3.15 or so. If you have a new theory or any solutions please let me know. I don't see anything in the logs about attempting to connect to the proxy or any other IP. I tried changing the container logging to debug or info but I only get the same startup information and web requests the webui + browser are generating. This is complete conjecture but I'm wondering if deluge has a few errors connecting to the proxy server and then just does something similar to an IP ban and stops trying to connect until I change the value. In the proxy configuration in the webui I have everything selected proxy hostname,peers,trackers. I used to have the same issue with the same proxy servers on Utorrent on windows but a simple restart of the client fixed it. Often that stops working and I try to try various IPs on their list until it starts working. ![]() I try to use or as it should direct me to a working proxy close to me. Normally I have to change the proxy server. ![]() When it stops I can't get it to work again without extensive fiddling with it. I am using the deluge in a docker container the image is from linuxserver.io and the version is Deluge 2.0.3-2-201906121747-ubuntu18.04.1 It works most of the time But I have a problem that from time to time the connection stops working and all torrents have a tracker status of something like connection timed out. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |