Looking at the Glitch, I think it might just be a filename issue. The uploaded file is called ella's-instagram-archive.wacz but its referenced as ellas-instagram-archive.wacz.
I think Glitch does not allow renaming the file, so would recommend re-uploading without the ' in the filename.
I found this by looking at the Logs on glitch, but we can probably improve the error handling in the web archive starter also…
Looking at it further, this might be an issue with Glitch itself… it seems like the file is returning an empty URL. Perhaps it is too big for glitch?
I would try re-uploading the file without the quote in the filename and seeing if that works…
I re-uploaded now without ’ and - in the filename and the reference is correct now, but it is still returning as not found… it could be too big… Do you have any suggestions of where I could host the file alternatively if it is too big for glitch?
Yes, though I wish they would just not allow the download instead of having it fail silently!
This is something we’re trying to figure out so that we can recommend a solution.
Most cloud-hosting services that can host files should work. I don’t know of any free options, but cloud-hosting services like Linode, DigitalOcean, etc… all should work fairly well, though they’re not free.
Google Drive also can work, but is a bit slow. Actually, looks like OwnCloud has a free tier.
I’ll update if I have any better solution… All that’s needed is file storage.