Data fetch failed when using AWS S3

16 views
Skip to first unread message

Kailee Yoshimura

unread,
Aug 28, 2024, 12:35:06 AM8/28/24
to WashU Epigenome Browser
Hello,

I have been trying to upload remote tracks (longrange.gz files) using AWS S3. I am running into issues after following the instructions to enable CORS using the WashU documentation. I have ensured that my data is publicly accessible and have copied and added the JSON CORS set up from the documentation to my bucket that has my remote files. Is there another setting/step I'm overlooking?

I also tried loading the remote track URL provided for the example bigWig file (http://washu-track-host.s3-website-us-east-1.amazonaws.com/bigwig/TW551_20-5-bonemarrow_MRE.CpG.bigWig) and it is still saying that the data fetch failed.

Let me know if you need any further information and thank you for your help!

lid...@gmail.com

unread,
Aug 28, 2024, 1:25:58 AM8/28/24
to WashU Epigenome Browser
Hi Kailee,

The reason is the default S3 url is with http, not https
then you would need to use our http site, not https site to visualize your files, http://epigenomegateway.wustl.edu/browser/, notice that is http://, not https if you setup https on your hosting, you can use the https site

see the screenshot with our example file showing on the http site, let me know if you still have issues.
thank you!
Screen Shot 2024-08-28 at 12.23.56 AM.png
Reply all
Reply to author
Forward
0 new messages