Infininite Loading Loop - Firebase issue

After new update i can't load into any game withput VPN, before there was no porblems. I tried acessing&nbsp; <a href="https://roll20-5.firebaseio.com/pingdomcheck.json" rel="nofollow">https://roll20-5.firebaseio.com/pingdomcheck.json</a> &nbsp;and it doesn't load at all. What happened and will it be fixed?&nbsp; Relevant settings: Operating System Windows 10 (64-bit) Web Browser Chrome 71.0.3578.98 JavaScript Enabled Tried Firefox and Edge, didn't help. Example error from Crme log: Failed to load resource: net::ERR_CONNECTION_TIMED_OUT roll20-7.firebaseio.com/.lp?start=t&amp;ser=57785761&amp;cb=11&amp;v=5:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT roll20-7.firebaseio.com/.lp?start=t&amp;ser=62481230&amp;cb=12&amp;v=5:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT app.roll20.net/:13 Refused to execute inline script because it violates the following Content Security Policy directive: "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>". Either the 'unsafe-inline' keyword, a hash ('sha256-W4z4mOiwkRlHZN9ZhB3StyLZj6HgkMDMbkFJOavx/+M='), or a nonce ('nonce-...') is required to enable inline execution.

Hi Eric R. We are sorry to hear that you are having this issue. We have a Feedback thread that is tracking and working on these issues. You can find the thread here . As such, I am going to move this post over there and close this one.