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.

DnD Character Sheet Window Pop-Out Forcing Login

Hello!  I currently am trying to get one of my games started but other players and I are having an issue where whenever we attempt to pop out our sheets to get full use of the screen, the new window prompts us to login to our roll20 accounts and then freezes. The first time I did this I tried bringing out the sheet again but it asked me to login again. I refreshed the main page and tried again a bit later and it still asked me to login the first time but afterwards trying to pop out the sheet did actually work, albeit slowly. We are using the DnD 5e Srd stylized sheets and I did notice that there were changes to that sheet in the changelog, but I wasn't certain if that had anything to do with this. Please let me know what else I can provide to help! Thanks!
I'm having the same issue. Looks like a site update might not be sitting well. Here's hoping the problem is resolved soon.
1582761463

Edited 1582761564
Having the same issue. Pretty much any changes I attempt to make (uploading, popping sheets, ect) forces a game board halt and login. Using the same 5e sheets but havn't tested other sheets/games (as im trying to run a game at the moment  =s   ).   Edit- Forgot to mention its not just uploads, but using the marketplace store for token placement is a no go as well, as it does infinite loading of nothing for any search.
Same issue the site is unusable in its current state.
Hello everyone -  Thank you for the report. We are currently investigating this issue and are working to get it resolved as soon as we can. We are consolidating reports to  this main thread here ; please follow it for further updates and communication. As such, we're going to go ahead and close this post.