You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The situation is Electorrent is configured with multiple servers. When Electorrent is launched as a result of "executing" a magnet file or .torrent link, it will attempt to send that link to the default torrent server, which is the desired behavior. However, if you then switch to another torrent server, it seems to "remember" that it launched via a magnet file and then it also sends that link to the server you switched to.
So the fix that need to be implemented is that after Electorrent is launched and sends the link to the first server you connect to, it needs to forget the fact that it was launched via link and stop trying to send it to additional defined servers.
If Electorrent is launched from the Start menu, this does not happen. It's only when the app is launched as a result of a file action.
Thank you!
The text was updated successfully, but these errors were encountered:
Client: qBittorrent
Client Version: 4.6.3 (latest)
Operating System: Windows
Application Version: 2.8.3
Description:
The situation is Electorrent is configured with multiple servers. When Electorrent is launched as a result of "executing" a magnet file or .torrent link, it will attempt to send that link to the default torrent server, which is the desired behavior. However, if you then switch to another torrent server, it seems to "remember" that it launched via a magnet file and then it also sends that link to the server you switched to.
So the fix that need to be implemented is that after Electorrent is launched and sends the link to the first server you connect to, it needs to forget the fact that it was launched via link and stop trying to send it to additional defined servers.
If Electorrent is launched from the Start menu, this does not happen. It's only when the app is launched as a result of a file action.
Thank you!
The text was updated successfully, but these errors were encountered: