Github Issue for this bug #265 Re-opening this issue because it was never fixed and I'm getting bugs about fonts showing up oddly. Here is the latest error messages showing in Chrome for both fonts and images: 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 font '<a href="http://imgsrv.roll20.net/?src=fonts.gstatic.com/s/gloriahallelujah/v8/CA1k7SlXcY5kvI81M_R28cNDay8z-hHR7F16xrcXsJw.woff2" rel="nofollow">http://imgsrv.roll20.net/?src=fonts.gstatic.com/s/gloriahallelujah/v8/CA1k7SlXcY5kvI81M_R28cNDay8z-hHR7F16xrcXsJw.woff2</a>'. This content should also be served over HTTPS. jquery.1.8.2.min.js:2 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 image '<a href="http://imgsrv.roll20.net/?src=i.imgur.com/3r76gXC.png" rel="nofollow">http://imgsrv.roll20.net/?src=i.imgur.com/3r76gXC.png</a>'. This content should also be served over HTTPS. jquery.1.8.2.min.js:2 From Github Issue #265 Ramblurr commented on May 30, 2014 Roll20 uses TLS by default, yay! But the content proxy server ( imgsrv.roll20.net ) isn't set up to deliver content over TLS, so the browsers are complaining. Firefox is the most strict in this regard. For passive content (e.g., images), this isn't a big deal as Firefox allows the content. But for "active" content (e.g., fonts) the content is blocked completely. This makes it impossible to use webfonts in our character sheets on Firefox. Ramblurr commented on Oct 26, 2014 This bug now affects Chrome too! Chrome now considers fonts to be "active" content. It has silently blocked mixed HTTP active content from HTTPS pages for awhile.Essentially custom fonts are broken in the to major browsers. Which is a huge drag :-( Fonts give a lot of character and personality to sheets. Please install a TLS cert on the imgsrv.roll20.net server.Any chance this could be bumped up the priority list? Heilemann commented on Nov 2, 2014 +1 to priority bumping. This is a pretty big detractor from the potential of the sheets. IanDominey commented on Mar 25, 2015 Yeah, this issue is really causing me pain and it seems reasonably easy to fix. bitspersecond commented on Mar 25, 2015 I'm in agreement. I'd like to see this addressed as well. Has anyone put a suggestion on the suggestion forum? I'd sacrifice one of my votes to add it to this if others go along as well. One vote isn't likely to get it noticed…. IanDominey commented on Aug 15, 2016 I don't get why this isn't resolved yet. All it requires is setting up a TLS cert on the proxy server. They could even buy and use a wildcard cert on all of their services.