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.

API Sandbox not Starting. API restart and script buttons unresponsive.

I'm having an issue with a 5E game with the OGL Sheet and multiple other API scripts. My API Console Log is blank (yes, i have the game running in background). Everything worked fine for about 2 weeks, and the issue has only cropped up this weekend past. API sandbox doesn't spin up on startup, and API's don't load. I am near certain this is not an issue with API scripts as no error is thrown from the API console log, and all my scripts worked previously. Not to mention other people have reported the same problem, mentioned here: Help - Apis not working API not loading I believe they stopped working Saturday, which aligns with some work the Roll20 team did on the API servers (as announced on their twitter and forums).  I've run the game on multiple computers , incognito mode, with and without a VPN , no browser addons, and different browsers (Chrome, Firefox) without success. Searched around and done everything I can think of but I'm convinced I've not caused the issue. Scripts work on one new game that I made. The error I receive in the browser console that I think? is causing the issue is this one: "app.roll20.net/:12  Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'sha256-dm6tOb8rwEmENe5+ec26sQvlH6Xd1CBZ7IvtZ4kJ1og=' 'sha256-jlxVUPsj/qdPM120UwbjpC4Tw7dq+obb7SYUV+lSfrI=' 'nonce-2LOZpvbgBWazMm3w'" "app.roll20.net/:13 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'sha256-dm6tOb8rwEmENe5+ec26sQvlH6Xd1CBZ7IvtZ4kJ1og=' 'sha256-jlxVUPsj/qdPM120UwbjpC4Tw7dq+obb7SYUV+lSfrI=' 'nonce-2LOZpvbgBWazMm3w'" My API output console is completely blank, API's don't work in-game, again I don't think this is anything I've done or the fault of an API. Clicking on Restart API Sandbox or Enable/Disable Scripts throws the following error to console: 4690355:6 Uncaught TypeError: Cannot read property 'child' of undefined at HTMLButtonElement.<anonymous> ( 4690355:4710 ) at HTMLButtonElement.dispatch ( v2.js?1590064647:51 ) at HTMLButtonElement.g.handle ( v2.js?1590064647:51 ) at HTMLButtonElement.nrWrapper ( 4690355:6 ) (anonymous) @ 4690355:4710 dispatch @ v2.js?1590064647:51 g.handle @ v2.js?1590064647:51 nrWrapper @ 4690355:6 For reference, here are the scripts I'm running: Also my location is UK, in case this is a location-based issue. Only bought pro recently, and finally finished setting up the API's, only for them to not work for the weekends D&D game. Obviously this is very frustrating and I hope someone can provide a solution to this issue as I'm pretty stumped, Cheers
You are not alone.  This is pretty much the same issue myself and others are facing.  For me it started when I ran a script (Combat Manager) that doesn't handle errors well if you don't have a token selected when you try to roll initiative.  That has caused my API Sandbox to hang for a few minutes before, but this time it did not recover at all and even deleting the script is not fixing the issue.  Same as you, hitting the restart sandbox button does absolutely nothing, and my console is not reporting anything (errors or otherwise).
I've had a similar issue with Combat Tracker that previously crashed the API sandbox, but was fixed with a restart. However, this issue occurred overnight without me really doing anything so I can't even point to a possible cause. 
Hey everyone -  We have identified a regional issue with certain Javascript assets that is causing a problem with the API scripts page and the external journal. We’re currently investigating and working on a fix. To keep messaging organized and consolidated, please follow the main thread for updates,  seen here . As such, we're going to be closing this post.