Roll20 Won't Load ---- Still

Please tell me what I need to do to make this web site work. Don't tell me it is a security issue, a hardware issue, router issue, whatever. Please tell me how to identify what part of the bridge is falling down and what to do in order to fix it. Roll20 worked great until Easter, not does not work at all. I've done nothing different so it has to be something on the server side. I new protocol that is rejecting my old equipment, a improved function that my legacy software is confused by, something.&nbsp; For the dozen some odd time, please help. Tell me something, anything, even if it is 'upgrade or go to hell'. My current concern is that when my new laptop arrives I will still be shut out in limbo-land since I don't understand why I am being locked at the infinite Load screen. $600 dollars is a lot of money to waste it the new machine is going to encounter the same problem. Again: Windows XP, Chrome&nbsp; Version 49.0.2623.112 m And the console:&nbsp; Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'nonce-m03rrbl0H8ayuszF' <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-esUuIeEqyXHne5UEJp7cTUgUxV+7YoT17cv5rF1EiLs='), or a nonce ('nonce-...') is required to enable inline execution. app.roll20.net/:13 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'nonce-m03rrbl0H8ayuszF' <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. jquery.migrate.js:20 JQMIGRATE: Logging is active instrument.ts:129 CAMPAIGN ID: 3170991 app.js:554 Uncaught SyntaxError: Unexpected identifier ?timestamp=1588212080&amp;disablewebgl=false&amp;forcelongpolling=false&amp;offsite=false&amp;fbdebug=false&amp;forceto…:38 Uncaught ReferenceError: soundManager is not defined <a href="https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7" rel="nofollow">https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7</a> Failed to load resource: the server responded with a status of 403 () app.roll20.net/:1 Fetch API cannot load <a href="https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7" rel="nofollow">https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7</a>. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '<a href="https://app.roll20.net" rel="nofollow">https://app.roll20.net</a>' is therefore not allowed access. The response had HTTP status code 403. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. <a href="https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7" rel="nofollow">https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7</a> Failed to load resource: the server responded with a status of 403 () app.roll20.net/:1 Fetch API cannot load <a href="https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7" rel="nofollow">https://sentry.roll20staging.net/api/10/store/?sentry_key=fe596f386bb14775b58cad9accd672d0&amp;sentry_version=7</a>. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '<a href="https://app.roll20.net" rel="nofollow">https://app.roll20.net</a>' is therefore not allowed access. The response had HTTP status code 403. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Please carefully work through to 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. Step 3: Clear your cache If none of the above succeeds, please have your player thoroughly work through Step 4. (Don't forget the complete Console Log!) If you need additional information on how to capture a console log we have additional information here: &nbsp; Submitting a Console Log in Firefox &nbsp;Submitting a Console Log in Chrome Thank you!&nbsp;

Gene, I feel you.&nbsp; One of my players is experiencing much the same issue, and it's preventing me from giving my players (what I hope to be) a great gaming experience.&nbsp; Everything worked okay until about a week or so ago, then kaput. TwilightWoods, um, he provided all of that.&nbsp; Did you read his post?

Thanks, I did what you suggested and it still fails.&nbsp; Step 1: I am running a legacy version of Chrome because I am running on a Windows XP machine that is older than my teenage sons. Version 49. Step 2: I disabled all the&nbsp; extensions on my browser.&nbsp; Step 3: Cleared Cache, saved passwords,&nbsp; Step 4: Not sure what you mean, I already included the entire console log. Did I miss anything? Still won't work.&nbsp;

DM and Twilightwoods, I did everything I was told to do to the degree that I understood the instructions. I provided screen prints of the section of Chrome that I was working on, in case I am just doing it wrong.&nbsp; Please look over my screen prints and my post and tell me where the wheels left the wagon.&nbsp;

Windows XP is indeed an old operating system, almost 20 years old , and out of support for 6 years. I imagine it is also 32-bit. Unfortunately, to provide the features and functions that most users want today, Roll20 cannot always maintain legacy support for a system that old. I am just another user, but I don't want Roll20 to hold off on things to support a small minority of users with outdated systems. Sorry, nothing personal. I hope your new laptop arrives soon, and Roll20 works great. A newer OS will be safer for you, too.

If it was just people using Windows XP having this problem I'd be inclined to agree with you. However there are people who are having this problem running Windows 10, Linux, the roll20 app on their ablets and phones, etc. I spent 10 years has a COBOL programmer oh, I know it's made for him and that's a whole different world and one best left in the ashes but that time taught me if the problem persists across multiple platforms it's probably bad code.

Gene S. said: I spent 10 years has a COBOL programmer I don't feel so old now.&nbsp; Thank you for that.&nbsp; XD (Also, yes, my player that's experiencing the most trouble is using a more recent OS and browser, no extensions.)

While I am not denying there may be an issue Roll20 needs to look at, I would rather they not spend their resources looking into systems that old. Additionally, there are some other issues going on. The Roll20 App needs updating, Roll20 has said as much, and had plans to update it this year, though that may have been delayed by the pandemic situation. Roll20 via the web and the Roll20 App is not supported on phones. The Roll20 App is intended to work on phones, but see above. There is a known issue with Firefox 75 on Ubuntu that is temporarily causing problems for a lot of folks on Linux. There are some workarounds, and Firefox 77 should correct it. There are some users with Windows 10 (and recent iOS and other flavors of *nix) encountering this problem, and while they may have the same symptom as the above, that does not mean they have the same root cause. These users are where Roll20 needs to spend their troubleshooting resources and support, IMO. There is also the unprecedented usage of Roll20 and network bandwidth in general these last few weeks that may be playing a role, too. EDIT: Correcting myself here: The Roll20 App is intended to work on phones, but the app still needs updating.

Gene S. said: Please tell me what I need to do to make this web site work. Don't tell me it is a security issue, a hardware issue, router issue, whatever. I know you don't want to hear it, but part of your problem is something in security settings on your end.&nbsp; During the last round of people not being able to connect, one user figured out that sentry-cdn is something you can't block and have Roll20 load.&nbsp; Knowing that, take another look at your console log. The post where this was mentioned (there are follow up posts that may be of interest):&nbsp; <a href="https://app.roll20.net/forum/permalink/8491859/" rel="nofollow">https://app.roll20.net/forum/permalink/8491859/</a>

A friend of mine but his computer to my house, and use the same internet connection that I do, and was able to acces the website just fine.&nbsp; I don't want to get into a pissing contest over this. My last rounds of posts were based on the concern that I was going to be buying a new computer and having the same problems. If it works I'm happy. Then someone says your stuff is out of date and we current users are more relevant than supporting you guys who can't afford to upgrade ticked me off. I love to game, been a GM for 37 years, I pay for my membership to help support the company, and I resent being told I'm not worth supporting. I saw over 2000 people who have looked into this issue. I imagine most are free users, but I doubt all are since I am among them. That isn't a small number. I am not irrelevant.&nbsp;

I've been trying to come up with a good example for this. I think I finally have. Mind you it's lame and not quite realistic but I think it's pretty close to the mark. Let's say you have a car you drive that car for 2 years with no problems. Then one morning you go out to your car expecting to take a pleasant drive but the previous night your city laid new asphalt on all the roads. For some reason your car can not get any traction on the new paving material. You contact the city because nothing has changed with your car but now it's useless for the purpose which it was intended. The city tells you it's your fault because you should have upgraded your tires. Unfortunately you don't have the $800 you need to buy the new tires that would be needed for the new paving material. Wouldn't that annoy you just a little?

Probably the most frustrating thing for those of us seeing the performance and other issues, is that we were told the new UDL was OPT-In and would not affect Legacy, yet we are all seeing the effects.&nbsp; Don't Pee on my head and tell me it's raining.&nbsp; Fix the problems with Legacy or remove the UDL from Production until you can get the issues resolve in Dev!

Thank you Bob for understanding my position. I didn't intend to get defensive or be offensive but I hate being "blamed" for my issues when I've made no changes. I have to admit something, the "friend" I mentioned who tested our router settings and ISP connection for the 'security violations ' my computer was having was my wife. She used her work computer (she telecommutes). I didn't want to get her in trouble but I don't think her boss is a member.&nbsp;

No one is saying you are irrelevant, but there has to be a realistic cut off at some point. Should Roll20 still support Windows 2000? Windows 98? The writing has been on the wall about Windows XP for some time now. A better car analogy would be if you were still driving a car that needed leaded gasoline. At some point, those folks needed to get a newer car, as leaded gasoline was no longer available. I am sorry you are experiencing problems, but you are in a very small minority. 2000 users is 0.04% of Roll20's 5 million users, and we probably have closer to 6 million users by now.

Rabulias said: No one is saying you are irrelevant, but there has to be a realistic cut off at some point. Should Roll20 still support Windows 2000? Windows 98? The writing has been on the wall about Windows XP for some time now. A better car analogy would be if you were still driving a car that needed leaded gasoline. At some point, those folks needed to get a newer car, as leaded gasoline was no longer available. I am sorry you are experiencing problems, but you are in a very small minority. 2000 users is 0.04% of Roll20's 5 million users, and we probably have closer to 6 million users by now. Rabulaias:&nbsp; You seem to continually belittle others who are genuinely having problems and slowdowns etc. and trying to justify launching a new solution into the mainstream before it was ready, with the statement that it is Opt-in and won't affect the existing framework.&nbsp; That statement was untrue and it is showing.&nbsp; As for your Windows update crap, When they launched windows 8/10, if you were still running Windows 7, you were not impacted by the launch.&nbsp; In fact, many people today, even though it is not supported, are are still running windows 7 and even windows XP, because it works for them.&nbsp;&nbsp; The launch of UDL was premature, as many of us on the Pro forum had stated before they did this on the 8th.&nbsp; The list of bugs as they stood were long and from what I can see, they still have not made much headway on those issues.&nbsp;&nbsp; I understand, with the influx of all the new users that things are being taxed.&nbsp; With that, wouldn't it have made sense to wait or, after all the issues started creeping up, rolled back the UDL onto the Dev Servers and continue development there rather than have your customers be your QC.&nbsp; I am a Test Engineer and if I launched a product to my customers before I had completely tested it, I would not have a job.&nbsp; So, I am happy that you are not having any issues but I believe that the ones not having issues are the minority rather than the reverse which you tend to state.&nbsp; I don't know what you get out of jumping on those of us who are genuinely displeased with the current state of affairs but after last year's Debacle with AFOW, that, to date, has not been fixed, 16 months later, with people who are paying for that feature, Roll20 didn't learn then as I thought they had when they delayed the initial release of UDL due to the number of "SHOW STOPPING" issues but they did not even make a marked improvement on that list before they launched it into the wild.&nbsp; If you like it and it is available on Dev, you could move your games there and be happy, but those of us who are still running Legacy and are being impacted, we want our Roll20 back, even without AFOW, so we can run our games and so our players can enjoy their session more. Rant over.&nbsp; Thanks for reading.

Bob P. said: I understand, with the influx of all the new users that things are being taxed.&nbsp; With that, wouldn't it have made sense to wait or, after all the issues started creeping up, rolled back the UDL onto the Dev Servers and continue development there rather than have your customers be your QC. My guess (and it is a total guess) is that not enough of us were using UDL on the dev server.&nbsp; I know I wasn't. None of the DMs that I talk to frequently use the dev server either.&nbsp; Not saying it is a wise decision, but I can certainly understand why they would introduce it "into the wild" to get more people using/testing/breaking it. I'm still not convinced that the system isn't opt-in, because none of the games I run (4) or games in which I am a player (6) have been impacted by the UDL being introduced.&nbsp; None of those games use it, or have had it turned on at any time.&nbsp; The only thing that seems to have impacted any of those games is the increased server load.

Kraynic said: My guess (and it is a total guess) is that not enough of us were using UDL on the dev server.&nbsp; I know I wasn't. None of the DMs that I talk to frequently use the dev server either.&nbsp; Not saying it is a wise decision, but I can certainly understand why they would introduce it "into the wild" to get more people using/testing/breaking it. I'm still not convinced that the system isn't opt-in, because none of the games I run (4) or games in which I am a player (6) have been impacted by the UDL being introduced.&nbsp; None of those games use it, or have had it turned on at any time.&nbsp; The only thing that seems to have impacted any of those games is the increased server load. Agreed on all points, with the exception that I really feel that the "in-development" nature of UDL had been more strongly stressed. I cringe when I see people trying to use this to actually play a game with. But Legacy? I haven't noticed any change in performance that is not far more likely to have come from the recent load. I do see a great number of reports of people making common errors like trying to use AFoW + Global Illumination and thinking the performance death has something to do with UDL. More to the original topic, I feel for you, Gene S. I can't even browse these forums with my old iPad; can't even log into the site. I can't upgrade to my latest OS unless I want to start paying Adobe monthly license fees for software I bought 8 years ago. It's annoying, but it's the way it is. Since your friend was able to load a game with the only variable being changed was a newer computer, hopefully your laptop will do the job. However, it is still possible that there is some setting in your game that is making the campaign difficult to load. If you would like to PM me an invite, and promote me to GM, I'd be happy to take a look. It could be as simple as a DL setting that is making a particular map (the one it is trying to load by default), too demanding for your current hardware.