Assets disappearing (and reappearing) randomly

support
1

We’ve customised our Discourse with some custom images and fonts that I’ve loaded in the Assets topic. But these assets keep disappearing and reappearing at different times in different browsers. Sometimes it leaves us with no web fonts (not the end of the world) but often it leaves us with no logo, and without vital images in our custom navigation.

It seems like a caching issue, and occurs more frequently when we’re doing customisations (though this may just be because we’re more likely to notice when we’re doing these!)

Has anyone else had similar issues? We want to make our Discourse public, but are wary that it might just appear broken!

1 Like
2

An example of such an asset at the moment is:

https://virtual-host-discourse.global.ssl.fastly.net/uploads/ind/original/1X/0a1f0d23828689af64572baaf8fd9a9d1a349a20.png

Which produces:

Screen Shot 2015-07-24 at 13.35.24.png1880×872 731 KB

Styles generated by Discourse:

Screen Shot 2015-07-24 at 13.36.12.png1118×280 86.9 KB

And here are the fastly.net 500 errors from the console:

Screen Shot 2015-07-24 at 13.40.10.png2944×540 307 KB 

[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (0a1f0d23828689af64572baaf8fd9a9d1a349a20.png, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (583e90b3bfea95253852244619f735b7087bfe44.png, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (2782d0c0e316d855c33a884fea104521cc5bbb34.woff, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (1c945c18ddc57d1a0b74912beeb0860a82448f26.woff, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (c07c234a7e2db36a70e5ddd2ff3b239906be58de.ttf, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (Internal Server Error) (63d5e903887079298fe4675c7f9269f3d3d29005.ttf, line 0)
3

@eviltrout will have a look soon, we moved CDNs and may have left a few links unmapped

Don’t worry image is still there it’s just on a diff domain

2 Likes
4

Thanks, Sam. From the errors, that’s what it looks like.

5

Did you recently restore from a backup or something? It’s weird because all those paths should have been updated automatically but were not!

I’ve fixed and redeployed and you should be good to go now!

2 Likes
6

We didn’t recently restore from a backup or anything, so no idea why it happened. But whatever you did seems to have fixed it, so thank you! :smile:

7

Please let us know ASAP if it happens again. I don’t expect it will but we can take a deeper look if those old links come back.