Ready for Main Sale!!!

[robsclone]

Mine keeps timing out or losing connection to server, also - BUT!:

I've been right-clicking and "reload frame" (chrome) on the center part, and I haven't had to re-enter my code or anything and it still refreshes every 60 seconds with "Grettings! You're in the queue..."

So maybe give that a shot if you (maybe?) don't want to lose your place?

here's to hoping...

[BurnerBunny]

kicked again

does chrome have a setting or something that only allowes auto refreshing for so long?

[JaRail]

My gf had issues in the billing pipeline. Something about trying to use her canadian billing address and wanting to have her tickets mailed to my house in the US for the cheaper postage. So that screwed up and she got booted back to the queue. Her queue time is now 12:15, which is pretty lame considering she was there right at 12 and already to the front of the line. I hope there aren't too many people losing their spot due to billing pipeline issues. I really don't think you should have to requeue to restart the billing pipeline. There's a TON of text you need to read. It takes a while. If it crashes and you need to restart.. that's really really crappy and NOT the user's fault! A major gap in their ticket pipeline IMHO.

[Undecided]

3rd time: The connection to queue.inticketing.com was interrupted.

[VultureChow]

Hey, just thought I'd put this out there, and I could be wrong about the whole thing.

My browser timed out after my number came up in the queue. Instead of reloading, I hit back, and it took me to the order screen where I had to redo the captcha, but it didn't make me get back in line. Using Firefox for the record.

Still processing my order in the browser, but I already got the email confirmation of the purchase.

[clocksnmirrors]

timed out.

refreshed like four times.


finally got requeued.....


i'm getting a bit nervous in spite of the tequila

[VampireKitten]

ACK It put me back in the queue after the Inticketing crash... what is this?! I thought I wasn't going to lose my place in line

[gus]

I've now gotten booted about 3 times! I thought it was my connection (sitting in my car with laptop running off a hotspot) but it seems we're all having this issue!? Boo!

[illy dilly]

The connection was reset.
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.

This is the error I keep getting out of Firefox!


DING DING DING!!! WE HAVE A SERVER CRASH!!!
At least this year they made it 40 Minutes!!!!!
\HAHAHA

[Ano]

I have now officially made it through the line twice, only to have my order die when I click "process." I wonder how many more heart attacks I can have today.

[melodiousdirge]

I've "Lost connection" with queue.inticketing.com about a dozen times now and each time it's taking longer to get back in line.

Oh and now I just got a message stating my passcode is not registered (It's worked the past dozen times). Glad some people are actually making it through but this is starting to worry me.

[clocksnmirrors]

my connection has been reset multiple times


but refreshing keeps reconnecting me without having to reenter my code....... so yea


ps : firefox

[Sprok da Sow]

Skyhawkecks, I was at the same page. After about 15 minutes, I took a chance and refreshed the page. It tried to draw the same page, but couldn't even render the whole thing. I refreshed a couple more times. Eventually I came to the credit card order entry screen.

After I filled that out, it timed out again. Then again. And I refreshed again. I had to fill out the credit card page 3 times.

Finally it worked. I got an order confirmation page and immediately got the confirmation email in my inbox. It appears that ll those refreshes did not put me back at the beginning of a queue at any stage of the process. It appears that filling out the order form more than once and refreshing several times did not duplicate my order. (I got only one confirmation email and web page.)

[melodiousdirge]

The connection was reset.
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.

This is the error I keep getting out of Firefox!


DING DING DING!!! WE HAVE A SERVER CRASH!!!
At least this year they made it 40 Minutes!!!!!
\HAHAHA

I don't think the server crashed. I can ping it OK and visit queue.inticketing.com just fine in another window but my ticketing window is having serious issues.

[Jenifersteppat]

Using Firefox. One crash, hit refresh and bumped me by a couple seconds - GOT OUR TIX! Good luck everyone! Wow, what a different experience from getting tix through STEP last year this is effin' awesome!! XOXO

[canexplain]

Same here on the connection ....grrrrrrrr****

[maxtov]

Getting "connection timed out" several times already - refresh, enter code again, wait, rinse, repeat.
Every next year the hopes of making it work right come back from the ashes of previous one only to be put to rest yet again... WTF?

[clocksnmirrors]

i queued at 25 seconds in. can't believe i haven't got a tix yet......



argggggh

[Ruleryak]

I was in at 12:00:58. Anyone after that time have a ticket yet? I timed out and refreshed at 12:16 and had to re-enter my code (which better damn well not mean I was put to the end of the line at that piont) - hope it's not a repeat of 2010 when I had to stay at work an extra 4 hours because I foolishly assumed that three hours to process an order would be enough time.

[TT120]

I got in at 27 seconds and no love here. The server has crashed on me many many times. So far, I'm still in the queue, I think.

[VampireKitten]

I take back what I said... all these crashes are nonsense. I really hope it didn't lose my spot.

[nighthawk]

I've been in queue since 12:00:17, haven't gotten to the ticket purchase page yet.
The connection has timed out twice so far. Since people with a later timestamp than me have purchased tickets, the place-in-queue holding mechanism apparently doesn't work.

Inticketing's tagline: "enhance the experience"
Yeah.

[gus]

i queued at 25 seconds in. can't believe i haven't got a tix yet......

argggggh

I got in at 12:08 and have been booted multiple times. Still waiting.

[melodiousdirge]

Your passcode is not registered.

You have reached our limit for trying. Please contact customer support for more information.

^^ That's all I'm getting now. What the hairy fuck?

[skyhawkecks]

Skyhawkecks, I was at the same page. After about 15 minutes, I took a chance and refreshed the page. It tried to draw the same page, but couldn't even render the whole thing. I refreshed a couple more times. Eventually I came to the credit card order entry screen.

After I filled that out, it timed out again. Then again. And I refreshed again. I had to fill out the credit card page 3 times.

Finally it worked. I got an order confirmation page and immediately got the confirmation email in my inbox. It appears that ll those refreshes did not put me back at the beginning of a queue at any stage of the process. It appears that filling out the order form more than once and refreshing several times did not duplicate my order. (I got only one confirmation email and web page.)

Well I'm in the "Greetings!" queue again but now I'm unsure if I should just keep hitting refresh. And the IP number at the bottom right keeps changing, I hope that's not messing with my place in line.

[clocksnmirrors]

I was in at 12:00:58. Anyone after that time have a ticket yet? I timed out and refreshed at 12:16 and had to re-enter my code (which better damn well not mean I was put to the end of the line at that piont) - hope it's not a repeat of 2010 when I had to stay at work an extra 4 hours because I foolishly assumed that three hours to process an order would be enough time.

this is why i am sitting naked on my sofa at home drinking.....

[melodiousdirge]

Your passcode is not registered.

You have reached our limit for trying. Please contact customer support for more information.

^^ That's all I'm getting now. What the hairy fuck?

...and now my GF is getting the same message so I guess plan B of her buying me a ticket is out the window too. Once again I say what the hairy fucking fuck?

[trilobyte]

The servers have not crashed, they are just struggling to keep up with the traffic demands. Every ticket seller has these kinds of issues when high demand events go on sale, unfortunately. Hang in there, keep trying.

melodiousdirge - hopefully you took heed of the error message, if not send an email to ticketsupport@burningman.com regarding your situation (include screen captures/error messages, if possible).

[gus]

Your passcode is not registered.

You have reached our limit for trying. Please contact customer support for more information.

^^ That's all I'm getting now. What the hairy fuck?

...and now my GF is getting the same message so I guess plan B of her buying me a ticket is out the window too. Once again I say what the hairy fucking fuck?

Shit. What a bummer man. I'm sure things will work out but you'll have to deal with grief you shouldn't have.

[JaRail]

Your passcode is not registered.

You have reached our limit for trying. Please contact customer support for more information.

^^ That's all I'm getting now. What the hairy fuck?

...and now my GF is getting the same message so I guess plan B of her buying me a ticket is out the window too. Once again I say what the hairy fucking fuck?

Of the ten or so people I know who were ready to go at 12, I'm the only one who has made it through. I'm lucky and had my email confirmations by 12:03.. But even so, I'm stressing out because I'm running tech support for everyone in my crew. My fb feed is filled with tons of technical people who are having tons of issues.

If the "retry until you get through" strategy starts failing.. wow, that's a major fuck up on a whole new level.