I believe shouldn't be a dev-build-related issue, atleast not seen reported, or encountered myself neither.
I'm guessing you refer to doadin's dev-builds, so If you have time once, then could you kindly please test
my dev-version also thanks, as if there's an issue with mine, then I'd like to know thanks - if having 7-zip you can just right-click installer and select extract to folder and run deluge.exe from there, and delete folder when finished testing - Same with doadin's btw, likewise deluge 1.3.x official, and all other NSIS installers. Mine will though show error when extracting because I include multiple libtorrent's etc, confusing 7z, so just select 'Yes to all' upon that error.
Anyway, all I know is that openssl for libtorrent works for https tracker authentication, and another openssl dll-pair likewise works for '_SSL' module from stdlib, e.g. used from yarss2 etc - I check these whenever making a build, as bitten from it in older times, and have checked this works likewise on doadin's build previously.
However, I don't know much about certificates and such generally e.g. the ssl option in deluge itself specifically, which have no clue about honestly, and never messed with, so maybe that is where your issue lies?
What I mean is that the extent of my checking is that if openssl not there or in wrong version/configuration, then when adding torrent with https tracker, then the tracker tab will state under status: 'Unsupported protocol' or something of that nature, whereas will state 'Announce OK' if working. Likewise when adding feed with yarss2, then will state under it's log-tab 'Unsupported protocol' and no matches returned, if not working - both of these aren't the case, as far I see here atleast.
Do you have any tips for reproducal and what's/where the error specifically? Preferably wiith public torrent/magnet, as have no private tracker accounts myself.
Thanks for reporting.