Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account
This post has been closed. You can still view previous posts, but you can't post any new replies.

Stuck on Loading Screen

When I click Launch game (any game), I just get stuck on the Loading Screen. This happen in both Chrome and a fresh install of Firefox. Already Tried the steps listed on the wiki ( <a href="https://wiki.roll20.net/Solving_Technical_Issues" rel="nofollow">https://wiki.roll20.net/Solving_Technical_Issues</a> ). Here is what my console says when I launch the game.&nbsp; Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'nonce-GZNWXrIII31VqFty' <a href="http://cdn.inspectlet.com" rel="nofollow">http://cdn.inspectlet.com</a> 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> *.sentry-cdn.com". Either the 'unsafe-inline' keyword, a hash ('sha256-N6tWZFAuzGf2PHG52tH3jO8V6zAg60JhsSbPGi9T+NQ='), or a nonce ('nonce-...') is required to enable inline execution. VM2954:13 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'nonce-GZNWXrIII31VqFty' <a href="http://cdn.inspectlet.com" rel="nofollow">http://cdn.inspectlet.com</a> 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> *.sentry-cdn.com". Either the 'unsafe-inline' keyword, a hash ('sha256-/XHNKTzdVLpPBcMgsOl9LN6PEC5ufZbaLdoU14BWKr0='), or a nonce ('nonce-...') is required to enable inline execution. VM2954:14 GET <a href="https://browser.sentry-cdn.com/5.15.4/bundle.min.js" rel="nofollow">https://browser.sentry-cdn.com/5.15.4/bundle.min.js</a> net::ERR_NAME_NOT_RESOLVED DevTools failed to parse SourceMap: chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map jquery.migrate.js:20 JQMIGRATE: Logging is active ?timestamp=1587366808&amp;disablewebgl=false&amp;forcelongpolling=false&amp;offsite=false&amp;fbdebug=false&amp;forcetouch=false:1 Uncaught ReferenceError: Sentry is not defined &nbsp; &nbsp; at ?timestamp=1587366808&amp;disablewebgl=false&amp;forcelongpolling=false&amp;offsite=false&amp;fbdebug=false&amp;forcetouch=false:1 (anonymous) @ ?timestamp=1587366808&amp;disablewebgl=false&amp;forcelongpolling=false&amp;offsite=false&amp;fbdebug=false&amp;forcetouch=false:1 loading.js?v=11:1 Uncaught ReferenceError: d20ext is not defined &nbsp; &nbsp; at loading.js?v=11:1 (anonymous) @ loading.js?v=11:1 app.js?1587138070:547 Uncaught TypeError: Cannot read property 'siteURL' of undefined &nbsp; &nbsp; at app.js?1587138070:547 &nbsp; &nbsp; at app.js?1587138070:586 (anonymous) @ app.js?1587138070:547 (anonymous) @ app.js?1587138070:586 tutorial_tips.js:7 tuts loaded&nbsp;
1587371077

Edited 1587371152
I'm having the same issue. Since yesterday night, I have been trying to get into one of the games I'm in, and I have not been able to get past the loading screen. I tried several of the other games I'm in as well, to see if it was just that game, but none of the other games I tried would make it past the loading screen either. I even left one of the games 'loading' overnight to see if it would kick, but when I woke up, the game was still stuck loading.
1587372332

Edited 1587372418
GET <a href="https://browser.sentry-cdn.com/5.15.4/bundle.min.js" rel="nofollow">https://browser.sentry-cdn.com/5.15.4/bundle.min.js</a> net::ERR_NAME_NOT_RESOLVED is the pivotal issue here I think. Something on your network (Pihole, router blacklist, antivirus browser security) is blocking that script from loading which means all the dependent scripts later on are failing. If you can work out which of your security systems is stopping it and add " browser.sentry-cdn.com " to a whitelist you should be back in business. For me it was my PiHole because that domain appeared on a gravity list.
PhoeM said: GET <a href="https://browser.sentry-cdn.com/5.15.4/bundle.min.js" rel="nofollow">https://browser.sentry-cdn.com/5.15.4/bundle.min.js</a> net::ERR_NAME_NOT_RESOLVED is the pivotal issue here I think. Something on your network (Pihole, router blacklist, antivirus browser security) is blocking that script from loading which means all the dependent scripts later on are failing. If you can work out which of your security systems is stopping it and get the domain whitelisted you should be back in business. For me it was my PiHole because that domain appeared on a gravity list. Thanks. I do indeed have a dns filter running on my router and I whitelisted "sentry-cdn.com". Didn't think it was that at first because I could manage to launch the game from my laptop which was connected to the same network.&nbsp;
Tom L. said: Thanks. I do indeed have a dns filter running on my router and I whitelisted "sentry-cdn.com". Didn't think it was that at first because I could manage to launch the game from my laptop which was connected to the same network. Exactly the same for me, it was working fine on my mutant Half MacPro Half Linux monstrosity, but not on my main machine. In the end I just assumed that Linux was asking for a second DNS lookup opinion because my PiHole was clearly being obtuse :) Glad that you're back in game.
Hello, To keep things consolidated and organized, we would ask that you please refer to the&nbsp; main thread for this issue seen here &nbsp;- it will have the most recent communications and updates from us. As such, we’re going to go ahead and close this post. Thank you!