[bob]

Thanks Mark,

I think I've got a handle on the problem here. Seems I was able to get a captcha when logging out and then back in again.. however, this did not solve the captcha error in gixen. I even tried firing up my backup sniper - jbidwatcher. However, jbid couldn't even log in to my account on start-up.

From your response, and reading around, I'm guessing eBay had put my account on lock down - maybe for a couple of bids being placed at the same second. eBay also seemed to know the difference between myself logging in via my browser (no captcha) and jbidwatcher/gixen logging in (captcha request).

Approximately 18 hrs after the first captcha, seems ebay lifted the lock down and everything when back to normal.

I place a number of snipes everyday, in the future I will keep an eye out for auctions finishing in the same second.

Thanks for the help

[Cupid]

The way that Gixen works... placing bids as you would via a browser and processing the pages that Ebay returns from each submission... it is unlikely that there could be false positive detections of Captcha images.

However, obviously, Gixen has no control over how Ebay algorithms decide to produce those blockages... or for how long Ebay imposes them on an account.

What we do suspect is that, currently, the cause is often trying to snipe multiple auctions that end at exactly the same second, with offsets that result in bids being attempted to be placed at exactly the same second... and if you do that again after having verified your account via the Gixen socks proxy... Ebay will often impose the restriction again... over and over again, seemingly without end.

[bob]

Hi

Seems every couple of months I have a captcha error and all the snipes I have set following that snipe get cancelled.

However, when I then proceed to connect to the proxy and place a bid to encounter said captcha and fix, I get - nothing... The bid places with no captcha request (via the Gixen proxy). I would like to point out that it could be some time after the error.

Is this a bug I have encountered, or is this expected behaviour? Seems like Gixen is throwing a captcha error when this is not the actual problem.

Thanks