Multiple issues

So, I've been using Roll20 for over a year, mostly since the start of the pandemic. I run a D&D 5E game on Tuesday nights and, for a long time, we played without any issues, especially connection issues.  Recently, though, we've had several. Last night was probably the worst. There were 5 of us - me and 4 players. I don't have any debugging information, or any more information that the following but I hope this is of use to someone in the technical area because if things continue this way, we're not going to be able to use Roll20.  The issues we've been having: People have problems seeing each other, or hearing each other or both. No matter how many times they reconnect, they have problems. One person last night was able to hear two of the other players, would then reconnect, and then be able to hear to different other players. Every time he tried to reconnect it would flip which two of the other players he could see and hear. One of the players could see and hear me, but couldn't see or hear anyone else. The map screen was also black for him, no matter what he tried. Yes, his token was on the map, and yes, the player ribbon was on that map screen. He couldn't see it. It was the same map that the other 3 players were on and they could see it. I checked all of his vision settings and they all looked good - the same as they've always been. Since the change was made to have character sheets on a different server, my players have reported problems with opening up their own character sheets. Last night, one player (the same one with the black screen) was able to open up his sheet, less than a minute later not be able to open up his sheet, and then later open his sheet again. Other players have, on other nights, reported not being able to open up their character sheets at all. I use a number of API scripts. Last night, the API kept crashing. I've not added new API scripts in a long time. Unfortunately, I was not able to grab the errors from the log file. However, this morning, the following appeared in the log: No existing sandbox found.   Preparing sandbox to start on game activity. Spinning up new sandbox... "[Resting in Style] Piggiebacking on TokenMod for token change observations." "Loading character sheet data..." "Starting webworker script..." "Loading 755 translation strings to worker..." "Starting webworker script..." "Loading 755 translation strings to worker..." "SyntaxError: Unexpected token '.'" "SyntaxError: Unexpected token '.'     at eval (<anonymous>)     at messageHandler (evalmachine.<anonymous>:713:6)     at process.<anonymous> (/home/node/d20-api-server/node_modules/tiny-worker/lib/worker.js:65:55)     at process.emit (events.js:310:20)     at emit (internal/child_process.js:876:12)     at processTicksAndRejections (internal/process/task_queues.js:85:21)"

Updates to 1-click installed api scripts get pushed out every Tuesday. It's possible that one was updated without you "changing" anything that is now causing the crash. I'd start temporarily disabling your scripts one by one until you can get the sandbox to load. If you have an idea what script might contain a function called "processTicksAndRejections", I'd start there :)  

For the A/V problems, I would suggest trying what many do (including myself), use Roll20 for video only, and use a dedicated program like discord to handle the audio. Since we switched the that, with the exception of one 2 week span, we have not had to play the reconnect game at all. As for the "blind" player, that's harder to diagnose. Are they using a supported browser? Do they have a problem with other maps or was it just specifically that one? If it is a universal problem, there are things we can suggest. If it was a specific map, it's hard to tell without "boots on the ground". You could try asking them to capture a Console Log ( Chrome ,  Firefox ) during the time it is happening, and  gather screen shots of settings and filing a  Help Center Request . Not sure what you mean by " Since the change was made to have character sheets on a different server". Are you referring to an update of some kind, or did you copy your game? In any case, there is a known bug of being unable to re-open a journal that has  been popped out while using Chrome. Could that be involved?

When they said "character sheets on a different server" I think that refers to the advent of the Purple Spinning Circle on opening characters. Since the update that started that. keithcurtis said: Not sure what you mean by " Since the change was made to have character sheets on a different server". Are you referring to an update of some kind, or did you copy your game? 

Derp, that sandbox error is the one that everyone has been getting lately that doesn't actually prevent the sandbox from spinning up. It can be ignored. Disregard my previous comment. I hadn't remembered it having that processTicksAndRejections line, but I just checked one of my games and there it is!

For the A/V problems we use Discord for another game and it has its own share of problems. I dislike using it. But, more importantly, some of the people playing are not computer literate, and can't handle having to use two applications for one game. It would turn them off. For the blind player: I tried all the obvious problems. This is someone who has been playing with us for several months and never had this problem. He also runs his own game on Wednesday (that I play in) and has never had this problem. It was only the one map since the party was only on one map that night. He reconnected several times, I checked his vision settings, I deleted and replaced the token several times, nothing worked. All he could see is a black screen. For the character sheet issue, it's my understanding that a few months ago, Roll20 made the decision to host character sheets on a separate server. Since that change, players have reported problems opening their character sheets. Sometimes, the problem comes and goes, sometimes they can open the sheet once, and then not again, etc. Again, this is a game that has been running with the same people for months and the "blind" issue only surfaced last night. The A/V issue has been intermittent for a month or two but usually is resolved by people reconnecting until everyone can see and hear each other. Last night that didn't work. The character sheet problem has been intermittent since the change. keithcurtis said: For the A/V problems, I would suggest trying what many do (including myself), use Roll20 for video only, and use a dedicated program like discord to handle the audio. Since we switched the that, with the exception of one 2 week span, we have not had to play the reconnect game at all. As for the "blind" player, that's harder to diagnose. Are they using a supported browser? Do they have a problem with other maps or was it just specifically that one? If it is a universal problem, there are things we can suggest. If it was a specific map, it's hard to tell without "boots on the ground". You could try asking them to capture a Console Log ( Chrome ,  Firefox ) during the time it is happening, and  gather screen shots of settings and filing a  Help Center Request . Not sure what you mean by " Since the change was made to have character sheets on a different server". Are you referring to an update of some kind, or did you copy your game? In any case, there is a known bug of being unable to re-open a journal that has  been popped out while using Chrome. Could that be involved?

Ah, I see what you are talking about. The way the sheets are implemented was changed in order to accommodate development of the mobile app, and for a month or so, there was an issue with resolution time. This was addressed and drastically improved, but you can still run into problems with compendium drops if you don't give the monster time to resolve. I haven't seen a lot of reports of being unable to just open existing sheets, though. Did you check with your players to make sure they are not popping their sheets out into a separate window, or that they do not have their settings defaulted to that behavior? That can absolutely affect the ability to re-open a sheet within a session, at least on Chrome. Likewise, have you enquired as to the browsers they are using? For the specific "blind" player, this might work, but seeing as it was only a single map, it's unlikely. Deleting cache might help if the issue was related to the system's refusal to serve him a particular graphic. Another thing to try in such a situation might be to duplicate the page and see if the issue persists. Ultimately, if it was just that map, and is not a persistent issue, it might not be worth the time and effort to solve. You have my sympathies on the technology matters. I also have to deal with players who have degrees of technophobia. It might be worth the taking the time to walk them through it (and remember, Discord can be run through your browser—it doesn't have to  be a separate app), if it ultimately saves time and bother of weekly "whack-a-mole" connection sessions. But if you dislike using Discord to begin with, then I understand that might not be a viable situation.

In one game I'm in as a player, I occasionally have the "blind" problem (totally black map), despite correct settings. I run in incognito mode to ensure no extensions. Sometimes joining in with a different browser helps me (if blind on Chrome, I try Firefox and it works or vice versa). In another game that I run, I had one player that suddenly couldn't log in (spinning up for >20min) for over a week. I made a copy of the game and with no other changes, poof, no problems for them. Can't explain it, but might be something to try if nothing else works. 

I agree with Saul that delays-glitches-timeouts when opening Character Sheets is still an ongoing issue to optimize further. Also agree what keithcurtis said, that problem was addressed & improved from how bad it was at first. Pro-tip for Saul's players: Open your Character Sheet just once. Then double-click the top line to MINIMIZE it. Don't close it.  When you close it & you have to re-open it, that can risk taking longer.  Doubleclicking the top-line to re-maximize the sheet you'd minimized is usually instant (faster). Saul J. said: For the character sheet issue, it's my understanding that a few months ago, Roll20 made the decision to host character sheets on a separate server. Since that change, players have reported problems opening their character sheets. Sometimes, the problem comes and goes, sometimes they can open the sheet once, and then not again, etc.

I think the browser the "blind" person uses is Chrome but I'll double check. We'll see what happens on Tuesday - this is the first time this player had that problem, and has been able to see that map on other occasions so I don't know what might have changed. I'll also try the "minimize" sheet trick - I do it myself with NPCs in this game, and my character sheet in another game but the players that have problems, might not know the trick. As for Discord - I have one player in the game who, every week, has to be told how to do things that he just did the week before. Trying to teach him to connect via Discord is probably going to be confusing. But, the one that that I need to be able to do is to talk privately with individual players periodically and I can't do that in Discord (as far as I know). keithcurtis said: Ah, I see what you are talking about. The way the sheets are implemented was changed in order to accommodate development of the mobile app, and for a month or so, there was an issue with resolution time. This was addressed and drastically improved, but you can still run into problems with compendium drops if you don't give the monster time to resolve. I haven't seen a lot of reports of being unable to just open existing sheets, though. Did you check with your players to make sure they are not popping their sheets out into a separate window, or that they do not have their settings defaulted to that behavior? That can absolutely affect the ability to re-open a sheet within a session, at least on Chrome. Likewise, have you enquired as to the browsers they are using? For the specific "blind" player, this might work, but seeing as it was only a single map, it's unlikely. Deleting cache might help if the issue was related to the system's refusal to serve him a particular graphic. Another thing to try in such a situation might be to duplicate the page and see if the issue persists. Ultimately, if it was just that map, and is not a persistent issue, it might not be worth the time and effort to solve. You have my sympathies on the technology matters. I also have to deal with players who have degrees of technophobia. It might be worth the taking the time to walk them through it (and remember, Discord can be run through your browser—it doesn't have to  be a separate app), if it ultimately saves time and bother of weekly "whack-a-mole" connection sessions. But if you dislike using Discord to begin with, then I understand that might not be a viable situation.

I hope the "minimize" trick helps your players. Discord if you decide to use it for this -- if your technology-challenged player has a smartphone, it may be easiest for them to get-install-run Discord on their phone, while Roll20 is on the computer. This way you don't have to switch between windows on the computer, and some people may find the phone app verison easier to learn and to turn-on Voice. Also last, yes, you can do Private chats (of text or voice) with individuals using Discord. Saul J. said: I'll also try the "minimize" sheet trick - I do it myself with NPCs in this game, and my character sheet in another game but the players that have problems, might not know the trick. As for Discord - I have one player in the game who, every week, has to be told how to do things that he just did the week before. Trying to teach him to connect via Discord is probably going to be confusing. But, the one that that I need to be able to do is to talk privately with individual players periodically and I can't do that in Discord (as far as I know). keithcurtis said: Ah, I see what you are talking about. 

Ok, more information about the "blind" player, after another night of gaming.&nbsp; &nbsp;The problem started in the middle of the game on 8/24. The characters moved from one map to another and this one player suddenly "went blind". &nbsp;The problem continued on 8/31. I worked with him after the game ended. He can't see anything on any map. He just gets a black screen. He can't even see his own token. &nbsp;He normally uses Chrome. It's the most recent version. I asked him to try Firefox, and he had the same problem. He runs another game on Wednesday night. He's not had the problem in his Wednesday game. I tried logging in as hime (he gave me his password) and it failed for me in Chrome as well. I tried both a regular window and an "incognito" window.&nbsp; In addition to not being able to see any map, he can't see anything in the "Turn Order" except for his own character name, and the round marker I put in. He can't see any of the other PC names in the turn order, nor any of the NPCs.&nbsp; Again, on his Wednesday night game, everything is fine. Same browser. Different RPG (the Tuesday game is D&amp;D 5E, the Wednesday game is Traveller) but I can't see how the rpg can have any effect. None of the other players have any problem. This player also has access to another of the PC tokens because he, on occasion, plays that character when that player isn't around. He used to be able to "see" what that other character saw as well but he doesn't see that either. I tried removing his permission to access that character token/sheet and it had no effect. I've tried playing with all of the "lighting" settings on his token turning vision off and on, turning off UDL for that token and turning on LDL, tried setting his field of vision, nightvision on/off, etc. and nothing made a difference. I logged in as him to one of the backup copies of the game that I had. His vision works fine in the backup copy. So, it's clearly something internal to the game that's causing the problem - something hidden somewhere in the internals. I had him grab a console log. I did as well while logged in as him. The log is below. I'm going to open up a bug report with this info too but maybe someone here can come up with a fix before support does by looking at the log and the above info. The last two lines of the console log are the most interesting to me. 07:26:29.230 app.roll20.net/:6 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-YlNbnurwys4uT3zV' <a href="https://storage.googleapis.com" rel="nofollow">https://storage.googleapis.com</a> &nbsp; <a href="https://www.datadoghq-browser-agent.com" rel="nofollow">https://www.datadoghq-browser-agent.com</a> <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 https://*.fullstory.com". Either the 'unsafe-inline' keyword, a hash ('sha256-kH8OfsIWm/j2az5XQDZmvxH0faTd3NBwLZS7nTM5Oy4='), or a nonce ('nonce-...') is required to enable inline execution. 07:26:29.347 app.roll20.net/:21 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-YlNbnurwys4uT3zV' <a href="https://storage.googleapis.com" rel="nofollow">https://storage.googleapis.com</a> &nbsp; <a href="https://www.datadoghq-browser-agent.com" rel="nofollow">https://www.datadoghq-browser-agent.com</a> <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 https://*.fullstory.com". Either the 'unsafe-inline' keyword, a hash ('sha256-pTNkp50U6tVf8FuQzTMh762+Nza6SP/j648+XWvdL+s='), or a nonce ('nonce-...') is required to enable inline execution. 07:26:29.354 ​ JQMIGRATE: Logging is active 07:26:29.919 ​ CAMPAIGN ID: 6261973 07:26:30.299 ​ [Deprecation] RTP data channels are no longer supported. The "RtpDataChannels" constraint is currently ignored, and may cause an error at a later date. (anonymous) @ app.js:278 07:26:30.401 ​ 70 07:26:30.437 ​ TOUCH SUPPORTED: false 07:26:30.441 ​ USING WEBGL ACCELERATION... 07:26:30.445 ​ WEBGL STARTUP SUCCESS 07:26:30.519 ​ Loading Custom character sheet. 07:26:30.550 ​ tuts loaded 07:26:31.428 ​ Including compendium template css. 07:26:31.564 ​ Starting up WEB WORKER 07:26:31.619 ​ Starting up WEB WORKER 07:26:31.624 ​ Roll20 Environment: Web 07:26:32.476 ​ Final page load. 07:26:32.554 ​ Auth'ed. 07:26:32.555 ​ Go post auth! 07:26:32.635 ​ initial setup 07:26:32.684 ​ joining game... 07:26:32.692 ​ Player -M31kmAu22E2PPV5SEKL is offline... 07:26:32.693 ​ Player -M3CMksYN1jEXPgLr23h is offline... 07:26:32.694 ​ Player -M3CdOQCdohfMHy49FYz is offline... 07:26:32.695 ​ Player -M3DWrxrIuw6Br959tQM is offline... 07:26:32.696 ​ Player -M3NaRURo-FdY9_wTV4H is offline... 07:26:32.697 ​ Player -M44PnvYLwVKkAUGF6Bd is offline... 07:26:32.697 ​ Player -M44dskuz-3MMteCQBIG is offline... 07:26:32.698 ​ Player -MJSUyfJ3RJ13bi91B8J is offline... 07:26:32.699 ​ Player -MJXtSppFSZGIIUEW6KR is offline... 07:26:32.706 ​ Deferred finish joining... 07:26:32.708 ​ Firebase Online 07:26:32.741 ​ Full load page! 07:26:32.749 ​ Full load page! 07:26:32.757 ​ Full load page! 07:26:32.765 ​ Full load page! 07:26:32.772 ​ Full load page! 07:26:32.781 ​ Full load page! 07:26:32.789 ​ Full load page! 07:26:32.795 ​ Full load page! 07:26:32.802 ​ Full load page! 07:26:32.809 ​ Full load page! 07:26:32.818 ​ Full load page! 07:26:32.825 ​ Full load page! 07:26:32.832 ​ Full load page! 07:26:32.840 ​ Full load page! 07:26:32.846 ​ Full load page! 07:26:32.853 app.js?1629823594:603 Full load page! 07:26:32.859 app.js?1629823594:603 Full load page! 07:26:32.866 app.js?1629823594:603 Full load page! 07:26:32.872 app.js?1629823594:603 Full load page! 07:26:32.879 app.js?1629823594:603 Full load page! 07:26:32.885 app.js?1629823594:603 Full load page! 07:26:32.892 app.js?1629823594:603 Full load page! 07:26:32.902 app.js?1629823594:603 Full load page! 07:26:32.908 app.js?1629823594:603 Full load page! 07:26:32.915 app.js?1629823594:603 Full load page! 07:26:32.921 app.js?1629823594:603 Full load page! 07:26:32.927 app.js?1629823594:603 Full load page! 07:26:32.933 app.js?1629823594:603 Full load page! 07:26:32.939 app.js?1629823594:603 Full load page! 07:26:32.945 app.js?1629823594:603 Full load page! 07:26:32.951 app.js?1629823594:603 Full load page! 07:26:32.957 app.js?1629823594:603 Full load page! 07:26:32.965 app.js?1629823594:603 Full load page! 07:26:32.971 app.js?1629823594:603 Full load page! 07:26:32.977 app.js?1629823594:603 Full load page! 07:26:32.983 app.js?1629823594:603 Full load page! 07:26:32.990 app.js?1629823594:603 Full load page! 07:26:32.996 app.js?1629823594:603 Full load page! 07:26:33.002 app.js?1629823594:603 Full load page! 07:26:33.008 app.js?1629823594:603 Full load page! 07:26:33.014 app.js?1629823594:603 Full load page! 07:26:33.020 app.js?1629823594:603 Full load page! 07:26:33.029 app.js?1629823594:603 Full load page! 07:26:33.036 app.js?1629823594:603 Full load page! 07:26:33.042 app.js?1629823594:603 Full load page! 07:26:33.048 app.js?1629823594:603 Full load page! 07:26:33.055 app.js?1629823594:603 Full load page! 07:26:33.061 app.js?1629823594:603 Full load page! 07:26:33.067 app.js?1629823594:603 Full load page! 07:26:33.075 app.js?1629823594:603 Full load page! 07:26:33.081 app.js?1629823594:603 Full load page! 07:26:33.087 app.js?1629823594:603 Full load page! 07:26:33.094 app.js?1629823594:603 Full load page! 07:26:33.100 app.js?1629823594:603 Full load page! 07:26:33.106 app.js?1629823594:603 Full load page! 07:26:33.113 app.js?1629823594:603 Full load page! 07:26:33.120 app.js?1629823594:603 Full load page! 07:26:33.126 app.js?1629823594:603 Full load page! 07:26:33.132 app.js?1629823594:603 Full load page! 07:26:33.138 app.js?1629823594:603 Full load page! 07:26:33.145 app.js?1629823594:603 Full load page! 07:26:33.151 app.js?1629823594:603 Full load page! 07:26:33.160 app.js?1629823594:603 Full load page! 07:26:33.166 app.js?1629823594:603 Full load page! 07:26:33.173 app.js?1629823594:603 Full load page! 07:26:33.179 app.js?1629823594:603 Full load page! 07:26:33.186 app.js?1629823594:603 Full load page! 07:26:33.192 app.js?1629823594:603 Full load page! 07:26:33.198 app.js?1629823594:603 Full load page! 07:26:33.204 app.js?1629823594:603 Full load page! 07:26:33.210 app.js?1629823594:603 Full load page! 07:26:33.216 app.js?1629823594:603 Full load page! 07:26:33.221 app.js?1629823594:603 Full load page! 07:26:33.260 app.js?1629823594:603 Full load page! 07:26:33.273 app.js?1629823594:603 Full load page! 07:26:33.280 app.js?1629823594:603 Full load page! 07:26:33.291 app.js?1629823594:603 Full load page! 07:26:33.298 app.js?1629823594:603 Full load page! 07:26:33.304 app.js?1629823594:603 Full load page! 07:26:33.311 app.js?1629823594:603 Full load page! 07:26:33.317 app.js?1629823594:603 Full load page! 07:26:33.323 app.js?1629823594:603 Full load page! 07:26:33.330 app.js?1629823594:603 Full load page! 07:26:33.336 app.js?1629823594:603 Full load page! 07:26:33.341 app.js?1629823594:603 Full load page! 07:26:33.347 app.js?1629823594:603 Full load page! 07:26:33.353 app.js?1629823594:603 Full load page! 07:26:33.358 app.js?1629823594:603 Full load page! 07:26:33.364 app.js?1629823594:603 Full load page! 07:26:33.370 app.js?1629823594:603 Full load page! 07:26:33.375 app.js?1629823594:603 Full load page! 07:26:33.380 app.js?1629823594:603 Full load page! 07:26:33.386 app.js?1629823594:603 Full load page! 07:26:33.391 app.js?1629823594:603 Full load page! 07:26:33.397 app.js?1629823594:603 Full load page! 07:26:33.402 app.js?1629823594:603 Full load page! 07:26:33.412 app.js?1629823594:603 Full load page! 07:26:33.417 app.js?1629823594:603 Full load page! 07:26:33.419 app.js?1629823594:604 We have 98 pages 07:26:34.916 app.roll20.net/:1 Mixed Content: The page at '<a href="https://app.roll20.net/editor/" rel="nofollow">https://app.roll20.net/editor/</a>' was loaded over HTTPS, but requested an insecure element '<a href="http://vignette1.wikia.nocookie.net/prehistoric-earth-a-natural-history/images/b/b1/270px-DimetrodonInfobox.jpg/revision/latest?cb=20140805195225" rel="nofollow">http://vignette1.wikia.nocookie.net/prehistoric-earth-a-natural-history/images/b/b1/270px-DimetrodonInfobox.jpg/revision/latest?cb=20140805195225</a>'. This request was automatically upgraded to HTTPS, For more information see <a href="https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html" rel="nofollow">https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html</a> 07:27:02.274 app.js?1629823594:340 [Deprecation] The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead. (<a href="https://bit.ly/audio-worklet" rel="nofollow">https://bit.ly/audio-worklet</a>) n.initializeAudioContext @ app.js?1629823594:340 07:27:08.881 app.js?1629823594:600 Debounced init page! 07:27:09.272 app.js?1629823594:600 Debounced init page! 07:28:27.303 app.js?1629823594:600 Debounced init page! 07:28:28.145 DevTools failed to load source map: Could not load content for <a href="https://app.roll20.net/js/d20/underscore-min.map" rel="nofollow">https://app.roll20.net/js/d20/underscore-min.map</a>: Fetch through target failed: Target not supported; Fallback: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE 07:28:28.357 DevTools failed to load source map: Could not load content for <a href="https://app.roll20.net/js/d20/underscore-min.map" rel="nofollow">https://app.roll20.net/js/d20/underscore-min.map</a>: Fetch through target failed: Target not supported; Fallback: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE