Ticket tips and Tricks for 2025 festival

[Suprefan]

20 minutes ago, dotdash79 said:

This would be possible to game with loads of registrations but with better checks on setting up registrations and managing them  this would help.

 

Maybe tie a registration to a mobile number, and have 2FA.

 

youre also giving this more to younger punters cause older attendees arent always the most trch savvy. Who says theer wont be a giant glitch that gives a ton of errors on verifying and youve got a giant swath of people on the outside while the ones who avoided it are holding tickets. And youre going to make See have to send verifications to global phone numbers? Like the person in Nepal has to get an sms. Think about it.

[Skip997]

8 minutes ago, Crazyfool01 said:

cameras mate not facial recognition 

Thanks for the clarification. 
 

Cameras or facial recognition it’s all OTT surveillance. Any way it’s possible to avoid the one on the self serve tills 

[dotdash79]

4 minutes ago, Suprefan said:

youre also giving this more to younger punters cause older attendees arent always the most trch savvy. Who says theer wont be a giant glitch that gives a ton of errors on verifying and youve got a giant swath of people on the outside while the ones who avoided it are holding tickets. And youre going to make See have to send verifications to global phone numbers? Like the person in Nepal has to get an sms. Think about it.

 

Verification on registration then a personalised queue link for the sale. Only one link per registration, would help limit the number of connections.

 

I think it's the first time Glastonbury would have any idea how many sessions were trying to connect, taking that down to the registration level would give an idea of the numbers actually trying.

[Crazyfool01]

1 minute ago, Skip997 said:

Thanks for the clarification. 
 

Cameras or facial recognition it’s all OTT surveillance. Any way it’s possible to avoid the one on the self serve tills 

dont disagree on that 

[dotdash79]

14 minutes ago, Suprefan said:

Like the person in Nepal has to get an sms

Nepal has some of the best mobile coverage in the world, just an FYI.

[Suprefan]

12 minutes ago, dotdash79 said:

 

Verification on registration then a personalised queue link for the sale. Only one link per registration, would help limit the number of connections.

 

I think it's the first time Glastonbury would have any idea how many sessions were trying to connect, taking that down to the registration level would give an idea of the numbers actually trying.

 

it still wont matter. You are severely underestimating how ahead the other side is. Unless you think like them, you wont have a leg up. Theyre really only concerned about resale security. Other than that they just want to sell all their tickets one way or another. Why dont they do something about the free labor. Oh right, they know thats how they stay afloat, so they let an extra 50,000 people onsite to make it happen for the rest who paid.

[justanotheronethen]

34 minutes ago, steviewevie said:

f**kface 

Morning

☕️

[Suprefan]

14 minutes ago, dotdash79 said:

Nepal has some of the best mobile coverage in the world, just an FYI.

 Just saying. You still have to have the infrastructure to send out the messages everywhere, regardless of coverage. If that fails then you got issues. Everyone now wants to add more layers to this and you have a larger margin for errors to arise.

[codeblue]

10 hours ago, WobblyPants said:

Not necessarily hackers. 
 

these links are acquired by making thousands of requests to the waiting room, harvesting queue ids and then polling queue it with the IDs. You then pluck out the ‘direct link’ for the IDs which are at the front of the queue. 
 

They’re legitimate unique queue sessions obtained by a bot. 
 

Some bot owners will then sell these, but this person obviously had their fill and decided to dump them all on Reddit for anyone to use (you can only use each one once). I suspect they wanted to make a point about how easy this new system is to game for bot owners/developers who want to crack it. 
 

This system was particularly weak. 

Was this on the main glasto subreddit? I'm on there a lot and didn't come across this at all.

[GlastoEls]

13 hours ago, Pipine said:

Sounds like it wasn’t as smooth technically as Thursdays sale.. people being routed to random pages, access denied in submission a lot.. spurious sold out messages.

Now that the dust has settled, it’s still really weird I got the front of the queue and was directed to a random “Local tickets have now sold out” message, which I first thought meant I was too late, but then saw g19 in the URL and it wasn’t the current type pages.

Thank goodness - after a bit of backwards (to the queue) and forwards (which took me back to g19) a big deep breath and entering “Glastonbury.seetickets.com” (removing the g19 event stuff) took me to the expected deposit screen (so clearly I was in an active session) and it was easy from there. 

Strange.

Edited 57 minutes ago by GlastoEls

[Flighty Zoo]

Still bummed out about not getting tickets. Have had a rough year.

 

could anyone explain why my chrome was progressing so much quicker (I was only a few bars away from getting through at 9.30!) than my Safari browser on laptop connected to WIFI, and my Microsoft edge and opera browser on my phone and iPad (connected to 4G respectively)? Partner was on same WIFI on their laptop and had one browser and told them to shut theirs down when it looked like I was progressing rather smoothly (they were only on two bars the whole time). Was I just put in the close, but no cigar section of the queue for that specific Queue-it ID? Would love to know theories, thoughts, speculations ahead of resale. 
 

Only thing I could think of is that *just before* the timer hit zero on Chrome, I hit refresh… and sporadically refreshed out of impatience (F5 trigger was kicking in from last four sales that I’ve gotten tickets). 
 

well done to those who got tickets and are returning, and for all the newcomers too. It’s not down and out for me yet but the anecdotal evidence from online and from friends of friends of friends etc of people who could backspace and get multiple tickets is just making me deflate like Michael Eavis watching Chris Martin yet again. It feels like 2019 and 2022 ticket days were relatively easy compared to the horror of last year and the admittedly more stable but equally frustrating process today. 

Edited 12 minutes ago by Flighty Zoo

[bob323]

1 minute ago, Flighty Zoo said:

Still bummed out about not getting tickets. Have had a rough year.

 

could anyone explain why my chrome was progressing so much quicker (I was only a few bars away from getting through at 9.30!) than my Safari browser and my Microsoft edge and opera browser on my phone and iPad (connected to 4G respectively)? Partner was on same WIFI on laptop and had one browser and told them to shut theirs down when it looked like I was progressing rather smoothly. Was I just put in the close, but no cigar section of the queue for that specific Queue-it ID? Would love to know ahead of resale. 
 

Only thing I could think of is that *just before* the timer hit zero on Chrome, I hit refresh… and sporadically refreshed out of impatience (F5 trigger was kicking in from last four sales that I’ve gotten tickets). 
 

well done to those who got tickets and are returning, and for all the newcomers too. It’s not down and out for me yet but the anecdotal evidence from online and from friends of friends of friends etc of people who could backspace and get multiple tickets is just making me deflate like Michael Eavis watching Chris Martin yet again. It feels like 2019 and 2022 ticket days were relatively easy compared to the horror of last year and the admittedly more stable but equally frustrating process today. 

I luckly got in twice on two separate PCs, the back button trick to get multiple ticket for me did not work, and i tried it quickly. no idea why that rumour exists

 

every session or queue id had a random chance of getting in sooner or later - the browser was not a factor. pressing F5 when i pressed it didn't do much. although i got a bad IP error message when i got frustrated and press it too much - which was game over for that session

 

the shutting down, no idea, that sounds like a operating system thing, nothing to do with seetickets