Adding torrents on Deluge WebUI 2.1.1 on NAS, get Tracker Status: certificate verify failed / unspecified system error

[mhertz]

Sorry still no help, but just wanted to add that I was checking out what the package does/uses, and was surpriced to see that although uses a wheel for libtorrent, then not coming from pypi where issue lies specifically, but instead built from scratch, like openssl, which isn't static here and correctly includes build option to look for certs into /etc/ssl dir, and has a comment about doing that so can find the certs from the DSM. Libtorrent seems built with crypto=openssl, unless i'm mistaken, so now i'm very puzzled about why this happens.

Sorry to have thrown out red hearing seemingly, but just sounded like regular pypi wheel issue.

I think I will post about this in there issues section on the synology packages github repo later, tomorrow maybe, and will post back if hearing anything.

Edit: https://github.com/SynoCommunity/spksrc/issues/5420

[mhertz]

@Sindweller @Orchismo, Can you guys please confirm if your issue comes from a new deluge install or an update? I'm asking because th0ma7, dev of deluge DSM package, kindly answered my ticket on there github and requested confirmation about that.

Thanks.

[jeps]

For me it is a new install on my Synology NAS (DS1815+).

My previous experiences with deluge 2.x and certificates were on different Ubuntu versions and both the Dev and stable Deluge releases.

[mhertz]

Sorry jeps and thanks for posting! I didn't realize you also had this issue(or even DSM user), sorry mate.

Your ubuntu issues are seperate, as you stated there using libtorrent from pypi:

I propose we release wheels on pypi which vendor openssl but don't integrate with certificate stores.

https trackers won't verify, but could still be functional with various workarounds. Lazy users can just disable validate_https_trackers; less-lazy users can use the SSL_CERT_FILE or SSL_CERT_DIR env variables to point to the right store, possibly setting up their own.

I think we reached a consensus (that we should vendor openssl, and sort out the various system cert store issues later), so this thread can be closed.

Source: By AllSeeingEyeTolledEweSew, dev of that wheel. from this libtorrent github thread: https://github.com/arvidn/libtorrent/issues/6448

[vferg]

I just came looking for an answer as well. I just saw the update yesterday and updated mine which is on Synology and I am having the same exact issue... It is the trackers with https, the few torrents I have that are http are fine. They should probably pull the update until it's resolved because this will everyone and as far as I can see I have no idea how to go back a version either so I am kind of stuck now.

[mhertz]

Thanks vferg, appreciate you posting, and i'll now mention over at synology github that it's now 4 users reporting this issue over here. Thanks again.

[Sindweller]

Mhertz, sorry for late reply, my deluge is a fresh install on my DSM.



Sending you love and blessings for helping us out this far! <3

[mhertz]

Thanks for posting Sindweller, I updated bug-report. Also, just really wanted to say thank you so much for your very kind post my friend, appreciate that!

[mhertz]

Found a working fix for this, package update upcoming.

Source: https://github.com/SynoCommunity/spksrc/issues/5420

Thanks for reporting and giving details guys!

(The fix was exporting SSL_CERT_FILE env-var and using certifi's where() function to find and use it's cert-store, meaning they don't have one under /etc/ssl/certs, hence presumably ca-certificates package not installed strangely, which should provide that. This is also done for windows already in deluge-code btw)

[Sindweller]

Thank you so much Mhertz! Your efforts are greatly appreciated!