>>/146550/
kek
That was because it was a borked connection with the front-end server.
It would have proto'd you hard next had it made it past that step.