RM+ 2.2 is currently in testing guys just final touches, it's me who has no time to finish some silly bugs.
Printable View
RM+ 2.2 is currently in testing guys just final touches, it's me who has no time to finish some silly bugs.
Note that unlike in mRatio, you have two advantages here: proxy settings can be changed after adding a torrent, and for multiple ones at the same time.
That information comes from the tracker and is optional. If not available, you'll have to make do without it. A real client would be able to classify peers in either category to some extent as it connects to them, but RM+ cannot do this (although such a feature is planned).Quote:
also seeders and leachers don't report correctly to RM+
mRatio has a bug that makes it parse the data incorrectly unless it comes from scraping the torrent manually, if the emulation and tracker support that. So once again, it could be worse :gredface:
Great news. Still using the latest version. Many thanks to you!
I am still getting "Tracker Response is empty. Torrent state: Error" even after tweeking the registry as suggested. Help please.
Hopefully, this works. I have sent you a link for the torrent file you asked for.
We have a difficult situation here, nya. Testing based on the data you messaged me indicates this particular tracker only supports TLS 1.3. Such a configuration is both highly unusual and discouraged, but considering context, they likely want to enforce the use of Encrypted Client Handshake which is a version-exclusive extension.
The registry values linked to in the first post explicitly disable TLS 1.3, because Microsoft's implementation isn't ready for prime time and causes more trouble than it's worth (or at least that's how it was last time I checked). However, you can turn it back on for testing purposes by merging the following. Note that your Windows and .NET Framework versions must be new enough; can't enable functionality that isn't there!
And yet, even if successful, that's only one piece of the puzzle. Their use of Cloudflare means they may also be sending chunked responses, which RM+ can't deal with at the moment (when this occurs, you'll see "received tracker response" followed by an error and garbage symbols in the log). Since TLS 1.3-only servers are very infrequent, I don't have a test setup for capturing data from them, so I can't confirm this. But if correct, it means you won't be able to use RM+ at all until the new version is out. The workaround on post #808 or switching to mRatio + Fixer won't work either!Code:REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:ffffffff
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00002a80
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00002a80
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00002a80
; This line is just a comment, but don't delete it.
I spent a good amount of time debugging the tracker respond using 2.2 version that supports TLS 1.3 and "Chunked" bug fixed to realize that i use windows 10 version old enough to make the server cry again.
To complete the puzzle you have to use windows 10 version at least 1903, besides 2.2 version of RM+ which is in the works.
https://sockettools.com/kb/windows-a...-tls-versions/
So i need to upgrade my windows 10 machine to complete the test
That's exactly why we're not ready for TLS 1.3-only servers just yet... imagine the non-technical people that don't even know why they can't access, or some browsers and torrent clients work while others don't :suicide:
So your suggestion for now is to wait for the new version of Ratio Master 2.2? I am using windows 10 Pro Oct 2020 Update (20H2) which I believe is newer than 1903.
I don't want to get caught because I need a lot of stuffs from that tracker and Ratio Master is the only way I can keep my ratio in check.
Waiting for the new version more eagerly now... :wink2:
I'm missing the double post merger already =]
If the registry values on post #820 don't work, that's exactly what you'll need to do. Given such a scenario, we're working hard to push 2.2 as soon as possible, and I'd recommend using the ratio tool on Extreme Mod as a stopgap alternative.
Registry hacks only turning on what's "already" there, So versions before 1903 there is no TLS 1.3 support at all to be turned on.
2.2 version will leave the TLS to the OS to decide which version you need and provide the right solution for it, So you need to be prepared with the knowledge for the right and minimum version that support TLS 1.2 or TLS 1.3.
I will try to add detectors for the maximum your device is supporting and what TLS version the tracker is using to be more user friendly for non-tech persons.
The new registry did not change anything. I am still receiving the same error message. So, I guess I will wait for the newer version and hope for the best.
Thanks for all the help.
Really appreciate it.
Thank you for keeping the non-tech users in mind. We will take all the help we can get. Thanks for all the work you all do.
Regards