View previous topic :: View next topic |
Author |
Message |
Mike Guest
|
Posted: Mon Nov 20, 2017 8:15 am Post subject: Item 302525611150 |
|
|
I got the following error for this item. My snipe was higher than the final price of the item and it looks like it didn't go through:
HTTP TIMEOUT (77)
Any idea what happened? |
|
Back to top |
|
 |
johnjpj Guest
|
Posted: Mon Nov 20, 2017 11:35 am Post subject: HTTP TIMEOUT (77) |
|
|
Same problem, my bid was the highest, I had not response email to say I had a problem but noticed HTTP TIMEOUT (77) to the right of my bid and the winning bid? Many thanks for an excellent product to date. |
|
Back to top |
|
 |
johnjpj Guest
|
Posted: Mon Nov 20, 2017 11:40 am Post subject: HTTP TIMEOUT (77) |
|
|
Sorry for wasting anyone's time, as soon as I saw this I thought I would piggy back but as soon as I posted the question I noticed more of the same lower down. We just need to accept that on occasion it will happen. This is the first bid I have lost since using Gixen years ago so I've got nothing to complain about. Thanks for the free product....it's great |
|
Back to top |
|
 |
juangrande

Joined: 09 Aug 2007 Posts: 890 Location: San Diego, California, USA
|
Posted: Mon Nov 20, 2017 7:08 pm Post subject: |
|
|
There are several things that could cause Gixen to report an HTTP TIMEOUT (77) error. It could be that eBay is blocking your bid for some reason.
Please email the item ID and your Gixen username to Mario directly at his Gixen support address, found on the Contact page. Then Mario will be able to look up what happened in the server logs.
You could also try bidding on an eBay item manually to make sure that eBay is accepting your bids. _________________ John
If you don't know where you are going, you will wind up somewhere else.
--- Yogi Berra |
|
Back to top |
|
 |
Gixen Advertisements

|
Posted: Mon Nov 20, 2017 7:08 pm Post subject: |
|
|
|
|
Back to top |
|
 |
Cupid

Joined: 09 Aug 2007 Posts: 7919 Location: Bristol, UK
|
Posted: Tue Nov 21, 2017 10:29 am Post subject: |
|
|
This same error has also been reported on this thread.
So perhaps thee is a more widespread issue that requires further investigation. _________________ Mark |
|
Back to top |
|
 |
|