Ready for Main Sale!!!

[TT120]

I got in at 12:00:27 and am still waiting. Had to refresh several times because the connection was lost but it seemed to keep my place in line. Lots of people have gotten their tickets that got in line after me so it seems there is no rhyme or reason.

Looks like I'm going to have to wait till the week of the burn and get my tix off Craigslist.

[VampireKitten]

... still waiting.

[Ano]

Yeah, we're all upset and mad and angry (or incredibly happy if one has a ticket), but, here's the thing...

Burning Man isn't sold out yet.

The main sale isn't even sold out.

We have time, folks.

Relax...

[FIGJAM]

In line at 12:00:40.

Still waiting.

[junglesmacks]

WRONG.

Just HOLD DOWN CTRL and HIT F5 to both clear your cache and refresh your screen! It's a cache issue!

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.

[gus]

Damn it, my mobile hotspot is about to die. If I reconnect under a different wireless I'll for sure lose my spot, won't I?

[Ano]

Work is out in two hours for me. Starting to get ready to get back in the groove of searching for a ticket like last year. I'll get one eventually!

[trilobyte]

I've just got confirmation from the ticket team, the passcode not registered error is a cookie issue. Clear your cookies (or switch browsers, since cookies are browser-specific), you should be set to go.

[Ruleryak]

Burning Man isn't sold out yet.

The main sale isn't even sold out.

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.

[theCryptofishist]

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...

[gus]

I have to pack up my stuff and head home. Thought this would be something easy I could do over lunch but it's going on three hours now. Good luck everybody! I'm going to jump back on the horse from home with hopefully a better outlook.

[sharpstick]

so, anyone know how long it will wait when my turn comes up? do i have to sit here and stare at the screen until it's time? what if i have to pee and it times out?
at least i've been in the queue without crashing for about 30 minutes now.
(i was having problems with firefox and switched to chrome and wasn't able to get in the queue at all. then i switched back to ff and noticed that i had mysteriously been in the queue already, so don't try to use multiple browsers at once!

[tiredofbeingnice]

I for one am quite happy with the ticket system this year.

All you really had to do was follow the directions and be patient.

I liked it better than entering a lottery and wondering if I would get drawn or whatever.

Luck has nothing to do with this one.

[JaRail]

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...

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]

I'm not on widows

[9ah]

Linux, Fishy?

[junglesmacks]

I'm not on widows

That's not what I heard.

[Ruleryak]

It's Command+Shift+Delete on a mac (command key, aka apple key, aka four leaf clover key instead of control) in IE and Chrome. God help your sorry soul if you're using Safari. There's no excuse for that, heh.

[melodiousdirge]

WRONG....It's a cache issue!

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

Thanks for the advice but there's no need to be a twat about it.

[melodiousdirge]

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.

[Ruleryak]

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.

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.

[theCryptofishist]

Ah, the biter bit... The snotty remark can cut. I suppose "my machine is fucked up and I can't get anything else on it" isn't enough. Luckily, there's plonk.

[Ruleryak]

Well three hours is just about all the anxiety and negativity I can stand to put myself through. Good luck to everyone!

While I definitely am entirely at odds with Trilo's opinion of InTicketing's piss-poor attempt at selling tickets year after year, one thing I learned to trust him on last year was that no matter what happens today, all of us that are dedicated to going this year absolutely will find a way. Whether it's a ticket in a month, three months or a week before the gates open we will make it. So at least there's no worry in that department this time around

[topclass]

Hi

My experience buying tickets for bm, been sitting watching blue and while bar for over 3 hours now. Getting late in the UK

I did have the “Your passcode is not registered.” horror but back at the bar in another browser, however I am concerned that the ip changes at every refresh, which feels like am going the back of the queue. My browser accepts cookies and have even tried on different devices, can any one in the know or who has been successful on this comment on the ip refresh thing.

Thanks

[gus]

My buddy got his and he was one of the early noon attempts. I just got back in the queue after a horribly frightening 'no tickets available' page that mysteriously disappeared.

[Hayseed]

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.

[whynotnow29]

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 would think it goes by pc ip address, not your browser

[melodiousdirge]

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.

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.

[melodiousdirge]

From Last year but feeling appropriate at the moment

[Hayseed]

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.

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.

Your words sound of logic and intelligence....I think I will stay put.