My best tips for ticket day....

[parsonjack]

4 minutes ago, psychology said:

Also tried at work, it's fine unless i am faster than 1 second

Thanks....does the page fire after 30 keystrokes, or after a full 60 seconds?

[psychology]

Just now, parsonjack said:

Thanks....does the page fire after 30 keystrokes, or after a full 60 seconds?

Just checked again, 60 keystrokes, about 30 seconds if I two per second 

[flyleen]

On 9/18/2018 at 2:35 PM, balti-pie said:

Book your own ticket and then go back to book your mates? That’s cold! 

That's arctic! ❄️

[The Other Steve]

18 minutes ago, parsonjack said:

Ok....try it over a second but less than 2 if you can....2 seconds is fine for me but I get it at anything over 35bpm.

Seems fine...just went at 1.5/sec and no issues

[Stretlow]

11 minutes ago, parsonjack said:

Thanks....does the page fire after 30 keystrokes, or after a full 60 seconds?

if you do hit this busy screen what happens then. does it let you back in after a short period or are you screwed?

[psychology]

Just now, Stretlow said:

if you do hit this busy screen what happens then. does it let you back in after a short period or are you screwed?

it goes back after 20 seconds

 

[Zoo Music Girl]

Just now, Stretlow said:

if you do hit this busy screen what happens then. does it let you back in after a short period or are you screwed?

That's what I'd like to know! Is this the busy screen you're on about?

I just got it after refreshing more quickly than once per second. Doing about once per second seemed fine for me, though. 

[Dangertappy]

I'm going to have a metronome going and alternate refreshes on my phone on 4g and laptop on Wi-Fi... of course whilst trying not to poo my pants ? multi tasking!!

[Stu H]

16 hours ago, parsonjack said:

See had 4 IP addresses advertised through DNS and allocated on a round-robin basis (as they still do btw...).  Each of these represents a load-balancer (the actual Web and application servers will be behind these on internal private IP's).  Back then See used an IP range which I think began 194.168.x.x.  On ticket day it was noticed that one of 4 x IP's was actually advertised as 192.168.x.x which would be a simple configuration mistake to make as the 192.168.x.x range is commonly used as a private IP range.  What it meant however was that the 4th load-balancer was not being advertised publicly for use, and by simply adding the correct 194.168.x.x address to Host files it could be specifically resolved to and serviced ticket requests very nicely thankyou....until See spotted the error and fixed DNS,

Fingers crossed the same tech guy is on shift this weekend ?

haha!

[FuzzyDunlop]

I haven't been active on this board too much recently, but over the last few days I have been reading this thread.... 

Thanks for scaring the shite out of me!

Best of luck to everyone tonight. Hopefully I'll be celebrating too on sunday. 

Only going to have my phone, so relying on others really.

 

[Stretlow]

9 minutes ago, psychology said:

it goes back after 20 seconds

 

Ahh not the end of the world then..

[panasonic2011]

So don't want to sound dumb and I've just refreshed page less than 1 second for 30 times and got busy page.  So getting this busy page does this mean I've got back rather than if I slowed the refresh time down I'd still be in with a chance of getting booking page

[The Martini Police]

Can someone please remind me of the structure of the coach ticket page in terms of the user journey? Do you filter by location first and then day (Wed, Thurs?)? Or is it a massive list or combinations? 

Edited October 4, 2018 by The Martini Police

[Sasperella]

2 minutes ago, panasonic2011 said:

So don't want to sound dumb and I've just refreshed page less than 1 second for 30 times and got busy page.  So getting this busy page does this mean I've got back rather than if I slowed the refresh time down I'd still be in with a chance of getting booking page

Do you mean is there a chance of redemption? Yes! I just tried practicing continuing to refresh slowly after getting the busy page and then it goes back to the previous page, but then back to busy page if you again go fast

Have tried it on chrome and safari....chrome seems to upload the page faster. Wondering if i should use that on the day rather than safari. Any thoughts?

[Sasperella]

1 minute ago, The Martini Police said:

Can someone please remind me of the structure of the coach ticket page in terms of the user journey? Do you filter by location first and then day (Wed, Thurs?)? Or is it a massive list or combinations? 

From memory, I think you pick the day first and then the location on the next page. I can't remember what happens if you're in the "wednesday" option and they all sell out while there are some "thursday" tickets remaining though...

[parsonjack]

9 minutes ago, psychology said:

it goes back after 20 seconds

 

You don't need to wait 20 seconds.....F5 as soon as you get it but slow your rate to less than 1 s to be sure you are within the limit and any busy page you get should be a genuine one.

[parsonjack]

16 minutes ago, Zoo Music Girl said:

That's what I'd like to know! Is this the busy screen you're on about?

I just got it after refreshing more quickly than once per second. Doing about once per second seemed fine for me, though. 

That's the puppy.

[mike86]

2 hours ago, parsonjack said:

Ok listen up people.....I've been testing out the refresh rate thing again and it seems that I now get the 'busy' page when I F5 at anything up to a 2 second interval.....and it seems to fire after just 30 keystrokes rather than after 60 seconds.

Now I'll caveat this with the facts that I have been trying this for some time, so there is the possibility that See have clocked me specifically, and I'm also currently on hotel wifi in Thailand (although I get same result with a VPN connection on a UK IP).

Before I cause widespread panic that the F5 rate is now limited to 2 seconds instead of 1 could people out there try this and corroborate or otherwise please?  If we can prove it's not the case then I will have this post removed.

Like I say, may just be me, but let's see if we can be sure of that. It's also possible that See have wound it down ahead of tonight's sale and will lift it back up later....

If you want to ensure you keep a regular F5 rate download a metronome app, set it to 35bpm, and keep in step with that.

Mine is still going to the loading page on the 60th refresh. 

I've been running the page on a 1s refresh for a few minutes and all is working fine. 

[pentura]

6 minutes ago, The Martini Police said:

Can someone please remind me of the structure of the coach ticket page in terms of the user journey? Do you filter by location first and then day (Wed, Thurs?)? Or is it a massive list or combinations? 

Someone please correct me if I'm wrong but when you eventually get through to the booking page you'll see two large 'buttons' essentially.

One for Wednesday Coach package and one for Thursday. You select whichever you want and then you can select location / time and enter reg. details and postcodes. Then you proceed to confirm all details and get to the payment page and then BOOM!

See photo below, obviously this example has Wednesday as sold out.

Edited October 4, 2018 by pentura

[parsonjack]

3 minutes ago, Sasperella said:

Do you mean is there a chance of redemption? Yes! I just tried practicing continuing to refresh slowly after getting the busy page and then it goes back to the previous page, but then back to busy page if you again go fast

?

[Mouseboy11]

17 minutes ago, Zoo Music Girl said:

That's what I'd like to know! Is this the busy screen you're on about?

I just got it after refreshing more quickly than once per second. Doing about once per second seemed fine for me, though. 

I thought this was just the usual holding page...what page are we expecting to see on Sunday if we refresh at a normal rate?

[mufcok]

Just now, Mouseboy11 said:

I thought this was just the usual holding page...what page are we expecting to see on Sunday if we refresh at a normal rate?

So did I but I just tried refreshing myself at a ridiculous rate and got that after a minute or so. Guess we'll fine out later on in the coach sale what we're expecting/hoping/praying to see Sunday

[billum]

I think the problem is that the two 'holding' pages are indistinguishable to the naked eye!

[parsonjack]

1 minute ago, Mouseboy11 said:

I thought this was just the usual holding page...what page are we expecting to see on Sunday if we refresh at a normal rate?

It is.....I'm expecting it to be his one whether it's real or 'fake' cos you've F5'd too fast.

[parsonjack]

Just now, billum said:

I think the problem is that the two 'holding' pages are indistinguishable to the naked eye!

Yep....pretty sure it's the same page.