#2149: deluge ignoring proxy settings
-------------------+--------------------------------------------------------
Reporter: rm | Owner:
Type: bug | Status: new
Priority: major | Milestone: 1.3.6
Component: gtkui | Version: other (please specify)
Keywords: |
-------------------+--------------------------------------------------------
Good day.
I fail to using deluge 1.3.5 in proxy environment (w/o autorization). It
worked fine in 1.3.4 at the same site and I'm 100% that I didn't block
anything in squid proxy server, all the applications like IM-clients,
browsers etc successfully working via the same proxy. Here is how I tested
it:
- removed ~/.config/deluge
Then just start it, go to Edit -> Preferences -> Proxy. Put in HTTP,
proxyaddr:proxyport into all four fields and then just checking squid with
sqstat - there is not even connections from deluge.
I also did another test: the settings are the same (proxy is turned on in
deluge), and on default router's firewall I allowed direct connections
with internets from my system - deluge successfully downloading the same
torrent, but still not using proxy. So it looks like that it didn't ever
try to use it.
If it make any difference, I'm using GTK-frontend of deluge 1.3.5 on
FreeBSD. Related apps versions are:
boost-libs-1.48.0
boost-python-libs-1.48.0
libtorrent-rasterbar-0.16.2
py-libtorrent-rasterbar-0.16.2 (python binding)
python 2.7.3
Please note once again that deluge working just fine another way. The
problem is only appears when I try to use deluge via proxy. And there was
no such problems with 1.3.4 in the same environment.
Here is what was added to my ~/.config/deluge/core.conf
{{{
"proxies": {
"peer": {
"username": "",
"password": "",
"type": 4,
"port": 3128,
"hostname": "192.168.0.7"
},
"web_seed": {
"username": "",
"password": "",
"type": 4,
"port": 3128,
"hostname": "192.168.0.7"
},
"tracker": {
"username": "",
"password": "",
"type": 4,
"port": 3128,
"hostname": "192.168.0.7"
},
"dht": {
"username": "",
"password": "",
"type": 4,
"port": 3128,
"hostname": "192.168.0.7"
}
},
}}}
I see in debug log:
{{{
[DEBUG ] 15:27:06 config:197 Setting 'proxies' to {'peer': {'username':
'', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'web_seed':
{'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080},
'tracker': {'username': '', 'password': '', 'hostname': '', 'type': 0,
'port': 8080}, 'dht': {'username': '', 'password': '', 'hostname': '',
'type': 0, 'port': 8080}} of <type 'dict'>
}}}
and later:
{{{
[DEBUG ] 15:27:06 config:391 Config /home/rm/.config/deluge/core.conf
version: 1.1 loaded: {'proxies': {u'peer': {u'username': u'', u'password':
u'', u'type': 4, u'port': 3128, u'hostname': u'192.168.0.7'}, u'web_seed':
{u'username': u'', u'password': u'', u'type': 4, u'port': 3128,
u'hostname': u'192.168.0.7'}, u'tracker': {u'username': u'', u'password':
u'', u'type': 4, u'port': 3128, u'hostname': u'192.168.0.7'}, u'dht':
{u'username': u'', u'password': u'', u'type': 4, u'port': 3128,
u'hostname': u'192.168.0.7'}}, }
}}}
So it looks like it set proxies before actually parsing core.conf?
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2149>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
