[[statics]] content not served

1

Hi, I’m using the [[statics]] section of the fly.toml config file to serve a couple of JS files.

I deployed my app 4 months ago, and it has been working fine until yesterday when I noticed that the files from statics were not served (it may have started before as it is a user who told me about it).

When doing a request to get them, I got a 404 error:

❯ curl https://api.hootify.io/static/hootify.js

{"status":404,"message":"*GET /static/hootify.js* not found","name":"NotFoundError"}%

I restarted the app, but that didn’t help. I deployed it again (building a new image) and it fixed it :thinking:

Was there an error on fly’s side recently that would explain this? Could it be that the files taken from the docker image had expired in some sort of bucket where they are served from?

Thanks

2

Hey @guims767

Yep, that was an error on our side:

3

Thanks very much, glad to see it is fixed :partying_face:

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.