Proxy Not Accessible In BC 1.33 x64

[U4RedaolNowdEht]

I signed up just to post about two issues that need to be fixed in this version and all the BitComet.releases after ver. 1.28 x64.

Problem .1

When you set the bandwidth limits in schedule option and it's activated, the limits aren't respected. Meaning BC runs the torrent(s) without limit, even when the master limit is set. I've tried every new release and the problem persist so I had to downgrade back to 1.28 the version that worked perfectly.

Problem .2

This issue/bug is with the latest version, it doesn't allow you to use a proxy which is a big issue given the current situation in the US. I would enter thr IP:port and Socks 5, hit apply and then refesh the IP. I go back to try a different IP:Port when the previous information is missing. So BC reverts to using your real IP at any given, even when BC is restarted and/or set to start with Windows. Previous versions didn't have this issue.... as far as retaining the VPN/Proxy info so BC can be refreshed with the input values.

[queeniequ]

I'll test the new version to see whether the problems exist. If they do exist, I'll convey these problems to our dev team. Thank you for your suggestion.

[queeniequ]

I've tested the first problem and found it works well on my computer. As to the the second problem, I've conveyed this problem to dev team. I'll respond to you once I have any news.

[U4RedaolNowdEht]

Thank you. As for problem 1 I'll play with BC 1.33 a little more.I did take into account that I didn't really see any reports about it. So I guess I have to go through the settings more carefully to see if I didn't set something properly. As for problem 2 I'll test that too as I wait for your update. Thanks again, I love this software it's better than all the others in my opinion.

[wxhere]

Hi, U4

In BitComet v1.33 the proxy settings changed from previous versions: BitComet will remember the IP:Port for sock4/4a/5 and IP:Port for HTTP 1.1 proxy separately. While in v1.32 and before, all the socks/http proxy share the same IP:Port settings.

I tested the http downloading using sock5 / http proxy / no proxy configurations, and the result is correct. BitComet will connect to download server through specified proxy server.

Please tell me your detail operations on BitComet to help me reproduce your encountered problem. Thanks.

[U4RedaolNowdEht]

Okay , I have BC 1.33 x64 installed and with the same settings as the previous working version i.e 1.28 x64, I enter the IP, Port and select Sock 5 apply, then right click the IP address which displays the WAN bottom right. I hit refresh so the Proxy IP will be reflected as WAN. The entered info is gone when I go back in options / proxy , I try to enter the IP:Port info I always use again. Everytime I refresh to reflect the Proxy IP it just revert back to my ISP IP. Hope this is the description you were looking for. Thanks..... as this is the main issue with the latest. The bandwidth limit not being respected continued through versions after 1.28 x64.

I also use CheckMyTorrentIP to make sure the correct IP is being used and reflected..

Edited August 14, 2012 by U4RedaolNowdEht (see edit history)

[wxhere]

I have tried as you said.

1. after entered the ip:port in proxy setting page, and click apply button, did you close the option window? If the option window remains open, you are not able to right click the IP address.

2. you hit refresh after right click the IP address, is that the "check it again" command in the right-click menu? (I have selected English language in the Tool menu of BitComet)

3. "The entered info is gone when I go back in options / proxy" - is that means the "proxy type" is still Socks5, but the "proxy server" and "proxy port" become empty? I didn't encounter this problem, and the "proxy server" and "proxy port" are still what I filled.

4. If the "proxy server" and "proxy port" become empty after refresh WAN IP, please check is there any other operations on BitComet will lead to the proxy settings missing. For example, open a torrent file, restart BitComet program.

5. Please tell me your Windows version (xp/vista/7?), BitComet language (in tools menu), BitComet install folder ( is it C:\Program Files\BitComet ?)

6. about the bandwidth limit problem, let's discuss it later, after the proxy setting problem.

Thanks again.

[U4RedaolNowdEht]

Response by number-

1. After I entered the requested info in Proxy option I click apply, the window closes. Then I attemp to refresh and WAN IP doesn't change.

2. Yes.

3. Yes , it still shows Socks 5 as Proxy type selected. For the IP box is empty and Port section shows a 0. I'm not sure why this issue occurs. From your results the issue seems specific to my use, I didn't encounter this with ver. 1.32 x64 and under.

4. It is empty after these conditions ~>

A). I hit apply after info is entered and window closes. I then reopen the Proxy setting box.

B ). After ^A^ but without reopening the Proxy settings. Instead I restart BC , then I'd check WAN IP which states the ISP IP. In other words the previous settings as far as Proxy IP & Port didn't stick and/or attempt to connect to Proxy settings thus real IP displayed by default. Even though Socks 5 is selected(based on what was entered for Proxy use and what's left see ^3^.

C).I start the torrent after ^A^ & ^B^ but I input the IP & Port again and select Socks 5 , apply/ ok. Try to refresh WAN IP, it shows real IP.

5. My O/s is W7 x64, language in BitComet x64 english and C:\Program Files\BitComet is the installation location.

6. Understood.

Thanks.

Edited August 15, 2012 by U4RedaolNowdEht (see edit history)

[wxhere]

Thanks for your reply. I think I got the point.

After hit Apply button in Option Window, the Option Window will not close in normal situations. It should only be closed after hit OK or Cancel.

So in your situation, the Option Window closed immediately after hit Apply, means there were errors in settings and the program didn't handle it correctly. As a result, your proxy IP:port settings are dropped and not saved to BitComet. So the proxy settings are never been taken effect.

To confirm my thought, please do the following test to help us fixing the bug: modify some settings and hit Apply, try to find which setting makes the Option Window closed incorrectly.

Thanks.

[U4RedaolNowdEht]

Oh sorry , I didn't mean it automatically closed after I hit apply. I just didn't state that I hit OK after apply, Sorry for the misunderstanding, Since you don't have this issue I'm starting to think it might have something to do with my security apps blocking BitComet from storing key strokes i.e anti-logger. Although 1.28 - 1.32 x64 worked fine. I will test on a newly installed W8 partition since not much will be affected... and report back.

[wxhere]

No problem. If the proxy settings can not be saved, other settings in BitComet maybe have this issue also. Please check other settings like download speed limit, default save folder and so on...

looking forward to your reply

[U4RedaolNowdEht]

Okay , I tried on W8 with all anti(s) disabled fresh install of BC 1.33 x64. With stock options , nothing altered but the Proxy option and required info typed in. Same issue and I literally don't want to DL behind my IP directly so I would have to downgrade to what works for me(1.28x64). Until a working version is released hopefully soon.

[wxhere]

Thanks for reply. I will do more test, hoping to reproduce this bug.

[wxhere]

I have installed Win8, and the issue occured as you described. We will fix this bug in next version. Thanks for your support!

[wxhere]

The porxy setting bug has been fixed. It's due to a error in fetch the proxy setting of IE as BitComet default proxy setting. Thanks U4 for the report.

For the schedule problem, please tell more detail about your operations on BitComet.

In my test, the download rate limit and download pause started normally when I set Windows time to the scheduled hour.

looking forward to your reply

[U4RedaolNowdEht]

Thanks again Wxhere , I will be looking forward to 1.34x64. I will report back about the scheduler shortly.