If wanted, you can now adjust the pause-mode speed in the top right corner by doing a right click inside the speed graph (alternatively also in the bottom right corner, if you've enabled quick settings before, more details see bottom of this support article) JDownloader will stop once all currently running downloads have been completed A speed limit will be active (see speedlimit setting in point 2. When downloads are running and you press this button, the following things will happen:
In the top left corner you will find a "pause" symbol right next to the "play" symbol: Whenever a speedlimit is active and downloads are running, you will see a red line in the speed graph in the top right corner:Įxplanation of the two different speed limit settings: useful if you're part of a bigger network and want to leave some bandwidth for the other people in this network. download speed according to your preferred limit. JDownloader provides two settings which are essentially doing the same: Limiting your max. If I then start a 17 GB d/l, it nearly immediately switch to bandwidth exceeded.Posted by pspzockerscene psp, Last modified by pspzockerscene psp on 21 February 2023 02:13 PM 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.
0 kommentar(er)
