Proxy Problem - Some Trackers Connect, Some Don't

[socratez]

Hey everybody, I know the topic of I2P has already been discussed but I'm here with a slightly different question.

I'm using I2P as my proxy and the weird thing is some trackers connect and it's fine, then with others it gives me this "Proxy connect error: No connection could be made because the target machine actively refused it." Now if I just read that sentence it makes sense to me, the target machine is not happy with me using a proxy and said "no, you can't connect like that"- however the weird thing is that one of these trackers actively encourages it's members (it's private) to use a proxy, and most of them are public trackers like tpb, publicbt, torrentbay, etc.

I'm convinced the proxy is working because some of the trackers are connecting, but why are some of them giving me an error? I really doubt they're "actively refus[ing]" my connection, especially since one of the trackers refusing the connection is a proxy-friendly tracker.

Do I have some configuration option set wrong that's confusing some of the trackers, maybe?

Any help would be greatly appreciated.

[Firon]

Your uT is not able to connect to the proxy at all.

[socratez]

Your uT is not able to connect to the proxy at all.

But why am I able to download/upload to certain trackers (publicbt for example) and not others if my uT is not connecting to the proxy?

[socratez]

Nevermind - apparently I2P is not designed as an external proxy. I'm not really very knowledgeable about proxies so I'm not sure what this means exactly, but from my understanding I2P is actually more of a private network software than it is a proxy for the general internet.

Apparently I need to be downloading torrents from other users on the I2P network in order for it to work, so that's why I'm getting such bad results. You can close this topic.