bagurka Posted May 24, 2006 Report Share Posted May 24, 2006 I was running my own tracker (PHPBTracker) and uTorrent worked fine until I moved the tracker to a new webhost. Now (with the same domain name and the same tracker script and database) uTorrent can't seed giving me the red up arrow and "HTTP Error 406" for every torrent I'm trying to seed.At the same time another BT client (ABC) works fine. But I don't want to switch back to ABC and so don't other users of my tracker.I suppose something in the web server settings is causing this. I don't have access to Apache config files on the old and new server, so I can't tell the difference. I can tweak Apache settings by putting a .htaccess file in the tracker directory though.Appreciate if someone can tell what may be causing the webserver to reject uTorrent's requests... Thanks in advance. Link to comment Share on other sites More sharing options...
Firon Posted May 24, 2006 Report Share Posted May 24, 2006 Sounds like a broken server or tracker. 406 means not acceptable, which means your server/tracker doesn't like whatever headers µTorrent is sending. Link to comment Share on other sites More sharing options...
bagurka Posted May 25, 2006 Author Report Share Posted May 25, 2006 It looks like Apache never even calls the tracker script rejecting the client right away.So I'm wondering what exactly in the µTorrent headers might make it mad and if there a way to make the server tolerate it instead of rejecting requests. Link to comment Share on other sites More sharing options...
Firon Posted May 25, 2006 Report Share Posted May 25, 2006 Without control of the server, I'm not sure there's anything you can do. Link to comment Share on other sites More sharing options...
bagurka Posted May 25, 2006 Author Report Share Posted May 25, 2006 I do have some control via .htaccess files and I can ask the webhost tech support to do some tweaks. But I have no idea what exactly to tweak Link to comment Share on other sites More sharing options...
bagurka Posted May 31, 2006 Author Report Share Posted May 31, 2006 Does anyone know (maybe the developer will be kind to tell): what does uT put in the Accept-Encoding field of the HTTP header when sending the GET request to the web server? I believe my problem lies there. Link to comment Share on other sites More sharing options...
bagurka Posted June 1, 2006 Author Report Share Posted June 1, 2006 Mistery solved. My new web hosting blocks most torrent clients (uT, Azureus, the original BitTorrent, and probably some others, but apparenty not ABC - I guess they never heard of it) based on the User-Agent signature in the HTTP request header. I talked to the tech support and they aren't willing to do anything about it. Sadly, I was planning on sharing 100% legal content via Bit Torrent (my own little free programs).Besides moving to another hosting (which I'd hate to do since this hosting is really superb comparing to many others), the only other solution would be for uT to have an option to have a custom User-Agent signature... Link to comment Share on other sites More sharing options...
Firon Posted June 1, 2006 Report Share Posted June 1, 2006 Well, that's not gonna happen, we don't support spoofing (and neither does most of the BT community).Sorry. Link to comment Share on other sites More sharing options...
bagurka Posted June 1, 2006 Author Report Share Posted June 1, 2006 > Well, that's not gonna happen, we don't support spoofing (and neither does most of the BT community).I understand.Just figured kind of a way - Proxymitron (HTTP traffic filter) can replace any headers on the fly.Sorry to have bothered good people here. If only the web hosting mentioned that they block BitTorrent clients in the user agreement or somewhere in their FAQ, but no.Thanks for the great software! Link to comment Share on other sites More sharing options...
Firon Posted June 1, 2006 Report Share Posted June 1, 2006 Well, uh, Proxomitron would only work on your end. Wouldn't the tracker still reject all the other clients? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.