Jump to content

ticket tips and tricks Glastonbury 2024 resales


Crazyfool01

Recommended Posts

3 hours ago, parsonjack said:

Just catching up on this....

Question 1 - As far as we can determine the system works basically as you suggest, where requests from potential customers are directed in turn via load balancing technology to a number of booking engine servers that allocate sessions if/when available or present the 'busy' page if not.  *IF* it was possible to bypass load-balancing and direct requests to specific servers then you could potentially fire off huge amounts of requests per second by scaling up browsers and devices as you suggest, and yet stay within the 60/minute limit.  The issues here are that a. we don't fully understand whether the rate limiting is via IP, device, a combination of the 2 or otherwise, b. there's no easy way to bypass the load-balancing, c. there are no guarantees that using multiple browsers on a single device contributes to the limiting in the way multiple tabs on same browser does, d. a 1/second refresh rate is probably too quick to know if you have a session before it fires again, and e. it would be nigh impossible to mange such a set up in practice.  

Question 2 - Correct. Load-balancing will remove a degree of risk where multiple devices share the same external IP, but to fully eliminate this the rate-limiting is almost certainly based upon a combination of IP and device identity ie MAC address.  We don't know for sure though.

Question 5 - No/Yes  Breaching the 60/minute limit automatically presents you with the same 'busy' page as when the server is genuinely busy. Subsequent refreshes will keep giving you that 'busy' page until your refresh rate falls below 60/minute.  The rub here is that as it's the same 'busy' page in both circumstances you can't be sure if you have it because the system is genuinely busy, or you have breached the limit.

Good Man. Thanks for this. Most interested on 1 here. Am I right in saying there is a risk / reward angle on multiple browsers then?

So if I had say 3 browsers running auto-refresh of 1 per second and I am lucky enough that they all allocated different booking engine servers due to the load balancing technology, I would end up with 180 refreshes per minute?

However we have no way to determine which engine server we get sent to - so those 3 browsers could go to the same one, in which case you will easily breach the limit.

So if we assumed there were 5 different booking engine servers and i wanted to take full risk - I would go for 300 per 60 seconds. However, if i wanted to play it safe I would just do the normal 60 (on one browser). Somewhere in the middle would be 150. Your choice is where you want to sit on the risk spectrum?

Does any of that make sense?  

 

 

Link to comment
Share on other sites

Just read through this thread & panicking for next week - eek!

What is the general consensus when it comes to setup on the day, multiple browsers and spamming F5?

Are people going to try use the links shared on this thread or click the link through See Tickets? Would be interesting to see what people are planning for the day. 🙂

 

Link to comment
Share on other sites

1 hour ago, vardyvarvar said:

It’s funny how anecdotally the posters on here get through in the last few seconds before sell out. I think that’s a testament to our perseverance! Too many fairweather wannabees that are on Twitter complaining about how difficult it is after 10 mins.

Lots will give up when they see sell out - leaving cart drops for us!

Link to comment
Share on other sites

I had a mare in the last resale and completely lost all focus … on the day we were doing well and were down to the last few groups on the spreadsheet  and the group I’d put my mates and my ticket buyer from the bus sale had someone in it who’s reg got used elsewhere and caused the blocking issue … at that stage I lost the plot and wasn’t able to focus or operate the computer for the next half hour . Fortunately the errant reg got deleted and those tickets were secured at the end … my . Don’t want to go through that again … I’m bad enough with the shakes as it is 

  • Like 1
  • Upvote 1
Link to comment
Share on other sites

1 hour ago, mpdow2 said:

Good Man. Thanks for this. Most interested on 1 here. Am I right in saying there is a risk / reward angle on multiple browsers then?

So if I had say 3 browsers running auto-refresh of 1 per second and I am lucky enough that they all allocated different booking engine servers due to the load balancing technology, I would end up with 180 refreshes per minute?

However we have no way to determine which engine server we get sent to - so those 3 browsers could go to the same one, in which case you will easily breach the limit.

So if we assumed there were 5 different booking engine servers and i wanted to take full risk - I would go for 300 per 60 seconds. However, if i wanted to play it safe I would just do the normal 60 (on one browser). Somewhere in the middle would be 150. Your choice is where you want to sit on the risk spectrum?

Does any of that make sense?  

 

 

You may as well use multiples of 60 - there's no mid-point for an uneven number of servers.

Definite potential for risk / reward.  If you saw two different browsers behaving the same (e.g. all getting the hold for 20 second page at the same time) then you could probably conclude that they're hitting the same server and just kill one of them.  That's a big if though - more likely (on ticket day) is that you'll see lots of white / blank screens due to not getting any responses back from any of the servers.  Does that mean that your not getting through, or are they still taking note of your 120/180 attempts only that you're not getting the feedback?

Link to comment
Share on other sites

Reading this thread honestly has me baffled as to how I’ve managed to get tickets on the last 2 general sales with just one tab on one device and manually refreshing. I’ve decided that I won’t try and fix what isn’t broken and just carry on with my method lol. Good luck everyone! 

  • Like 2
  • Upvote 2
Link to comment
Share on other sites

46 minutes ago, p.pete said:

You may as well use multiples of 60 - there's no mid-point for an uneven number of servers.

Definite potential for risk / reward.  If you saw two different browsers behaving the same (e.g. all getting the hold for 20 second page at the same time) then you could probably conclude that they're hitting the same server and just kill one of them.  That's a big if though - more likely (on ticket day) is that you'll see lots of white / blank screens due to not getting any responses back from any of the servers.  Does that mean that your not getting through, or are they still taking note of your 120/180 attempts only that you're not getting the feedback?

Quite.  There's also the risk around session cookies and the confusion it can cause to the back end servers where multiple tabs/browsers are being used on the same device.

GF (Emily I think...) have warned against this in the past, and I've no reason to doubt that it's been said for anything other than good advice where it comes to maximising your chances.

Link to comment
Share on other sites

59 minutes ago, parsonjack said:

Quite.  There's also the risk around session cookies and the confusion it can cause to the back end servers where multiple tabs/browsers are being used on the same device.

GF (Emily I think...) have warned against this in the past, and I've no reason to doubt that it's been said for anything other than good advice where it comes to maximising your chances.

Thanks @parsonjack@p.pete  On the cookies point, is that not solved by having Private mode on all the browsers you try?

It sounds like you guys think the risk is too high which I think is right. You would rather 100% know that you have 60 chances per second than be in the hands of the gods by trying to get to 100 or something. And we don't have a clue how many servers there are - imagine its a few to manage traffic but who knows

So in summary safe approach:

- 1 browser refreshing 60 times per minute

- 1 4G phone refreshing 60 times per minute

Dangerous but potential reward approach:

- Private Browser 1 - refreshing 30 times per minute

- Private Browser 2 - refreshing 30 times per minutes

- Private Browser 3 - refreshing 40 times per minute

- 1 4G phone refreshing 60 times per minute

Extreme Danger but massive reward approach:

- Private Browser 1 - refreshing 60 times per minute

- Private Browser 2 - refreshing 60 times per minutes

- Private Browser 3 - refreshing 60 times per minute

- 1 4G phone refreshing 60 times per minute

Does that make sense? 

At the end of the day control the controllable (spreadsheets, organisation, no drinking night before, try post sold out, have enough credit / funds, etc etc) and the rest is luck. 

Link to comment
Share on other sites

11 minutes ago, BlueDaze said:

This is the first time that i can remember GF putting so much 'preparedness' info on the website https://www.glastonburyfestivals.co.uk/glastonbury-2023-tickets-on-sale-in-november/

Note the 'Be reasonable and considerate' section near the end.....

 

They published the same document in 2020 😀

https://www.glastonburyfestivals.co.uk/full-2020-ticket-info/

Link to comment
Share on other sites

Just for people who can't be bothered scrolling through the whole thing (which included me so apologies for my dumb questions which had already been answered@p.pete @parsonjack

- 1 browser - refresh 60 times per minute

- 1 4g phone - refresh 60 times per minute

If you use multiple browsers you may increase your chances but it comes at a huge risk. People have tested it on here and on balance it appears a risk not worth taking. 

  • Upvote 1
Link to comment
Share on other sites

5 hours ago, CJB said:

Reading this thread honestly has me baffled as to how I’ve managed to get tickets on the last 2 general sales with just one tab on one device and manually refreshing. I’ve decided that I won’t try and fix what isn’t broken and just carry on with my method lol. Good luck everyone! 

In all honesty this is the best method, everything else just causes distractions

  • Like 1
Link to comment
Share on other sites

31 minutes ago, CurlyPutz said:

this is the shoddiest part

'Unfortunately, See Tickets has not offered a free-of-charge identity protection service for the impacted individuals, so exposed customers were left on their own to deal with the consequences of the security breach.'

proper bad, even if it was like 10 customers they deserve to be supported from SeeTickets own cock up

Link to comment
Share on other sites

15 hours ago, mpdow2 said:

Thanks @parsonjack@p.pete  On the cookies point, is that not solved by having Private mode on all the browsers you try?

It sounds like you guys think the risk is too high which I think is right. You would rather 100% know that you have 60 chances per second than be in the hands of the gods by trying to get to 100 or something. And we don't have a clue how many servers there are - imagine its a few to manage traffic but who knows

So in summary safe approach:

- 1 browser refreshing 60 times per minute

- 1 4G phone refreshing 60 times per minute

Dangerous but potential reward approach:

- Private Browser 1 - refreshing 30 times per minute

- Private Browser 2 - refreshing 30 times per minutes

- Private Browser 3 - refreshing 40 times per minute

- 1 4G phone refreshing 60 times per minute

Extreme Danger but massive reward approach:

- Private Browser 1 - refreshing 60 times per minute

- Private Browser 2 - refreshing 60 times per minutes

- Private Browser 3 - refreshing 60 times per minute

- 1 4G phone refreshing 60 times per minute

Does that make sense? 

At the end of the day control the controllable (spreadsheets, organisation, no drinking night before, try post sold out, have enough credit / funds, etc etc) and the rest is luck. 

I wish I'd never seen this 😭 We normally have several browsers/devices on the same wifi connection, I didn't know anything about the 60 times a minute thing and its never been an issue, but now I'm paranoid about it...

Link to comment
Share on other sites

1 hour ago, CurlyPutz said:

Is there anything i should do? looks like this might be a US thing maybe (hopefully). bought tons through see

10 minutes ago, JoeyT said:

No sings of life in the festival whatsapp group as of yet.

When should I give it a poke?

asap! ours has been chatting (well me at people) for a good few weeks now

Link to comment
Share on other sites

Does the coach ticket location have to correlate with your address? Bunch of mates will be in the area prior and after so are looking to get coach from Bath but we are from all over the country.

 

What is this 'Rank: Newbie' all about? Have been on here since 2002 lol Admittedly not much in recent few years.

Edited by Breeze
Link to comment
Share on other sites

Just now, Breeze said:

Does the coach ticket location have to correlate with your address? Bunch of mates will be in the area prior and after so are looking to get coach from Bath but we are from all over the country.

It doesn't.

I know of people who live 10 miles from the festival site who have traveled to Manchester in order to get the coach back!

  • Like 1
Link to comment
Share on other sites

  • Crazyfool01 changed the title to ticket tips and tricks Glastonbury 2024 resales

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.



×
×
  • Create New...