![]() ![]() # Can't detect which method we should be using so just denyĭiff -Nur deluge-1.3.15-py2.7.egg/deluge/ui/web/js/deluge-all.js deluge-1.3.15-py2.7.egg-noauth/deluge/ui/web/js/deluge-all.js ui/web/auth.py should be like following:ĭiff -Nur deluge-1.3.15-py2.7.egg/deluge/ui/web/auth.py deluge-1.3.15-py2.7.egg-noauth/deluge/ui/web/auth.py find section “deluge.LoginWindow” and replace the function (it is located near the end of the minified line) ui/web/js/deluge-all.js, usually the is /usr/lib/python2.7/dist-packages/deluge/ or /usr/lib/python2.7/dist-packages/deluge-1.3.15-py2.7.egg/deluge. If we already have a reverse proxy for it(I usually add ssl and htpasswd via proxy), Deluge-Web will be useless, we can disable this build-in auth by folloing steps. You can read up on portforwarding, incoming connections and uploading with some quick googling if interested.The Deluge-web has a build-in Authorization, you need to input your password to manage your client. If deleting the rules upnp/natpnp makes and not setting them up manually, as you did before, then you will have less connectivity, but if e.g downloading popular torrents then it will still work fine, and there mostly is for improving upload connectivity(it effects download speed too if the torrent is less popular or have bad seed-to-peer ratio, as when you get throttled/punished for not uploading so much, and if not a bunch of available seeds then will affect you more there, but will still work(you're rotated-in regardless(unthrottled) just under-prioritized compared to other more uploading peers), just slower). ![]() So either you disable upnp/natpnp and set up portforwarding yourself in router or you let upnp/natpnp do it. It can sometimes duplicate the port-forwards and if the port change then new rules made etc. Pretty much all torrent-clients(except rtorrent and a few select others probably) has upnp enabled which sets portforwarding up for you automatically, so you get better connectivity in the torrent swarm(as you then have incoming connections also, instead of only outgoing ones). ![]() So how do I stop Deluge from creating more ports? Are they even needed? Im new to all this so any input would be appreciated. I refreshed the port forwarding page mutliple times to see if Deluge created some more and it didn't so I guess Deluge doesn't need them? While they were downloading I checked the forwarding rules and again there were 2 new ones (one for TCP and one for UDP), I deleted them both while my torrents were downloading to see if they are even needed and they weren't. Than I rebooted again and tried to download some torrents. I deleted all the rules made by Deluge and unchecked the boxes in WebUi prefrences that say "Use Random Ports" and I changed the ranges to 0-0. So I just setup my server on Ubuntu Server 18.04.4 LTS and installed Deluge 1.3.15. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |