Stop µTorrent accessing webserver

[elixir]

Hi,

I've been looking for a solution to this and I'm sure there is one, but they're hard to find, so I thought I'd post it.

I run µTorrent on the same machine as an Apache webserver on port 80.

The webservers' access.log get filled with these long entries from 127.0.0.1 containing "GET /announce?info_hash=...", which all result in 404's.

What causes this and more importantly, how do I turn this behavior off?

Thanks,

Alex

[DreadWingKnight]

How many of the torrents that you have loaded have thepiratebay's trackers in them?

[elixir]

There could be quite a few piratebay trackers in there at any time.

Are you suggesting I block these? Is there a more practical alternative to blocking?

[DreadWingKnight]

nemu ~ # dig tracker.thepiratebay.org

; <<>> DiG 9.4.3-P5 <<>> tracker.thepiratebay.org
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6525
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0

;; QUESTION SECTION:
;tracker.thepiratebay.org.      IN      A

;; ANSWER SECTION:
tracker.thepiratebay.org. 3600  IN      A       127.0.0.1

;; AUTHORITY SECTION:
thepiratebay.org.       526     IN      NS      ns1.thepiratebay.org.
thepiratebay.org.       526     IN      NS      ns0.thepiratebay.org.
thepiratebay.org.       526     IN      NS      ns3.thepiratebay.org.
thepiratebay.org.       526     IN      NS      ns2.thepiratebay.org.

[elixir]

Thanks for that most cryptic reply ;-)

I'm sure it could be useful, but am afraid I can't quite make sense of what you're suggesting.

Can you please clarify?

[DreadWingKnight]

In short, you want the loopback access to stop, you need to REMOVE the piratebay's trackers from the torrents before you load them.

[Switeck]

Or painstakingly remove *EVERY* piratebay tracker from already-loaded torrents...since they're all doomed to fail anyway AND screw with your server doing it!

[elixir]

Ah. I see. I'll work on setting that up.

Thanks again.