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 14 hours ago 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 13 hours ago 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 10 hours ago 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 9 hours ago 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.