No, thank YOU for your effort and help.
After reinstalling with the latest installer, still in 2.0.3 portable mode with the latest libtorrent, Deluge 2 runs well and no longer crashes without requiring any changes in dlls (libpng16 confirmed present and not renamed in system32).
*OLD-THREAD - SEE NEW* [Unofficial] Deluge 2.0.x installer
Re: Deluge 2.0.x unofficial Windows installer.
Thanks mate, appreciate that!
I'm glad you helped me squash another issue others most probably will run into also, so thanks for good teamwork.

adding ltConfig plugin - unofficial Windows installer.
How to install the plug-in
1. I have downloaded the version that is updated for Deluge 2.0 and Python 3
2. Tried installing the from GUI / Preferences - nothing happened.
3. Tried copying it to
4. Tried putting it under
5. Tried renaming it to
I have only restarted
EDIT: Solved, a daemon restart helped with the plugin in
EDIT2: moved it to the config dir plugins folder, since the one in program files gets deleted on every reinstall. So this works too:
ltConfig
?1. I have downloaded the version that is updated for Deluge 2.0 and Python 3
ltConfig-2.0.0.egg
from https://github.com/ratanakvlun/deluge-ltconfig/releases .2. Tried installing the from GUI / Preferences - nothing happened.
3. Tried copying it to
c:\Users\szeke\AppData\Roaming\deluge\plugins\
- no luck either.4. Tried putting it under
c:\Program Files\Deluge\Lib\site-packages\deluge\plugins\
- still does not show up under Preference / Plugins.5. Tried renaming it to
ltConfig-2.0.0-py3.7.egg
- still not getting picked up.I have only restarted
deluge.exe
in thin client mode. Does Plugin installation require restarting the daemon?EDIT: Solved, a daemon restart helped with the plugin in
c:\Program Files\Deluge\Lib\site-packages\deluge\plugins\
, no rename needed!EDIT2: moved it to the config dir plugins folder, since the one in program files gets deleted on every reinstall. So this works too:
c:\Users\<UserName>\AppData\Roaming\deluge\plugins\
Last edited by petersasi on Wed Jan 15, 2020 4:26 am, edited 5 times in total.
changing log level for performance optimization - unofficial Windows installer.
Having ltConfig up and running my next venture is into performance optimization, according to https://github.com/arvidn/libtorrent/issues/2215 author of libtorrent suggest to enable
According to https://github.com/arvidn/libtorrent/bl ... /alert.hpp
Problem is I do not know which log level prints these
1. default log level is
2. more logging with
3. even more with
4. and most verbose logging with
EDIT: solved this too,
[WARNING ][deluge.core.torrentmanager :73 ] on_alert_performance: <Torrent Name>: performance warning: max outstanding piece requests reached, outstanding_request_limit_reached
performance_warning
alerts in the alert_mask setting.According to https://github.com/arvidn/libtorrent/bl ... /alert.hpp
performance_warning
is bit 9, which I believe is set, at alert_mask is 861 in my ltConfig
.Problem is I do not know which log level prints these
performance_warning
alerts. According to https://dev.deluge-torrent.org/wiki/Troubleshooting1. default log level is
error
2. more logging with
warning
(tying this now)3. even more with
info
(much more info than needed e.g. loading of every single torrent)4. and most verbose logging with
debug
(I hope I will not need to go up to this as it logs A LOT)EDIT: solved this too,
warning
log level seems to deliver performance_warning
s>[WARNING ][deluge.core.torrentmanager :73 ] on_alert_performance: <Torrent Name>: performance warning: max outstanding piece requests reached, outstanding_request_limit_reached
GeoIP.dat - unofficial Windows installer.
Sorry for spamming your topic, I am just trying to document the questions and solutions as I get at fixing them.
After enabling warning level logging, I have noticed:
After googling I have found viewtopic.php?t=51455 and downloaded the zip from there and unzipped it to
Because of data protection regulations now you have to sign up for an account to get a up to date copy: https://blog.maxmind.com/2019/12/18/sig ... databases/
Anyhow, just not using the latest, but an old, archived version of GeoIP.dat, I get another error:
...
Ok two mistakes by myself, I have fixed the ticket diff and it should be
Is this something that could be part of the installer?
After enabling warning level logging, I have noticed:
Such path is definitely not going to be found on Windows. So I wanted to point it to the right file in[WARNING ][deluge.core.preferencesmanager:73 ] Unable to find GeoIP database file: /usr/share/GeoIP/GeoIP.dat
C:\Program Files\Deluge
, to my surprise there was no geoip.dat
.After googling I have found viewtopic.php?t=51455 and downloaded the zip from there and unzipped it to
C:\Program Files\Deluge
.Because of data protection regulations now you have to sign up for an account to get a up to date copy: https://blog.maxmind.com/2019/12/18/sig ... databases/
Anyhow, just not using the latest, but an old, archived version of GeoIP.dat, I get another error:
Googling this Cas says: viewtopic.php?t=55382[WARNING ][ddeluge.core.preferencesmanager:73 ] GeoIP Unavailable
It seems that ... package py3-geoip is not the ... python package but you can try:
Code: Select all
pip install GeoIP
Ok two mistakes by myself, I have fixed the ticket diff and it should be
pip3 install GeoIP
or python3 -m pip install GeoIP
Is this something that could be part of the installer?
Re: Deluge 2.0.x unofficial Windows installer.
Thanks for your feedback peterasi, and you're most definately not spamming and I appreciate, and encourage, peoples thoughts and findings, and is a nice breakup from my own ramblings at times 
I have spend some time now, without success, on this geoip thing. I'll mess some more with it at a later time, but i'm not promising anything, because unless I can build it on linux and copy over to windows and it works, then I doubt I can, because there's no wheels, meaning that pip command need building C code with visual studio on windows, and it's never as easy as linux with ./configure, make and make install, and a bunch of errors always occurs in my experience because there's so many conflicting versions of tools used. The same with building libtorrent, I have 7 boost versions and 3 visual studio build tools versions installed, because one versions works with this, and another with that etc. Well, I only need 2 boost and 2 vc build-tools versions for both libtorrents, but rest where for testings to even come at that place where it worked, and was 2 weeks of headache before that place.
First that pip command needed header files, so I downloaded them from libgeoip, which also states is needed on the pip page of geoip, and added them to include folder, then the visual studio couldn't find the lib, and I then build the lib manually with visual studio from libgeoip first. Then it still didn't work, but was because the lib name was wrong, so I renamed the lib part away from beginning of filename, and then it fails now with unresolved externals found in the lib! Same experiences I had with libtorrent in beginning.
Sorry, but as said i'll look at building under linux and copy over, and i'll update if working, but not time now any more sorry. Else if anybody else finds the correct combinations of tools and commands and files and reports back, or better, make a wheel for py3.7 for me to install from, as not available online I checked.
Edit: I just checked on my main linux system, where I have deluge2 installed and including python-geoip, and it will not work to be copied over, as a *.so library, which I should have thought off anyways that it wouldn't work, as obviously libraries differs between windows and linux, but some python things are interchangeble, but not when with C code like here unfortunetly, sorry.
Edit2: Sorry, I didn't read the posted links initially, as thought they weren't needed till afterwards I had found a way building GeoIP at all, but now after reading them, then I see there are another alternative, which also is pure python so easier to "build" though needs a patch to a deluge file, like peterasi also referenced. I'll take another look at that, when having time for it.

I have spend some time now, without success, on this geoip thing. I'll mess some more with it at a later time, but i'm not promising anything, because unless I can build it on linux and copy over to windows and it works, then I doubt I can, because there's no wheels, meaning that pip command need building C code with visual studio on windows, and it's never as easy as linux with ./configure, make and make install, and a bunch of errors always occurs in my experience because there's so many conflicting versions of tools used. The same with building libtorrent, I have 7 boost versions and 3 visual studio build tools versions installed, because one versions works with this, and another with that etc. Well, I only need 2 boost and 2 vc build-tools versions for both libtorrents, but rest where for testings to even come at that place where it worked, and was 2 weeks of headache before that place.
First that pip command needed header files, so I downloaded them from libgeoip, which also states is needed on the pip page of geoip, and added them to include folder, then the visual studio couldn't find the lib, and I then build the lib manually with visual studio from libgeoip first. Then it still didn't work, but was because the lib name was wrong, so I renamed the lib part away from beginning of filename, and then it fails now with unresolved externals found in the lib! Same experiences I had with libtorrent in beginning.
Sorry, but as said i'll look at building under linux and copy over, and i'll update if working, but not time now any more sorry. Else if anybody else finds the correct combinations of tools and commands and files and reports back, or better, make a wheel for py3.7 for me to install from, as not available online I checked.
Edit: I just checked on my main linux system, where I have deluge2 installed and including python-geoip, and it will not work to be copied over, as a *.so library, which I should have thought off anyways that it wouldn't work, as obviously libraries differs between windows and linux, but some python things are interchangeble, but not when with C code like here unfortunetly, sorry.
Edit2: Sorry, I didn't read the posted links initially, as thought they weren't needed till afterwards I had found a way building GeoIP at all, but now after reading them, then I see there are another alternative, which also is pure python so easier to "build" though needs a patch to a deluge file, like peterasi also referenced. I'll take another look at that, when having time for it.
Re: Deluge 2.0.x unofficial Windows installer.
Still not there fully, but a "short" update. I found I made a mistake in the building of the C library which I took another shot at, but it still failed with errors again regardless, and I also saw unfixed bugreport about building on win10 failing. The devs state they don't really priotize that lib, so will probably take some time - they make another lib, which supports more formats also, though one tested it to be 4 times slower than the original, plus the poster stated same error there + it is not even supported/tested for VC2015, let alone 2017 or 2019, the three I currently have installed, and i'm not gonna add a fourth and anchient VC2010 version for this project solely, which is about 3-4GB big each(as e.g including win-sdk etc). Also, unless i'm missing something, then the legacy lite database format I believe deluge uses, has been removed by them, and so they provide geoip2 format now, so i'm not even sure it will work with them even if I gotten it to work. (Btw, actually I can build the c lib manually, but the errors occurs when the c lib need linked into the main geoip python app from pipy, with unresolved external symbols found and linking errors).
Regardless, Cas stated an alternative and provided a patch to deluge code to use the alternative with. In my personal testing, I have added the alternative and patched the deluge code to use it, and downloaded a legacy lite database file provided freely online by thrid-party, and it works, however it's needed to go into preferences in deluge and add path to the database file, which I have added to deluge folder in my current test system(unreleased as of yet), and that is annoying, I would like to change the deluge code so that it by default can find it in deluge folder, but now with some tests I need full path and cannot just add a relative path or only the filename, as not picked up then. Granted, it's not that big of a deal, and I could also hack it into my installer to patch the deluge code with choosen install path, but i'm honestly not going to bother with that, and if I cannot find other sulution, then you yourself need adding that path into preferences yourself.
Note, I haven't updated installers yet, as am only testing things out on my personal test-system, so all this is just for information purposses.
Regardless, Cas stated an alternative and provided a patch to deluge code to use the alternative with. In my personal testing, I have added the alternative and patched the deluge code to use it, and downloaded a legacy lite database file provided freely online by thrid-party, and it works, however it's needed to go into preferences in deluge and add path to the database file, which I have added to deluge folder in my current test system(unreleased as of yet), and that is annoying, I would like to change the deluge code so that it by default can find it in deluge folder, but now with some tests I need full path and cannot just add a relative path or only the filename, as not picked up then. Granted, it's not that big of a deal, and I could also hack it into my installer to patch the deluge code with choosen install path, but i'm honestly not going to bother with that, and if I cannot find other sulution, then you yourself need adding that path into preferences yourself.
Note, I haven't updated installers yet, as am only testing things out on my personal test-system, so all this is just for information purposses.
Re: Deluge 2.0.x unofficial Windows installer.
I have added support for GeoIP database lookups to both installers as per default functionality, and thanks peterasi for helpfull feedback and info on this, appreciated 
I added the very small/lightweight(110kb) pygeoip python module from pypi for the GeoIP lookup functionality, as Cas talked about and posted patch for using(scheduled for inclusion in deluge-2.0.4 on bug-ticket), which I also applied + I added a newly updated(december 2019) GeoIP.dat file into deluge install-folder, and finally, I added a few lines of python code to deluge, so that if the GeoIP database path selected in deluge preferences(or in core.conf) isn't a valid path/file, then instead of failing as before, I imade it do an extra and final search for GeoIP.dat in deluge install folder and if found then loaded and used, or else failing as before.
Edit:
I got the GeoIP.dat file I included from this third-party site here:
https://www.miyuru.lk/geoiplegacy
I used the 'Maxmind - Country' IPv4 link here, which always will point to latest version:
https://dl.miyuru.lk/geoip/maxmind/coun ... nd4.dat.gz
You can update yourself later on, if finding any need for such, or change to other version if preferred also, just rename unpacked file to GeoIP.dat and overwrite the old in deluge install folder.
I read up some more on this, and the geolite legacy database isn't available to unlicensed "regular" users no-more, and so we are either to use latest version from April 2018(which I could take from my linux system), or use a third-party updated one, like I already did, linked above(made from newest officially published maxmind GeoIP2 database translated to legacy geolite format with a python script), or use geolite2 official database which is updated and free, but needs software updates for being able to use it on the backend.
Also, transmission-remote-gui changed to same third-party GeoIP.dat file as I use in middle of 2019, after getting reports about it giving better/more lookups than the old official April 2018 version previously used.

I added the very small/lightweight(110kb) pygeoip python module from pypi for the GeoIP lookup functionality, as Cas talked about and posted patch for using(scheduled for inclusion in deluge-2.0.4 on bug-ticket), which I also applied + I added a newly updated(december 2019) GeoIP.dat file into deluge install-folder, and finally, I added a few lines of python code to deluge, so that if the GeoIP database path selected in deluge preferences(or in core.conf) isn't a valid path/file, then instead of failing as before, I imade it do an extra and final search for GeoIP.dat in deluge install folder and if found then loaded and used, or else failing as before.
Edit:
I got the GeoIP.dat file I included from this third-party site here:
https://www.miyuru.lk/geoiplegacy
I used the 'Maxmind - Country' IPv4 link here, which always will point to latest version:
https://dl.miyuru.lk/geoip/maxmind/coun ... nd4.dat.gz
You can update yourself later on, if finding any need for such, or change to other version if preferred also, just rename unpacked file to GeoIP.dat and overwrite the old in deluge install folder.
I read up some more on this, and the geolite legacy database isn't available to unlicensed "regular" users no-more, and so we are either to use latest version from April 2018(which I could take from my linux system), or use a third-party updated one, like I already did, linked above(made from newest officially published maxmind GeoIP2 database translated to legacy geolite format with a python script), or use geolite2 official database which is updated and free, but needs software updates for being able to use it on the backend.
Also, transmission-remote-gui changed to same third-party GeoIP.dat file as I use in middle of 2019, after getting reports about it giving better/more lookups than the old official April 2018 version previously used.
Re: Deluge 2.0.x unofficial Windows installer.
First, mhertz = genius. Second, I am having a hard time with the web interface. When I try to add a url or file I keep getting "not a valid torrent" with nothing really in the log other than
[ERROR ][deluge.ui.web.json_api :79 ]
[ERROR ][deluge.ui.web.json_api :79 ]
Re: Deluge 2.0.x unofficial Windows installer.
Lol, that made me laugh
First part I mean... Thank you mate, you're too kind and I appreciate the kind words for sure!
As for your issue, i'm affraid I cannot reproduce. Does same thing happen if trying this arch-linux iso torrent URL: (You can copy/paste link into deluge webui add dialog)
https://www.archlinux.org/releng/releas ... 1/torrent/
Or the same in magnet format:
magnet:?xt=urn:btih:3f70b98c6162c02924194447e1f23e749edf7a1f&dn=archlinux-2020.01.01-x86_64.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce
I tested with 2.0.3 everything default in installer, so libtorrent 1.2.3. You mentioned nothing in log, but did you make log for webui, or deluged.exe or both. Also, does it happen if using GTKUI?(if not then only log for webui is needed) How you start webui and deluged, though nssim or manually, or startup folder or...
This sounds like a deluge 2.x issue(meaning not installer/mismatched-files related), which for the most part unfortunetly are out of my reach, except when very simple fixes/diagnostics.

As for your issue, i'm affraid I cannot reproduce. Does same thing happen if trying this arch-linux iso torrent URL: (You can copy/paste link into deluge webui add dialog)
https://www.archlinux.org/releng/releas ... 1/torrent/
Or the same in magnet format:
magnet:?xt=urn:btih:3f70b98c6162c02924194447e1f23e749edf7a1f&dn=archlinux-2020.01.01-x86_64.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce
I tested with 2.0.3 everything default in installer, so libtorrent 1.2.3. You mentioned nothing in log, but did you make log for webui, or deluged.exe or both. Also, does it happen if using GTKUI?(if not then only log for webui is needed) How you start webui and deluged, though nssim or manually, or startup folder or...
This sounds like a deluge 2.x issue(meaning not installer/mismatched-files related), which for the most part unfortunetly are out of my reach, except when very simple fixes/diagnostics.