Bad remote download link for (File Name) (cache file served)

[miste]

I'm getting this lately. This problem only began a couple weeks ago, and it began with files which had been served successfully since forever. I changed nothing on my server, I DID change the names of the actual files. But I've tried updating the code on my site, just in case some part changes, I've tried removing then re-adding the links, I've pinged eJunkie from my server, I've downloaded the files in a browser to make sure they are there. It's not every time. The same file will be successfully served one purchase, then fail the next. It is utterly mystifying. Any advice?

[E-junkie_Guru]

First, it may help to review how our Remotely Hosted Downloads feature works -- see the "Here's how it works" section here:

http://www.e-junkie.com/ej/help.file-downloads.htm#remote



When you get a notification that the remote download link is not accessible and the buyer was served the file from our cache, the only real problem there is that we could not verify our cached copy was still identical to your remote file -- i.e., we could not tell whether your remote file may have been updated after we'd cached a copy from a prior download, so we went ahead and served the download from that cached copy as usual, just as if we'd confirmed your remote file hadn't changed.



If you're getting this notification every time for a given file, there may be something incorrect about the Remote Product File URL you'd specified for that product; we'd be glad to take a closer look if you could tell us which product is affected, and feel free to email us if you'd rather not discuss details here on the forum:

https://www.e-junkie.com/ej/contact.php



If you're getting this notification only sometimes for a given file, while at other times the same file is delivered without notification, there's probably just some sort of sporadic networking glitch somewhere along the path across the Internet between your server and our Tucson datacenter, or possibly sporadic performance issues with your remote server, neither of which is a problem for us as long as we have a cached copy of your file to deliver to buyers. If you're sure you haven't updated your remote file since the last time that file was purchased and downloaded successfully, and if buyers aren't contacting you to say their file had a problem, you can just disregard these notifications.

[miste]

Thanks, that allays all my concerns actually. I'll contact support if someone says they're having problems and otherwise ignore the warning. It does make me wonder, why do I only have 500 gb of uploaded stuff if you're just gonna cache my file anyway? Wouldn't it be better to give me like 8 gb of upload space or access to same, and not let me use remote files at all? That seems like it would be easier on your bandwidth.

[E-junkie_Guru]

The difference is that we're obligated to retain uploaded files in perpetuity as long as the seller maintains an active subscription and doesn't delete the relevant products, whereas remotely hosted files may not use any storage or bandwidth at our end if they don't get purchased in the first place, and we can delete our cached copies of rarely-purchased remote files at any time as needed to optimize our storage utilization, since we can expect to simply re-stream a fresh copy from the remote server if and when that file may finally get purchased again.