8 / 8
Feb 2017

I have a product (digital) that was corrupt (bad .zip file)..



I have a new, .zip file that is good...



I have uploaded that to my own host (I have a plan where I have both hosted and remote files)...





I was under the impression that when I uploaded the new .zip file.. I could then send out a product update to all buyers of that digital product.. however it it giving me an error because it is a remotely hosted file?



Why?



I have no more space on EJ to upload to.. hence the remote hosted package.. and I'll be damned if Im going to 'up' my package level AGAIN... I have already done so twice!.. just for some more MySQL 'slots'! (which really makes me mad..not even more HD space.. which is pennies now a days)



and your charged for this? (dont you already pay for this bandwidth and storage options with the package/plan?

(just another reason to find an alternative...sigh)



Is there a fix or work around on this?





- (xl97) customer

  • created

    May '13
  • last reply

    Feb '17
  • 7

    replies

  • 1.9k

    views

  • 4

    users

  • 2

    links

This help page explains why sending Updates & Newsletters is an extra-cost service, rather than a standard feature included with a monthly subscription:

4http://www.e-junkie.com/ej/faq.updates.surcharge.htm4



Updates are not available for remotely-hosted files because of the sudden spike in system load and other performance issues that would incur, above and beyond what it takes to serve Updates for an uploaded file. Our system handles Update download links exactly the same as regular paid download links, so with every download attempt, our system would first have to check your remote file URL to make sure our cached copy matches that and, if not, restream a fresh copy from your URL and then serve the file from our local cache, which would result in throttled download performance and a major hit to our local system until we have a copy of the file cached to our Amazon S3 provisions to start serving it from there. Uploaded files don't have those problems because we have a copy of the file synced to S3 within 15 minutes of the upload, so uploaded Updates would be served from S3 from the get-go. We're considering some possible solutions to these issues, so if that all pans out, we might be able to start allowing Updates for remotely-hosted files in the future.



That said, note that you can temporarily upgrade to a larger plan without actually paying the higher rate. When you upgrade to a larger plan, the change in account limits take effect almost immediately, but your first payment at the higher rate is deferred until your next monthly payment is due. It appears your next payment is due on the 21st, so as long as you delete the uploaded file and re-downgrade to your current plan before then, you won't wind up paying the higher rate at all.



We can also offer to delete all files you have uploaded to products that have a Remote Product File URL entered, so you could reclaim the storage space those files are using unnecessarily. To confirm your identity and attend to this, we would need you to email this request to Support along with your E-junkie account password, or your Subscription ID (from your Seller Admin > Account Summary screen), or your original activation code (from the original "Account information" email we sent you at registration):

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

2 months later

I'm having the same issue and receive the error.



Can you tell me which plan allows for remotely hosted files for Product Updates?



One of my updates files exceeds 260MB



Thanks!

Mark

We have no plan level that can use remotely hosted files for product updates. Your current plan level has 500 MB of upload space available, and our file uploader can handle files as large as 500 MB each, so your 260 MB file should be no problem.



To send your Update, edit the product and use the Upload Product File button to upload your file, then click Next until you reach the Remote Product File URL field, where you should temporarily delete that URL and click Next until you can Submit changes. Once the update downloads have been claimed (I'd say give it a week or so), you can re-edit the product to delete the uploaded file and restore the Remote Product File URL. Note that sending Updates requires payment of a nominal fee to cover our costs to provide this extra service; for a 260 MB file, the cost would be $1.07 per recipient.

ok thanks.



So if I have 1500 people to send updates to then my cost would be $1500.

I find $1.07 a bit high. I'm hosting with MediaTemple on a Dedicated server which handles spikes larger then this with no issues. I'm sorry it puts a load on your servers, I don't know why. I wouldn't mind paying a fee for it but $1.07 is not nominal at all. I understand you have many users but it's still too high unless you are running a very small shop. This among other things questions our future with e-junkie.

I've asked Development and Management to consider revising the per-MB component of our Updates fee, as our actual overhead costs may well have changed since the fee formula for Updates & Newsletters was first devised.

3 years later

I am shocked that there is no better way to do this. The price per update is definitely too high, and the inability to update remotely hosted files makes e-junkie and untenable solution long term. After being a customer for a loooong time I'll be switching to another solution based on this issue alone.