Carbon0-Games/carbon0-web-app

Unexplained 404 on Index.html

UPstartDeveloper opened this issue · 1 comments

UPstartDeveloper commented

Hey team,

We have encountered a 404 error when loading the home screen (aka the / path) of the Django site. Currently the cause of this error is unknown. I will paste the error message from the Chrome Inspect tool's console below, please help us out if you know what this means.

Error Message

base.js:1550 GET https://r5---sn-p5qs7nek.googlevideo.com/videoplayback?expire=1603313993&ei=6UyQX-vtLOrr8gTm-46gAg&ip=64.30.94.41&id=o-AAbIqadU2RuqH9IKsTCbYMIUA8wlzIRuvwi_Gu4UPFap&itag=135&aitags=133%2C134%2C135%2C136%2C160%2C242%2C243%2C244%2C247%2C278%2C298%2C302&source=yt_otf&requiressl=yes&mh=SM&mm=31%2C29&mn=sn-uvfopn2-cvne%2Csn-p5qs7nek&ms=au%2Crdu&mv=m&mvi=2&pcm2cms=yes&pl=24&initcwndbps=1701250&vprv=1&mime=video%2Fmp4&otf=1&otfp=1&dur=0.000&lmt=1578890863547100&mt=1603292336&fvip=5&keepalive=yes&fexp=23915654&c=WEB_EMBEDDED_PLAYER&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cotf%2Cotfp%2Cdur%2Clmt&sig=AOq0QJ8wRQIgeOeeFNgeX0OwXEcn31qErFYuSJl7RCxCg3Eb14WJsiwCIQCWNKovisqIVzNx41lPQ3gwJ44fucZRvM303fX8HCO0vA%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhAKN072XnWXQRky_5by2bD6iTFDhB14YyccwdCwfgVzQLAiEA03L4ygFKEggt8dsaUVZjgmgw-K2YXsC_WC5iGllwOnw%3D&alr=yes&cpn=PiFr2MYMCnbRlhAp&cver=20201020&fallback_count=1&rn=34&rbuf=0 404

Other details
The error currently isn't causing anything on the UI to be messed up, so my hunch is this error has to do with one of the 3rd-party APIs we have integrated into any of the following HTML files:

  1. carbon0/templates/base.html --> base HTML template
  2. carbon0/templates/index.html --> main HTML template used for this view. It integrates the Mixpanel Javascript SDK at the top.
  3. carbon0/templates/partials/intro_video_player.html --> partial template that integrates the YouTube iFrame Player API.

Any help is much appreciated!

UPstartDeveloper commented

I think was solved a while ago and I forgot to update the issue. Closing for now, 99% sure it was just some small issue.