View Single Post
  #1  
Old 25.04.2015, 17:41
maxmaster maxmaster is offline
Bandwidth Beast
 
Join Date: Dec 2014
Posts: 139
Default Premiumize - "Daily Limit reached"-message not handled properly

I hope this is the proper section for MOCH-problems, as it's a JD2-only feature.
If not, please move this thread.

---

When Premiumize is responding with a "daily limit reached"-message, JD2 is not switching to a different way of downloading (premium-account, free user or just showing a waiting-timer), but instead keeps on retrying every second.

Here's the error-log:
Spoiler:
Code:
--ID:584TS:1429972342941-4/25/15 4:32:22 PM -  [jd.http.Browser(loadConnection)] -> 
{"result":null,"statusmessage":"Daily limit reached for this host!","status":0}

--ID:584TS:1429972342941-4/25/15 4:32:22 PM -  [jd.plugins.hoster.PremiumizeMe(handleAPIErrors)] -> PremiumizeMe Exception: statusCode: 0 statusMessage: Daily limit reached for this host!
--ID:584TS:1429972342941-4/25/15 4:32:22 PM -  [] -> jd.plugins.PluginException: DB connection problem
	at jd.plugins.hoster.PremiumizeMe.handleAPIErrors(PremiumizeMe.java:443)
	at jd.plugins.hoster.PremiumizeMe.handleMultiHost(PremiumizeMe.java:294)
	at jd.plugins.PluginForHost.handle(PluginForHost.java:1235)
	at jd.controlling.downloadcontroller.SingleDownloadController.download(SingleDownloadController.java:385)
	at jd.controlling.downloadcontroller.SingleDownloadController.run(SingleDownloadController.java:561)
Reply With Quote