Stuck at Loading (No New Game)

Hi Silvia U. - Thank you for the report and we apologize for any trouble! To best assist with troubleshooting this, would you mind providing us with the exact name of a game that this issue has or is occurring in?

Hey all - Thank you for the additional details. Unfortunately, when I go to load into the games you mentioned, I am having no issues loading in. Would you mind providing some additional information below, whenever you get a chance, please? This will allow me to best escalate this to our development team so they can further investigate what might be going on here.  A snapshot of the following computer settings/options (A good place to find this info if you don't know it is  Support Details ): Web Browser(s)  Browser Version(s) Operating System(s) If Javascript is enabled Your anti-virus software List of any browser add-ons or extensions enabled A Console Log from the moment you try to load into the game. Directions for providing a console log in Chrome can be found  here . Firefox will have the same process as what is noted in the Chrome article except it uses a different interface, which is explained  here .

Silvia U. said: Well sadly I cant do any screenshots, but I can tell I use Firefox 69 for Roll 20 and I have Windows 10 as Opertating System and Javascript  is enabled Also I have Norton as Anti Virus Software Hey Silvia U. - Gotcha! Thanks for confirming that. Are you able to provide us with the console log (item #2) as well? Getting that console log is important for allowing our development team to best diagnose and address this issue. We appreciate your patience and understanding.

Silvia U. said: Again sadly no screenshot, but well thats the text after trying to log in aswell as well jumping through some websites, because I had to get this all set up nsLoginManager: searchLogins: `formActionOrigin` or `httpRealm` is recommended LoginManager.jsm:467:13 LoginHelper: Couldn't parse origin for about:blank <unavailable> LoginHelper.jsm:248:11 Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsICacheInfoChannel.isRacing]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-response-listener.js", lineNumber: 334, columnNumber: 0, data: null, stack: "NetworkResponseListener.prototype._getSecurityInfo<@resource://devtools/server/actors/network-monitor/network-response-listener.js:334:26\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22\nonStartRequest@resource://devtools/server/actors/network-monitor/network-response-listener.js:226:10\n", location: XPCWrappedNative_NoHelper } ThreadSafeDevToolsUtils.js:90:13 Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsICacheInfoChannel.isRacing]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-response-listener.js", lineNumber: 334, columnNumber: 0, data: null, stack: "NetworkResponseListener.prototype._getSecurityInfo<@resource://devtools/server/actors/network-monitor/network-response-listener.js:334:26\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22\nonStartRequest@resource://devtools/server/actors/network-monitor/network-response-listener.js:226:10\n", location: XPCWrappedNative_NoHelper } ThreadSafeDevToolsUtils.js:90:13 Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsICacheInfoChannel.isRacing]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-response-listener.js", lineNumber: 334, columnNumber: 0, data: null, stack: "NetworkResponseListener.prototype._getSecurityInfo<@resource://devtools/server/actors/network-monitor/network-response-listener.js:334:26\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22\nonStartRequest@resource://devtools/server/actors/network-monitor/network-response-listener.js:226:10\n", location: XPCWrappedNative_NoHelper } ThreadSafeDevToolsUtils.js:90:13 Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsICacheInfoChannel.isRacing]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-response-listener.js", lineNumber: 334, columnNumber: 0, data: null, stack: "NetworkResponseListener.prototype._getSecurityInfo<@resource://devtools/server/actors/network-monitor/network-response-listener.js:334:26\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22\nonStartRequest@resource://devtools/server/actors/network-monitor/network-response-listener.js:226:10\n", location: XPCWrappedNative_NoHelper } ThreadSafeDevToolsUtils.js:90:13 Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsICacheInfoChannel.isRacing]", result: 2147746065, filename: "resource://devtools/server/actors/network-monitor/network-response-listener.js", lineNumber: 334, columnNumber: 0, data: null, stack: "NetworkResponseListener.prototype._getSecurityInfo<@resource://devtools/server/actors/network-monitor/network-response-listener.js:334:26\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:111:22\nonStartRequest@resource://devtools/server/actors/network-monitor/network-response-listener.js:226:10\n", location: XPCWrappedNative_NoHelper } ThreadSafeDevToolsUtils.js:90:13 LoginHelper: Couldn't parse origin for about:blank <unavailable> LoginHelper.jsm:248:11 Hello Silvia U. - This actually seems to be a log from the Network tab in the Firefox developer tools, rather than the Console tab. Again, to best troubleshoot this, we would need a log from the Console tab. I found an additional article with better directions on how to send a console log in Firefox. Here it is . However, for those directions, you can ignore steps 9 and 10 and instead copy-paste the log directly to me here. We apologize for any troubles and we really appreciate your patience. Thank you!