
An important detail is that when downloading files larger than 5 GB, MEGA will warn us that we are exceeding the limit: Free registered accounts may have 5 GB transfer fee up to 24 hours, although it is usually less time, around 6 hours or so, although MEGA tells us it will depend on time of day, ISP and country, for what may be more. Interrupted transfers will resume automatically when a certain time elapses and we have more data transfer quota. If I then start a 17 GB d/l, it nearly immediately switch to bandwidth exceeded.According to MEGA official website, transfer fees are measured by IP address only, and not by the registered user that we use. Closing JD2, waiting for it to shutdown and restarting JD2, clears the issue and refreshing the account shows the same 740 MB d/l. Refreshing the account info, shows 740 MB d/l and then switches to Bandwidth exceeded error. I next set the max chunks, max downloads, and max downloads per hoster to 1. So it looks like JD2 reports the queue size to Mega and gets blocked by the total size of the queue. If I disable them so they don't queue for download refreshing the accounts clears the bandwidth exceeded. I should note, that I have some files in the D/L larger than the old 5GB limit. If I switch IP address with JD2 running, then refresh the account in JD2, it initially reports bandwidth used = 0, and immediately marks it as bandwidth exceeded. This account has NEVER been uploaded or downloaded from. It does recover from Mega's transfer limit exceeded.Įdit: I added a never before used mega account to JD2 and in the verification message it reports "verified logins: Free Account | Bandwidth used 2.58GB. It seems like JD2 doesn't recover from 509 Bandwidth Limit Exceeded.

I've found that the only way to get JD to start downloading is to manually stop D/L, shut down JD2, then switch IPs and restart JD2. IF JD2 gets a 509 response from mega, doing a reconnect to a new IP address does not clear the error, even then other programs like megadownloader can download from the same IP address. I use a VPN and I have a reconnect script in JD2 that selects a random endpoint if I click Reconnect.

I've notice a change in behavior as well.
