jaelanicu Posted August 10, 2008 Report Share Posted August 10, 2008 In v1.8 release, when using HTTPS proxy, tracker always failed with "host name not found" status. This doesn't happen in v1.7.7 nor when using other type of proxies.FYI, my internet connection is available only via proxies. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 10, 2008 Report Share Posted August 10, 2008 internet explorer proxy settings set properly? Link to comment Share on other sites More sharing options...
Firon Posted August 10, 2008 Report Share Posted August 10, 2008 Do you have a firewall? Are you sure it's actually an HTTPS proxy and not just a plain HTTP one? Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 10, 2008 Report Share Posted August 10, 2008 I just set up CCProxy, set uTorrent 1.8 to use an "HTTPS" proxy pointing at CCProxy, and then added a torrent with an HTTP tracker. This worked fine.Does that not work for you, or is your situation different? What is the tracker URL you're using?In order for the HTTPS proxy to work, you need to be able to resolve DNS names locally (without sending them through a proxy). Are you able to do this? Link to comment Share on other sites More sharing options...
jaelanicu Posted August 11, 2008 Author Report Share Posted August 11, 2008 It only give the error when I use HTTPS proxy (only for tracker - not for peers). Using HTTP, SOCKS4 or SOCKS5 doesn't give any error (all of them). This error doesn't apply for v1.7.7. Only in v1.8 release/final which I'm currently using, don't know about betas nor RCs. The problem is not caused by firewall since I don't bother using one and since v1.7.7 works. Also it's not tracker specific also, since in v1.7.7 they all works. In v1.8 release, they all got error - including all torrents.EDIT:My NIC DNS is set to the DNS proxy, which works properly. Please note: v1.7.7 doesn't have this problem. Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 11, 2008 Report Share Posted August 11, 2008 It only give the error when I use HTTPS proxy (only for tracker - not for peers). Using HTTP, SOCKS4 or SOCKS5 doesn't give any error (all of them). This error doesn't apply for v1.7.7. Only in v1.8 release/final which I'm currently using, don't know about betas nor RCs. The problem is not caused by firewall since I don't bother using one and since v1.7.7 works. Also it's not tracker specific also, since in v1.7.7 they all works. In v1.8 release, they all got error - including all torrents.EDIT:My NIC DNS is set to the DNS proxy, which works properly. Please note: v1.7.7 doesn't have this problem.Can you capture the traffic with Wireshark? Both of 1.7.7 and 1.8. Post the capture on http://mediafire.com and link to it here. Please Link to comment Share on other sites More sharing options...
jaelanicu Posted August 11, 2008 Author Report Share Posted August 11, 2008 Man... I hate bloated applications. Not to mention that I only have a 4KB bandwidth...Anyway, I'm downloading Wireshare now.In the mean time, is there other alternative to Wireshark which I can use? Non-bloated of course... Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 11, 2008 Report Share Posted August 11, 2008 Man... I hate bloated applications. Not to mention that I only have a 4KB bandwidth...Anyway, I'm downloading Wireshare now.In the mean time, is there other alternative to Wireshark which I can use? Non-bloated of course...I found Microsoft Network Monitor recently. It seems to work ok. Link to comment Share on other sites More sharing options...
jaelanicu Posted August 11, 2008 Author Report Share Posted August 11, 2008 OK. I'm switching my download to Microsoft Network Monitor.I'll post the result once I get it done.EDIT:I'm done. This zip file contains 2 files for v1.7.7 and v1.8 versions.Test preparations:1. Stop DNS Client service (the Windows DNS cache).2. Launch Network Monitor.Test tasks for each uTorrent version:1. Set proxy to HTTPS and also enable proxy for P2P connections.2. Exit uTorrent.3. Start Network Monitor logging (no filters).4. Launch uTorrent.5. Wait until uTorrent is idle (until no network traffic).6. Start the Ubuntu torrent.7. Once the tracker status is not "updating...", stop the torrent.8. Stop Network Monitor logging.9. Save Network Monitor logging into file.I'm no expert in BitTorrent nor HTTPS protocol, but judging from the log, the behaviour is different between both versions. Anyway, I hope I get the work done properly. Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 11, 2008 Report Share Posted August 11, 2008 So it seems like DNS is properly resolved either way, but 1.8 never starts the TCP connection. For some reason it thinks DNS has failed.Please try out this test build: http://utorrent.com/utorrent.11759.exeRun it like this to get a logfile: utorrent.exe /LOGFILE dns.logThen run it, wait for the tracker update to fail, exit and send me dns.log.Please Link to comment Share on other sites More sharing options...
jaelanicu Posted August 11, 2008 Author Report Share Posted August 11, 2008 Here is the zipped dns.log plus netmon log file for build 11759. The dns.log says something about cache error, but I turned off the DNS Client service prior performing the test. Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 11, 2008 Report Share Posted August 11, 2008 Ah! I see the problem. uTorrent discards DNS responses if they are not routable. This causes a problem in your case, since you must use a proxy. I've special cased it for proxies:http://utorrent.com/utorrent.11760.exeLet me know if that works. If not, send me the log same as last time. Link to comment Share on other sites More sharing options...
jaelanicu Posted August 12, 2008 Author Report Share Posted August 12, 2008 Still not working. Here is the log: http://www.mediafire.com/?ckzcjjfj3dtDo you require more information regarding my network configuration? Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 12, 2008 Report Share Posted August 12, 2008 Hm. Two new builds:http://utorrent.com/utorrent.11761.exehttp://utorrent.com/utorrent.11762.exe Link to comment Share on other sites More sharing options...
jaelanicu Posted August 12, 2008 Author Report Share Posted August 12, 2008 Build 11761: No change...Build 11762: Success!Here's the log for both: http://www.mediafire.com/?y5xjyw43ibhI also re-tested the SOCKS4, SOCKS5 and HTTP proxies. Result is OK. They are not affected by this fix (build 11762).Many thanks for the hard work. Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 12, 2008 Report Share Posted August 12, 2008 Hm, that's odd. Can you give me the log for this build?http://utorrent.com/utorrent.11763.exe Link to comment Share on other sites More sharing options...
jaelanicu Posted August 12, 2008 Author Report Share Posted August 12, 2008 He? Not done yet?Tested. Build 11763 doesn't work again. ???Log file: http://www.mediafire.com/?5uhwnbegxuc Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 12, 2008 Report Share Posted August 12, 2008 Not quite done, sorry.http://utorrent.com/utorrent.11764.exe Link to comment Share on other sites More sharing options...
jaelanicu Posted August 12, 2008 Author Report Share Posted August 12, 2008 Build 11764 failed. Same error message.Log 11764: http://www.mediafire.com/?c9wxtj4m9ytMay I know what went wrong? Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 12, 2008 Report Share Posted August 12, 2008 May I know what went wrong?I'm trying to get the proxy special case working on your setup. For some reason it seems to work on mine. The build that worked turned off the route check entirely. Link to comment Share on other sites More sharing options...
Greg Hazel Posted August 12, 2008 Report Share Posted August 12, 2008 I emailed you the next test build. Link to comment Share on other sites More sharing options...
jaelanicu Posted August 12, 2008 Author Report Share Posted August 12, 2008 Already replied your email. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.