parsonjack

I use Chrome for all of them. You'll see folks suggesting why splitting across different browsers could give you an edge as they *could* be seen by See as separate sessions and therefore allow you a greater F5 rate but it's mostly anecdotal.

The front page (https://glastonbury.seetickets.com) should be updated with links to either the Coach sales (tonight) or GA tickets (Sunday) at 1800 and 0900 respectively. It almost certainly happens automatically so will likely occur in line with server time. Those links direct to the pages where you put in registration details, which are most likely set to become live just before the front page is updated to redirect to them. There is good theory therefore that if you know the actual registration page URL it might be possible to get a session a second or 2 before 1800/0900......the only barrier being we don't (yet) know the URL.....

Yep.....see second post on this thread. That was from Thailand and haven't tried from within UK but....

Personally.....I will have 3 browsers open on a single device, each refreshing every 4 seconds. That gives the window time to load and cumulatively doesn't breach the 60/min hit limit.

If you're referring to the Chrome 'Easy Auto Refresh' extension then there isn't a keyword option...at least not in the free version. It's no biggie though as you can just stop it should you get a registration page up....and not a problem if it fires again before you stop it as you'll get the page back. Just make sure to stop it before you enter any details as you;d lose those.

Yup....close/reopen the browser might fix it.....if not then clear all your browser cache and cookies, then close/reopen.

c:\windows\system32\drivers\etc\hosts

It's still there. Perfectly possible that even at 0.5 sec rate network congestion is sufficient enough to dump some of your attempts and keep you below the limit. Personally...not risking it.

If you're suggesting using a VPN to give you international IP's then see first, maybe second, post in this thread.

Agreed....there's space in June for it but holding it back makes little sense unless official sellers of the other UK dates (TM and AEG) have insisted on their dates getting priority.

Possible yes...perhaps that's where he might slot in the rumoured Manchester date.....

Highly unlikely imo.......Friday 28th would be a back to back with Netherlands (not happening), and either Sat 29th or Sunday 30th would both leave just 1 night between gigs in other countries which doesn't happen anywhere else on the schedule.

Cardiff, Sunderland or Wembley.....tough choice for me. Even though closest Cardiff is an utter nightmare travel wise, Sunderland is like the other end of the world, and although Wembley is do-able I've never rated the acoustics as being anything special.....

Unlikely tbh. See's set up changed ahead of the April resale and moved from advertising 5 X IPs via DNS to the single Azure IP we still see now. Fully agree though there's little point in adding that IP to a Hosts file....it would only be of any benefit if the DNS service itself failed which is highly unlikely.

Yes.....the https://glastonbury.seetickets.com page will change at 1800 on Thursday to show links to choose between Wednesday or Thursday departures. Once you make that choice you're then into the F5, F5, F5 world before getting the reg details page up 🤞

Pretty much as you describe apart from there is a page after reg details that confirms the names etc of the regs entered....there might be a confirmation tick box on there but otherwise it's proceed to payment. Note that's for GA tickets on Sunday.....Coach tickets obvs has other pages to choose departures etc

The best/safest strategy is to have as many devices as you can on different connections, and therefore different IP addresses eg. 1st laptop on wifi, 2nd laptop on /5G mobile hotspot, 3rd laptop on another 4/5G hotspot etc. The true risk to folks using shared wifi is not fully known but it is likely that separate devices on shared wifi are actually seen as different connections by See (even though using same IP address...) and that the risk of breaching the limit is therefore mitigated. Safest approach is above, or a mix at best.

Your autorefresh will continue to fire unless you stop it manually or are using a tool that can stop when it detects the presence of a particular word on the page returned. In either circumstance it is not a great problem as the registration page will stay with you even if it refreshed for the duration of your 5 minute session. It's important to stop it before you add any reg details though as these would be lost if entered before a further refresh requiring re-entry.

Thankyou for this. I think this corroborates a theory that the rate limiting applied by Seetickets is per IP Address, but isn't an issue for shared wifi as the port number differentiates between connections using the same source IP. It still means that more than 60 hits/minute by a single *device* will breach the limit as the port number remains the same for each request on that https connection.

No. He totally misses out that the hardest part is actually getting to the registration details page at 24 seconds in. What is most likely to happen is that after clicking the first link to buy either Coach or GA tickets you will get the dreaded 'Busy/Queue' page that automatically refreshes itself every 20 seconds. Don't wait, refresh it yourself but be careful not to exceed a refresh rate of 1/second. Assuming you are lucky and get to the registration details page then his other error is suggesting, at 1.04, that you should refresh the reg details page if it hangs. Better advice is to hit 'Back' and then resubmit. Refreshing should keep your session but you will most likely need to re-enter all the details again.....and you don't want to waste time doing that.

All we know for sure is that there is some sort of limiting, in which IP plays a part and seems to be triggered when 60 hits/minute is exceeded. That's not to say it is solely IP based, as that would put folks on shared wifi at a massive disadvantage, so there is something else in play to mitigate that. Best guess is that See's load-balancing plays a part, where hits are shared in turn across See's servers, and in some fashion minimises the chance of a single (shared) IP breaching the limit. It's guesswork, with a bit of fact thrown in, but a limit of some sort does exist. Your setup generates 3.5 hits/second on a single IP.....over 3 times the limit.....there's nothing to prove or disprove that many of the holding pages you see aren't the 'fake' one, but if you've got tickets using it then at least some of your hits must have got through at exactly the right point to nab a free session.

I've not found a way of doing it on native Android.....this app for Android seems to work although there are some annoying ads to wade through. https://g.co/kgs/XZB2xS

As above.... you'll not lose the page if it refreshes but you would likely lose any reg details you might have entered.....not that it would be much I guess.

Yeah...I think you can do that. When I've been testing I only ever get the 'busy' page after the 60th F5....even if I've done 60 in 30 seconds or so. It seems that the 'busy' page then sticks with you until your rate falls back below 60/min, so in theory yes, doing what you suggest should be possible.

No evidence to suggest See detect anything other than a refresh rate of above 60/minute. My recent record.... 2017 Manual 2018 Fallow 2019 Missed out 😥 2020/22 Auto-refresh 2023 Manual It's all anecdotal obviously and it only takes a single lucky F5 to get you the page....but I'm a firm believer in maximising chances by having more than one device trying - where an auto-refresh works as another pair of hands.