Opened 7 years ago
Last modified 6 months ago
#3091 new bug
Proxy settings ignored
| Reported by: | Alexandre Viau | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | needs verified |
| Component: | Plugin | Version: | 1.3.15 |
| Keywords: | proxy | Cc: | deadlyknapsack@gmail.com, a.starr.b@gmail.com |
Description
Hello,
Even with intentionally bad proxy settings, Deluge can still download/upload.
I was doing this to confirm that deluge was in fact using my proxy, but it looks like its not.
Note that I have configured the proxy from the Web UI.
I have restarted the daemon several times.
Change History (7)
comment:1 by , 7 years ago
| Cc: | added |
|---|---|
| Keywords: | proxy added |
comment:2 by , 7 years ago
Note that I have tested with the official Debian package for Deluge.
Currently, Debian has the following libraries versions:
- python-libtorrent 1.1.1
comment:3 by , 7 years ago
| Cc: | added |
|---|
comment:4 by , 7 years ago
| Cc: | added |
|---|
comment:5 by , 7 years ago
I encountered this problem in Deluge2.0. Even if SOCKS5 is forcibly stopped, it can still be downloaded and uploaded
comment:6 by , 5 years ago
I do not experience this in 1.3.15. Refer to comment 41 on https://dev.deluge-torrent.org/ticket/2149
Is the distinction non-authenticated socks5?
comment:7 by , 5 years ago
| Component: | Unknown → Plugin |
|---|
Confirming and verifying that this is still a bug. This case is already opened at https://dev.deluge-torrent.org/ticket/2149
It would be very beneficial to hear back from the developers on this case.
Thank you so much :)
Confirmed. This was reported over 5 years ago and is still not fixed. Bug #2149 is about the same and was reported to be solved in version 1.3.14, but it clearly isn't.