Join Game Link Leads to Gibberish (as GM)

Having two problems, half the time when I click on the game name to get to details it tries to launch a download box instead of opening the details page. But more importantly when I click join game, instead of opening my game window its opening a page of html and gibberish. Here`s a sample. Using Chrome on windows 10. 0 HTTP/1.1 200 OK Date: Sun, 29 Jan 2017 00:45:55 GMT Content-Type: text/html;charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Status: 200 OK Cache-Control: no-store, private Content-Security-Policy: script-src 'self' 'unsafe-eval' https://*.googlesyndication.com https://*.doubleclick.net <a href="https://partner.googleadservices.com" rel="nofollow">https://partner.googleadservices.com</a> <a href="https://www.googletagservices.com" rel="nofollow">https://www.googletagservices.com</a> <a href="https://ssl.google-analytics.com" rel="nofollow">https://ssl.google-analytics.com</a> <a href="https://www.google-analytics.com" rel="nofollow">https://www.google-analytics.com</a> <a href="https://ajax.googleapis.com" rel="nofollow">https://ajax.googleapis.com</a> <a href="http://ajax.googleapis.com" rel="nofollow">http://ajax.googleapis.com</a> <a href="https://d3clqjduf2gvxg.cloudfront.net" rel="nofollow">https://d3clqjduf2gvxg.cloudfront.net</a> <a href="https://cdn.firebase.com" rel="nofollow">https://cdn.firebase.com</a> https://*.firebaseio.com https://*.tokbox.com https://*.opentok.com <a href="http://static.opentok.com" rel="nofollow">http://static.opentok.com</a> <a href="http://www.google-analytics.com" rel="nofollow">http://www.google-analytics.com</a> <a href="http://cdn.crowdin.com" rel="nofollow">http://cdn.crowdin.com</a> <a href="https://crowdin.com" rel="nofollow">https://crowdin.com</a> <a href="http://stun.l.google.com" rel="nofollow">http://stun.l.google.com</a> Vary: Accept-Encoding Content-Encoding: gzip Set-Cookie: rack.session=aabb80f2cc9fc8702169cc32ec36a45cd189e55ff87e1067db60d167f22b34e6; domain=.roll20.net; path=/; expires=Mon, 13 Feb 2017 00:45:55 -0000; secure; HttpOnly Server: cloudflare-nginx CF-RAY: 3288aa05ee0a0c35-SEA 3346 ‹�C;X�ì½m›Ó8²�úyï¯&trade;’\’ô L7NÓÀÀ8ÀÌì.O_'VŽí±îÎü÷[U’lÉ–'ÝÍ°,{Îб­—R&copy;Tª*•ªîßxôòäí?_=f³tîÿŸûâc÷gÜqñüL½Ôçâ7c¯œt6ñ—Ç}öÔ‰ãðܦì#{úþ°¥Õ¸?ç&copy;ÃÆaò =j?{|ô؝òÞx‡s~´Ó†ŽÓ¨ÏÿXxgGíô9óÈI½‘ÏÛÖ&¼ÀK=Çï'cLJÛ=vî¹éìÈågÞ˜÷é¡Ç €ˆehé({l5狹^qî\˜¯Ú,p�®ö&trade;ÇÏ£0N èSˉ"Ÿ÷çáȃ?ç|Ô‡ý±a?­ÌÖ’'­råIϝ´ïò”S/´ )÷y4Ö¨9ž9q¡Ä/oŸôïÁ§ûÉ8ö¢”¥Ëˆc½‹tëwçÌo[C˜7&lt;üüúñ//&gt;~ìÐߣ??ué×À&áÑŸ­w ëÖAkäÌAÜwÔ &lt;üÇ“½ó““Çþ­ÉOÿ|ýëù¿Fÿç»ÿ ü±àþÖêÛFGâݏ¡ô§…çBÓɐú6üÀaÁÂ÷åüøéþ–@ÕƘ읞ñiŒTó£É" qux/íÝ?Õ3‹;ðäM:7ÒwÁûîŸgNÌÂ#ü}ô'¿@êJþüôéÃ›wÛï@ƒ~'ÈO½¬ÙTU¥‚;ïߥïcž.bì!üø1í~ê…½¬b÷“üˆ=&copy;—Ÿ�Œ–j±ut„'LGWVÓß½vDçÛ‡áý`àó`šÎÃ[º0ºwáûnʧΟ;ïjÑýóSöªï²vV-{ãA‰w€Ÿ³GNÊ»ƒ)Oq¦;]@TÀÔw'ž.æ0«IÛKà4¤3/váñ,ô\¶M/&gt;}Â1xG¼Óš9ë´ÛsàiÛ[ÀŸ½noŒß8¼Ç~:H­cC&copy;ÉMúak
,øwsäIê�cÄxófGý&lt;št±Çäè]Vî+ ½_¡á÷ðÍÉ"IÃùqšÆÞh‘Ê—qÙ=%øbx½yÉ:ÒuÝá[„ ¼À8žz&copy;øð؆“ðÖûž¼ÉëzÑ‘«å]ýÖ¡ÓÑ Päsvü[iï-$¯ÕŠž -ô˜ÊR‰–ñªå±Ç€ö×!ÀŽƒ¥cõ(J¦ŠöŽZ ²Ì.là¨4ç4Û±˜‚î' {¢8LCZ¡ŽcÄ@˜ˆÌqaé�g/&gt;",ôžfÔÝR³Ü{‡6ÂóNÇ{Áû^ÜíiÀÁÒøÜK;ðA8Hö[Ý[­IÐOR'NÍâ^ø 0ì¦ñRs:@†µìd9Õ~‚9†E¿üS¶MòÀ5ÄÆ&gt;Áÿ`*‘

I think others who have had similar problems had a browser extension that causing problems. Try turning off all browser extensions and see if that fixes it. If it does, try re-enabling them one-by-one to isolate the culprit.

Could you please carefully work through the first three steps of our guide to Solving Technical Issues ? Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable all add-ons/extensions and anti-virus programs . Step 3: Clear your cache If none of the above succeeds, please thoroughly work through Step 4 . (Don't forget the complete Console Log!) Thank you!

Thanks for the help, I will submit a big report shortly. At first disabling the extensions seemed to work. But they are still disabled (I checked) and I clear the cache....and still get gibberish screen about 80% of the time. If I just keep clearing the cache and opening chrome again eventually it just decides to work...sigh.