#1
|
||||
|
||||
mega.nz: wrong transfer quota left displayed
In normal way with an account bought from new, the bandwidth quota is displayed correctly until the end of the premium membership.
But if a premium account was renewed before the end (ie for increasing total bandwidth) JD2 doesn't handle correctly the new transfert quota. Removing and adding the account seems to have no effect. Maybe there are some changes in the api. (which tag to use to post the premium account?) Last edited by GTD; 20.01.2017 at 10:39. |
#2
|
||||
|
||||
Send logins to support@jdownloader.org
Please also post screenshot and/or explain what should be shown in JDownloader.
__________________
JD-Dev & Server-Admin |
#3
|
||||
|
||||
__________________
JD-Dev & Server-Admin |
#4
|
||||
|
||||
This is the real quota as showed on mega.nz website:
This is the quota reported by JD2 after the renewal of the premium membership: |
#5
|
||||
|
||||
Today all things seems to be ok :|
|
#6
|
||||
|
||||
Mega has 3 different counters
1.) max 2.) used 3.) reserved Website only uses 1 and 2. JDownloader (by default) also makes use of 'reserved' traffic. You can now disable that in Settings-Plugins-search for mega 'reserved' traffic: When you start a download, mega will reserve the traffic for the file and then delayed check how much traffic really got used.
__________________
JD-Dev & Server-Admin |
|
|