Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#5363 closed Bug (wontfix)

Configured proxy is not being used, local IP exposed

Reported by: bedge Owned by:
Priority: Highest Milestone: None Set
Component: Transmission Version: 2.77
Severity: Critical Keywords:
Cc:

Description

I have the following setup:

"proxy": "proxy.btguard.com", "proxy-auth-enabled": 1, "proxy-auth-password": "XXXX", "proxy-auth-username": "XXXX", "proxy-enabled": 1, "proxy-port": 1050, "proxy-type": 2,

Yet when I go to http://checkmytorrentip.com/ It is able to see my local IP rather than the proxy's IP.

Change History (4)

comment:1 Changed 9 years ago by livings124

Proxy support is no longer a part of Transmission.

comment:2 Changed 9 years ago by livings124

  • Resolution set to wontfix
  • Status changed from new to closed

comment:3 follow-up: Changed 9 years ago by bedge

This makes it completely unusable for NAS boxes that do not have a global proxy config option.

It's also dangerous to maintain the proxy options in the config while silently ignoring them. That leaves users completely exposed while they believe they are behind a proxy.

comment:4 in reply to: ↑ 3 Changed 9 years ago by rb07

Replying to bedge:

This makes it completely unusable for NAS boxes that do not have a global proxy config option.

Proxies never did, or will, fully work (i.e. too many protocols involved, proxies are only meant for http over TCP). This has been discussed a lot on the forum, and shows your lack of information.

It's also dangerous to maintain the proxy options in the config while silently ignoring them. That leaves users completely exposed while they believe they are behind a proxy.

The options you have shown are old remnants of previous installed versions, much older than current (see: https://trac.transmissionbt.com/wiki/EditConfigFiles#Proxy) and deprecated.

That makes your report invalid.

Note: See TracTickets for help on using tickets.