Access Denied

[dulcificum]

So what was the deal with this? I got through the queue pretty quickly then was met with a brick wall stuck behind this for 15 mins. Refreshing just gave a different reference number.

 

Eventually it stopped and I got through to choosing coach times but then got "all tickets allocated" with sporadic options to choose other cities for 30 mins.

 

Why did I get the access denied and how can I avoid it next time?

[dulcificum]

Nobody else got this after getting through the queue?

[TigerTom]

I had this and had to reload the last page as one of my reg numbers wasn't correct, ended up getting through again with no issue.

[Helsbels]

4 hours ago, dulcificum said:

So what was the deal with this? I got through the queue pretty quickly then was met with a brick wall stuck behind this for 15 mins. Refreshing just gave a different reference number.

 

Eventually it stopped and I got through to choosing coach times but then got "all tickets allocated" with sporadic options to choose other cities for 30 mins.

 

Why did I get the access denied and how can I avoid it next time?

Did you have more than one browser open?

[dulcificum]

19 hours ago, Helsbels said:

Did you have more than one browser open?

Had 1 chrome tab and 1 firefox tab on 1 IP. It stopped after a while though.

Edited November 15 by dulcificum

[dulcificum]

19 hours ago, TigerTom said:

I had this and had to reload the last page as one of my reg numbers wasn't correct, ended up getting through again with no issue.

How long did it last?

[secondhandsausagedog]

ahh that's devastating,  looks like you were fine on the queue-it/akamai side but when you actually got through to seetickets it didn't like something. Do you get any errors when browsing see tickets at all?

Edited November 15 by secondhandsausagedog

[Alvoram]

29 minutes ago, secondhandsausagedog said:

ahh that's devastating,  looks like you were fine on the queue-it/akamai side but when you actually got through to seetickets it didn't like something. Do you get any errors when browsing see tickets at all?

Look at the error message, Akamai did not like something... Edgesuite.net is Akamai security.

My guess is that they do some of their checks after the queue, and whilst you think you're ok in the queue, you could be wasting your time as you may get rejected after anyway... 

[dulcificum]

3 hours ago, secondhandsausagedog said:

ahh that's devastating,  looks like you were fine on the queue-it/akamai side but when you actually got through to seetickets it didn't like something. Do you get any errors when browsing see tickets at all?

No, no issues at all apart from that. And it went away after a while. I did leave it for 3-5 mins and it was still like that.

 

Where does Akami come in the flow?

 

My understanding is that you are on Queue-it infrastructure in the queue then get handed over to Glasto servers once you reach the front.

 

The weirdest thing was that the same session was fine later but too difficult playing departure city musical chairs at that point...

 

(and the other surprising part is I didn't hear about many other people with this issue)

Edited November 15 by dulcificum

[secondhandsausagedog]

9 minutes ago, dulcificum said:

No, no issues at all apart from that. And it went away after a while. I did leave it for 3-5 mins and it was still like that.

 

Where does Akami come in the flow?

 

My understanding is that you are on Queue-it infrastructure in the queue then get handed over to Glasto servers once you reach the front.

 

The weirdest thing was that the same session was fine later but too difficult playing departure city musical chairs at that point...

 

(and the other surprising part is I didn't hear about many other people with this issue)

So Akamai is the name of the company who provide the servers / edge services for queue-it but I think they also now do some stuff for the general See site as well. I might be wrong. 

What browser was you using?

Edited November 15 by secondhandsausagedog

[dulcificum]

2 minutes ago, secondhandsausagedog said:

So Akamai is the name of the company who provide the servers / CDN for queue-it but I think they also now do some stuff for the general See site as well. I might be wrong. 

What browser was you using?

This was on a Chrome tab.

[Alvoram]

19 minutes ago, dulcificum said:

Where does Akami come in the flow?

 

Every stage of that flow is routed back through the Akamai edge connector. 



Hence why I think this block occurred after the user had got to the front of the queue, Akamai then found something it didn't like. 

[MilkyJoe]

8 hours ago, dulcificum said:

 

 

(and the other surprising part is I didn't hear about many other people with this issue)

 

There were a quite a few people reporting this.

[dulcificum]

12 hours ago, Alvoram said:

Every stage of that flow is routed back through the Akamai edge connector. 



Hence why I think this block occurred after the user had got to the front of the queue, Akamai then found something it didn't like. 

Are we thinking a fingerprinting issue? 

[Alvoram]

21 minutes ago, dulcificum said:

Are we thinking a fingerprinting issue? 

I'm thinking it blocked you due to you using two browsers on the same IP, probably with the same fingerprint. But I honestly have no idea. Beyond what I've already posted, (some personal cloudflare zero trust experience) I have very little knowledge and experience in these kind of things. 

The fact you eventually got through is interesting though. I have a number of ideas of why that might be, going around my head, but they're all just baseless speculation, and nothing more. Did it let you through when the other session idled out? Did you brute force your way through with refreshes? And many more ideas, but I genuinely have no clue really, I'm just speculating. 

[GhostOfMaurice]

Sounds like complete and utter bobbins, that.

[JayBoogie]

Buying for friends this morning, we got in but were booted out for suspicious activity/IP stuff. Didn't have multiple tabs or anything, four devices on the same wifi though...lesson learned I suppose

[Dan190984]

We got access denied. Couple of back and try agains and we were through

[phil2005]

I got through the queue, entered the reg details and got this access denied message. Clicked back and resubmitted, maybe 15-20 times over the course of several minutes with no luck, and then finally when I had pretty much lost hope it worked and took me to the payment screen. 
 

still waiting for my confirmation email so not fully chilled about it yet. 

[Aragorn]

Same thing for the person who booked mine, they eventually got through and paid after it said sold out, so presumably the system allocated tickets and it was just a case of getting in 

[MEGABOWL]

I got that screen. I had three Chrome tabs open with different profiles logged in. All went at different speeds. The first one got through but I hit that message. So I shut the other two tabs and resubmitted a couple of times and it worked.

[barcelonista1899]

I managed to get through for some friends today. Had the access denied page after entering the reg details several times. Clicked back and resubmit until eventually it went through.

 

 

[Cooter]

Yep, same here.

[phillyfaddle]

2 hours ago, barcelonista1899 said:

I managed to get through for some friends today. Had the access denied page after entering the reg details several times. Clicked back and resubmit until eventually it went through.

 

 

2 of my group had that error at payment stage. They knew to click back, then resubmit and the payments were then processed fine. Wonder how many got caught out by this glitch? 

[Alvoram]

I had the access denied page too, few refreshes, presses of the back button, and eventually got through, terrifying.

But I knew nothing was wrong with that device, as it was a clean single browser, single tab, and it's own connection device, so I figured it was just a server load issue.