I occasionally get nil file errors after I upload to Flightsim.com, so I always do a test download for any new livery to make sure the upload is valid. When I uploaded the livery below yesterday, I downloaded it straight away and the livery was blocked as unsafe. Hence my comment above. When I tried the exact same livery today it downloaded it without error. I use Chrome on WIndows 11, so it may be that one of those 2 is somehow the cause. Chrome config is set to block unsafe downloads, and that is not something I would ever turn off. But not sure if Chrome relies on WIndows 11 to tell it that a download is unsafe, so either could be the culprit. It's not related to only new files, as when I initially encountered the error I also tried a number of new and old downloads, both mine and from other authors, and all MSFS files were blocked. But FSX files downloaded without error at the same time MSFS files were being blocked. So it may be there is something in the structure that is triggering this error. I also upload the the same files to another site and only encounter this problem with Flightsim.com. You mentioned in another post that Flightsim.com file are stored on Amazon AWS servers. Could it be that there be some disassociation between those servers and whatever Chrome or Windows uses to identify an unsafe download? Then Amazon runs an update and all is working again?