Match history still broken

Arsinik··1 votes·569 views

How long until this is fixed it is always down it seems like.

5 Comments

EndlessSorcerer2 votes

AFAIK, it seems to be an issue with the cookie in the browser.

I'd recommend clearing your cookies or trying a different browser.

Arsinik1 votes

Tried both still hasn't worked in about 2 weeks.

Modi1 votes

Open up the match history and take a look at the developer tools (F12 in most browsers, or ctrl+shift+i in windows, cmd+shit+i in mac) see if it is similar to this issue.

Arsinik1 votes

Looked at the other thread then looked at my errors that doesnt seem to be the same problem.

VM33:8 X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>. codex.js:1 Uncaught SyntaxError: Invalid or unexpected token http://riot-dradis-assets-oregon.s3.amazonaws.com/dradis-0.5.0-prod.min.js Failed to load resource: the server responded with a status of 403 (Forbidden) analytics.min.js:4 Uncaught ReferenceError: Dradis is not defined at analytics.min.js:4 at HTMLScriptElement.<anonymous> (analytics.min.js:1)

Those are the errors on my side.

Arsinik1 votes

That doesnt seem to be the problem on my end.

VM33:8 X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>. codex.js:1 Uncaught SyntaxError: Invalid or unexpected token http://riot-dradis-assets-oregon.s3.amazonaws.com/dradis-0.5.0-prod.min.js Failed to load resource: the server responded with a status of 403 (Forbidden) analytics.min.js:4 Uncaught ReferenceError: Dradis is not defined at analytics.min.js:4 at HTMLScriptElement.<anonymous> (analytics.min.js:1)

These are the errors that are showing up on my side.

More from Report a Bug

More by Arsinik