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 .
×

Unable to see copied tokens when using HTTPS

Detailed description of the problem When token is dragged in, it is visible and functional. If any subsequent token, is copied from it, it will not be visible. In list of characters for initiatives, there is only an empty icon with no image. Hovering over said character does not highlight the copied token on the field. Minimum number of steps to reproduce the problem Roll20 has to be connected in HTTPS exclusively. If the client is connected to roll20 in mixed HTTP/HTTPS or only HTTP, the copied tokens become visible and intractable again. Description of setup Brave Version 0.68.139 Chromium: 77.0.3865.90 (Official Build) (64-bit HTTPS Everywhere Windows 10
Hi Crystal - We do not support the Brave browser at this point in time. The only browsers we support are Google Chrome and Mozilla Firefox. Using an unsupported browser will cause issues of which we will not be able to address. As such, would you mind trying to reproduce this issue on one of our supported browsers and letting us know the results, please? Thank you! 
Same issue occurs with Firefox as well. It doesn't seem be to be browser based. It's really about, whether it's a strict HTTPS connection or whether the client allows HTTP connection to roll20
Hi Crystal - Gotcha - thanks for the update! For isolating and troubleshooting this issue, would you mind also following the rest of the steps in our  Solving Technical Issues  guide, as seen below: 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, we would also ask that you provide the rest of the requested information from Step 4 .  (Don't forget the complete Console Log!)
With HTTPS Everywhere extension disabled, the token visibility works properly, since we can now have mixed HTTP/HTTPS connection. Strict HTTPS is becoming more and more common. Use of plugin like this is not uncommon. If detected, Roll20 should inform the player, that there are currently issues with strict HTTPS connection and that they should add Roll20 as an exception. It's an workaround, not a solution. Solution would be to have the whole connection strict HTTPS.
Hello Crystal -  Thank you for the additional info! At this time, we have no way of providing additional support for this extension/addon. We apologize for the inconvenience. However, I went ahead and provided your feedback to the development team for future reference :)