

Looks like I'm going to have to wait till the week of the burn and get my tix off Craigslist.
mini_wheat wrote:melodiousdirge wrote:Your passcode is not registered.
You have reached our limit for trying. Please contact customer support for more information.
If you get this message, switch browsers or devices. I think it has to do with a cookie or something counting the times you refresh. I switched browsers and I'm back in queue, though I don't know if I kept my place. At least I'm in the running still.
This got me back in the queue.
If you get this message SWITCH BROWSERS.
Savannah wrote:It sounds freaky & wrong, so you need to do it.
You're absolutely right - at the rate it takes InTicketing to process the queue I'd estimate they've sold a grand total of 200 or fewer tickets so far. So we're probably all fine - it's just the principle of the thing. We're ready to purchase when they go on sale to get this out of the way. If they didn't go with InTicketing and instead went with any mainstream ticket outlet we'd see no increase in fees and we could go back to our business in minutes. The fact that people actually took today off just to wait in line all day for the chance to buy a ticket shows how little we trust this company to be reliable.Ano wrote:Burning Man isn't sold out yet.
The main sale isn't even sold out.
You can also clear your cookies manually. If you are on Windows, press Ctrl+Shift+Delete in your browser. The clear history dialog will appear (works for IE, chrome, and firefox). Make sure you're clearing cookies. Make sure the time period (if applicable) is long enough to ensure it's cleared (not just the last hour!). Hit OK. Go back to the ticket queue. You should be able to enter your code and reenter the queue.theCryptofishist wrote:Didn't work, Trilo. I have reached their limit for trying. Can't install another browser, because I still haven't resolved my earlier issue...
That's not what I heard.theCryptofishist wrote:I'm not on widows
Savannah wrote:It sounds freaky & wrong, so you need to do it.
junglesmacks wrote:WRONG....It's a cache issue!
Thanks for the advice but there's no need to be a twat about it.melodiousdirge wrote:I think it has to do with a cookie or something counting the times you refresh. I switched browsers and I'm back in queue
Yeah, I spoke too soon when I assumed they associated your position with your IP or something. Apparently the "you won't lose your place" line when you sign in was untested unfounded crap and not based on actual facts. Oh well.melodiousdirge wrote:Also it seems switching browsers (or clearing your cache) resets your position in the queue, considering I was in line 24 seconds after it opened and I'm still waiting.
I would think it goes by pc ip address, not your browserHayseed wrote:Got in at 12 and 51 seconds. At 1:10 my password locked out. 1:13 back on with different browser. It's now 3:27.
QUESTION: Should I stay put.....or
clear cookies and try going back on with original browser?
Logic being it would remember my place in line, instead of staying put at a 1:13 start time.
"I don't know" is an acceptable answer.
I'm in the same boat. I'd suggest staying put. Going by the logic that your place in line is stored in the cache/cookies then when you clear it, it will go away and you'll just be starting all over again.Hayseed wrote:Got in at 12 and 51 seconds. At 1:10 my password locked out. 1:13 back on with different browser. It's now 3:27.
QUESTION: Should I stay put.....or
clear cookies and try going back on with original browser?
Logic being it would remember my place in line, instead of staying put at a 1:13 start time.
"I don't know" is an acceptable answer.
Your words sound of logic and intelligence....I think I will stay put.melodiousdirge wrote:I'm in the same boat. I'd suggest staying put. Going by the logic that your place in line is stored in the cache/cookies then when you clear it, it will go away and you'll just be starting all over again.Hayseed wrote:Got in at 12 and 51 seconds. At 1:10 my password locked out. 1:13 back on with different browser. It's now 3:27.
QUESTION: Should I stay put.....or
clear cookies and try going back on with original browser?
Logic being it would remember my place in line, instead of staying put at a 1:13 start time.
"I don't know" is an acceptable answer.
The original message wasn't clear whether it remembered your passcode or your browser via cookies but it's becoming pretty clear that it's not your passcode... which sucks for you and I and a bunch of others that had this issue. I'm sure there's enough tickets that I'll get there eventually but this is a serious drain on my day and mood.