Images, maps, tokens and in game cards do not load. Problem persists across broswers

Using google chrome   Version 77.0.3865.120 Windows 10, Javascript is running, Standard windows AV / firewall All previous steps taken Log is included

I can't see pictures loading for anyone's profile pictures I play with, I don't see Maps, Character Sheets, I can't see any pictures on both my 2015 Macbook Pro using Google Chrome totally updated or Safari browser, or my Windows 10 PC (2019 9900k super gaming PC) using Firefox totally updated as well. I have a game coming up with my normal group this Friday. I have restarted all computers, my network router and modem, and every browser many times, even resetting all of their settings and cookies or whatever... Please let me know what to do to fix this ASAP! -Wil 

its something on roll20's end, im having it too

Here too also.

It's totally screwing me tonight. I may have to cancel an entire game. Any help??

So, there are multiple posts about this issue. It seems wide spread. Why is Roll 20 not commenting?? 

I have the same problem. I tried clearing my cache and now I can't see anything at all.

Mine is slowing loading. Warning: I fixed some of my tokens that had disappeared from maps and ended up with duplicates all over the place. My maps where blurry too, but are slowing fixing themselves.

It's the same for me. I'm on Firefox btw, fully updated, and it's also my friend's profile pictures, so I'm gonna guess they'll have the same problem too. And it's also every asset except a scant few in Roll20- even the ones I've uploaded. I hope they resolve this quickly.

Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome&nbsp; and&nbsp; Firefox. RESULT: &nbsp;Same on both browsers Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable&nbsp; all&nbsp; add-ons/extensions. RESULT:&nbsp; No Extenstions installed. issue persists Step 3: Clear your cac he RESULT: &nbsp; Issue persists On a different post it seems &nbsp;like AWS S3 is having issues, it's what hosts most of the images. <a href="https://downdetector.com/status/aws-amazon-web-services/" rel="nofollow">https://downdetector.com/status/aws-amazon-web-services/</a>

Im in the exact same boat.&nbsp; Game was suppose to start at 7:30

My GM was having issue and I created a game under my account and invited him to it and that seems to have resolved the issue for him. his games/images are loading just fine now

Looks to still be down? Or perhaps images are having to "catch up" again? Some images appear to load but only about 2%.

Nope, I was wrong. Looks like&nbsp; <a href="https://s3.amazonaws.com/" rel="nofollow">https://s3.amazonaws.com/</a> &nbsp;is down.

I'm also seeing this, seemed to start on 22/10/2019 somewhere between 11-12 BST. Looks likes it's still not sorted this morning. Cleared browser caches, updated chrome, no addons/extensions, and even tried MS edge, its definitely server side. Update: Looks like AWS suffered a DDoS yesterday for 4-6 hours, taking out their DNS. Claims to be resolved but I'm still seeing issues. 14:45 Now, and still seeing this. Some assets with broken image icon. Loading images to the library seems pot luck if they appear. Loading images directly into Handouts seems to work. 17:12 Some testing of broken links after clearing the browser cache on my side. Delete Broken Image in roll20, upload same image = image still broken Upload Broken Image with new file name = image still broken Edit image and change 1 pixel = image uploads and is visible. Something has cached the broken images at the server side and won't refetch it from amazon s3, nor if the image fingerprint matches. Does roll20 need to do something to flush all these broken images so they can be refetched from the datastore?

I am still having problems with Image loading, even after the twitter update for the problem.

same

Is this still being investigated by Roll20? It's clear there's some problem beyond the initial DNS issues getting to AWS.

Morning, I tried the DNS swap to Cloudflare after emptying the browser cache and a reboot, sadly still have broken images. What is weird is if I delete and upload a broken image again, it's still broken, or if I rename the image and upload it, indicating some kind of 'picture fingerprint cache' somewhere that's holding on to the stale broken image. If I modify the image by a few pixels and upload, the image comes through. This is affecting a handful of recently uploaded since ~20th October. Some additional troubleshooting If I take the S3 link for a working image:&nbsp; <a href="https://s3.amazonaws.com/files.d20.io/images/95130265/OfGOVOK7tCV5ALSSFEQWmg/max.png?1571831240" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95130265/OfGOVOK7tCV5ALSSFEQWmg/max.png?1571831240</a> All is good. For a broken image: <a href="https://s3.amazonaws.com/files.d20.io/images/95140708/8QJOJrHBiojh76UZfoQ8MQ/max.jpeg?1571846405" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95140708/8QJOJrHBiojh76UZfoQ8MQ/max.jpeg?1571846405</a> So this looks like the request gets through to AWS but then gets refused. Nicholas said: Hello all - Amazon is not currently reporting additional issues. However, we have investigated further, and noticed a few other service providers are still reporting similar problems with Amazon. Unfortunately, we are unable to directly resolve this issue on our end, but we will keep an eye on it and try to assist however we can. As a possible workaround, some reports have indicated that changing your DNS provider to Cloudflare's DNS (1.1.1.1) has resolved the issue. You can find additional information and directions on how to do this via this Cloudflare support article: <a href="https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/" rel="nofollow">https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/</a> .

I also have this problem and have a session planned for tomorrow. Any updates on the situation?

Issue is still ongoing. Maybe you need to reboot you cloud storage buckets? In any case it's still broken

Also @nicholas i can't even upload images at this time... (the bar just hangs there) Nicholas said: Hello all - Amazon is not currently reporting additional issues. However, we have investigated further, and noticed a few other service providers are still reporting similar problems with Amazon. Unfortunately, we are unable to directly resolve this issue on our end, but we will keep an eye on it and try to assist however we can. As a possible workaround, some reports have indicated that changing your DNS provider to Cloudflare's DNS (1.1.1.1) has resolved the issue. You can find additional information and directions on how to do this via this Cloudflare support article: <a href="https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/" rel="nofollow">https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/</a> .

Morning, Any update on this issue? Example bad image:&nbsp; <a href="https://s3.amazonaws.com/files.d20.io/images/95140708/8QJOJrHBiojh76UZfoQ8MQ/max.jpeg?1571846405" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95140708/8QJOJrHBiojh76UZfoQ8MQ/max.jpeg?1571846405</a> What testing has revealed: Some images are failing to display, seemingly being denied access at AWS as shown by the link above. Deleting the image from your library and uploading the image again does not fix the issue. Renaming the image and uploading does not fix the issue. Uploading the same image to a different Roll20 account made for test purposes does not fix the issue. Modifying 1 pixel on the image and uploading it, Image is displayed. This suggests to me that Roll20 creates a fingerprint for an image at the point of upload and stores the image single time at AWS if it doesn't exist already. If it does exist it simple uses the one it has already stored at AWS. This looks to be done across multiple accounts, so the image also needs some kind of reference count. Quirks: I have one of the images which is broken in the library imported as an image in a handout. This image is displaying fine. Potentially related to different sizes of the image stored for thumbnail, library use, handout use.

So I deleted all the broken images from my game on Saturday, and thought I'd have a quick try at uploading one of the images again. It is still a broken link however when it gets to roll20's library. Surely if this was a DNS issue it would have fixed itself by now, this very much feels like something else has gone wrong. <a href="https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836</a> That image for a Cloak of Protection, is still returned as access denied from AWS.&nbsp;

#metoo Using Chrome, 100Mb/s internet connection and have this problem since ~1 week.

So we're now a week since this was first reported and zero progress with this issue. <a href="https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836</a> This image and a handful of others still comes back Access Denied from AWS S3 and are broken in my roll20 art library. I've tried all your troubleshooting steps including using a VPN on a different machine, all give the same Access Denied response for the image.&nbsp; Has Roll20 actually run through the troubleshooting list for this, rather than just attributing it to the DDoS attack on the S3 DNS? Surely the direct fall out from that has been cleaned up by now. To troubleshoot Access Denied errors from Amazon S3, check the following: Permissions for bucket and object owners across AWS accounts Issues in bucket policy or AWS Identity and Access Management (IAM) user policies Credentials to access Amazon S3 VPC endpoint policy Block Public Access settings Missing object Object encryption by AWS Key Management Service (AWS KMS) Requester Pays enabled on bucket AWS Organizations service control policy

Any update on this? Its still broken in my art library. <a href="https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/95562603/hWbkXAkl0ltL40lffjE9zQ/max.jpeg?1572244836</a>

Bernd S. said: #metoo Using Chrome, 100Mb/s internet connection and have this problem since ~1 week. Fortunately at least I don't have 'access denied' issues (still). But the images are loading awfully slow. And since this happens only in roll20, I am pretty sure that this is not a browser or cache or DNS issue. Another hint is that it happens in Firefox AND Chorme. I am sure that there went something wrong with roll20 update during the last 2-3 weeks.&nbsp; Suggestion : A good test for this would be a rollback to the state before. If everything's fine afterwards, you'll have evidence. If not, we could seach on.

Any update on this? Whilst the cause may have been the AWS S3 DDoS something else must have gone wrong here, to be still broken now weeks later. Is anyone looking into this?

Images still broken.&nbsp; <a href="https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508</a> All the broken links end up at Access Denied on AWS S3. Caches cleared, alternate DNS, VPN, Alternate PC entirely give the same broken images, same access denied. Also this is a completely new game instance copied from the original, which was the advice to get around the 'dice rolls not showing for all ppl' issue.&nbsp;

So my ISP at home is Plusnet. However, I've also tried this from work on Virgin, on a completely different PC. And also finally on a VPN. Hell I've even tried it from my phone over 4G. Same results from all connections. The AWS S3 links come back Access denied. I've also tried deleting the images from roll20 and uploading them again to run into the same issue. If I change a single pixel and reupload the image, it uploads fine and displays normally.&nbsp; It feels like a fingerprint for an image gets made and used to reference the image at AWS S3, but for some reason for these images, the lookup comes back denied and nothing is clearing it. Are you telling me if you go to&nbsp; <a href="https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508</a> &nbsp;you can actually view the image? Update: So I also had a friend in the Netherlands try and access the URL above, they get access denied, they also then used a VPN based in the USA to access the same link, also got access denied. That's a goodly number of ISPs and routes tried to get to the image which are coming back access denied.

Any update on this from your end? Can you folks at roll20 see the image in my post above? By my count I've tried 2 UK ISPs, 1 UK Phone network, 1 Netherlands ISP, and 2 US VPNs. All of which come back access denied.

Access denied, and I'm a non-VPN'd US user.

PNG's load fine regardless of drag and drop on to the virtual table or using the tool/button. If I drag the 'jpeg' files directly on to the virtual tabletop, the image loads correctly. If I rename the 'jpeg' to 'jpg' and upload the file via the tool/button, the image loads correctly. Uploading the 'jpeg' via the tool, the image fails to load. So we have a winner, for some reason JPGs ending with '.jpeg' fail when uploaded via the tool/button. \o/ And of course, when I'd modified the image by 1 pixel and uploaded it successfully, the file extension had been saved as, JPG, not JPEG, so that also explains that little mystery.

Nicholas, I'm not the user with the error here ;)

I think she meant she saw the same response when clicking on the link Dresden provided for others to use as a test: Dresdon said: Are you telling me if you go to&nbsp; <a href="https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/96350267/ZNMUoChxNQbeZmt8iautzg/max.jpeg?1573147508</a> &nbsp;you can actually view the image?

Keith is correct.&nbsp; I was simply replying to Dresdon's request for others to view the link.&nbsp; Again, I have no errors to report, of any kind.

Yup I think we're good here, I guess I was just unlucky to find this particular bug at the same time as the DDoS of AWS S3 happened, as it muddied the waters when troubleshooting it. I've just renamed my files to 'JPG' for a quick fix.&nbsp; Cheers for chasing it down and finding the root cause. :)