cancel
Showing results for 
Search instead for 
Did you mean: 

no1_vern's Posts

Thank you for the suggestion and the link, I Chatted with Stadia support to get this issue fixed, I have this problem solved, and I'm able to login to play.   To fix this issue, I have to disable Sc... See more...
Thank you for the suggestion and the link, I Chatted with Stadia support to get this issue fixed, I have this problem solved, and I'm able to login to play.   To fix this issue, I have to disable Scriptsafe in all the Chrome windows before starting Stadia. The issue, even though I had Scriptsafe off in the Chrome windows I opened up to run Stadia(both incognito/logged in), I didn't realize the original Chrome window that did have Scriptsafe still enabled would interfere with Stadia running properly.  Scriptsafe caused the 2nd error above as the Stadia script is disallowed by a Security Policy directive:  Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem:". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution.   I believed Scriptsafe would only stop scripts from running in the Scriptsafe enabled windows. So apparently I have a lot more learning to do - instead of gaming.   Again, thank you for your help.
AFter logging in on my gmail account, accepting the terms, selecting an avatar, Stadia name, reading the privacy statement, and performing all the updates, I'm at the Pro Trial setup, which sits at t... See more...
AFter logging in on my gmail account, accepting the terms, selecting an avatar, Stadia name, reading the privacy statement, and performing all the updates, I'm at the Pro Trial setup, which sits at the spinning icon, inside a Chrome tab.   It's Doing nothing, just sitting there spinning, and its been like that for the last several weeks while I've tried various things to TS this problem. I've verified my AV is off, I'm not using a VPN, I am using Win10 Pro(updated to the latest version), Chrome is allowed through the Firewall.      Chrome is also up to date, and isn't running any extensions that might interfere with the process(I have Scriptsafe OFF, Ublock Origin off) .  When I open the Chrome console to inspect the element, I see there are 2 errors 1. Unchecked runtime.lastError: The message port closed before a response was received. m=EFQ78c,FCpbqb,WhJNk,_latency,fFdwef,hKSk3e:35      AND  2. Refused to create a worker from 'https://stadia.google.com/mgsw.js?xhrRoot=%2F_%2FCloudcastPortalFeWebUi&mssRowKey=boq-chrome-cloudcast.CloudcastPortalFeWebUi.en.pmQcACyBtws.es5.O&buildLabel=boq_cloudcastportalfeuiserver_20200610.02_p1&initialJsPath=https%3A%2F%2Fwww.gstatic.com%2F_%2Fmss%2Fboq-chrome-cloudcast%2F_%2Fjs%2Fk%3Dboq-chrome-cloudcast.CloudcastPortalFeWebUi.en.pmQcACyBtws.es5.O%2Fam%3DAiAQmOOtQtCOcwAg%2Fd%3D1%2Fexcm%3D_b%2C_tp%2Csetupview%2Fed%3D1%2Fdg%3D0%2Fwt%3D2%2Fct%3Dzgms%2Frs%3DAAT3hJb97VmzKTpMKVtrV46PN2BaTbGqcQ%2Fm%3D_b%2C_tp' because it violates the following Content Security Policy directive: "worker-src https://ssl.gstatic.com/stadia/gamers/".      This is the same error I've been receiving since I started almost 4 weeks ago now. Help would be greatly appreciated.