Just tried it on my end (Win7 SP1 x64, Manga Downloader 46.5), chapter 39 downloaded without any error. It might be the toonily.com server timing out momentarily, for some undetermined reasons
Edit: tried downloading the whole story, and it started erroring (on all further attempts) after 12 more chapters. I suspect a very touchy bandwidth protection, especially during peak hours.
If such isolated errors happens too often, I would suggest lowering the “concurrent downloads” settings, and/or increasing the “pause between pages downloads” timer (mine’s set to 1 concurrent download 2 seconds pause for maximum safety), in case the issue comes from the server triggering its bandwidth protection measure.
Also, due to the lockdown, a lot of these websites have seen their bandwidth consumption increase significantly, and not all managed to gather the funds to upgrade their hosting solution plan, so random timeouts do happen more frequently.
In my case I’m mostly downloading from mangadex, and despite my safe settings and their upgraded servers, I get between 0.5% to 1% of chapters where the server doesn’t deliver its list of pages, so I have to queue that chapter download again and it works just fine this second time. I hope your issue is the same and can be fixed by re-downloading the missing chapter.
It started working the day after. You're probably right! Thank you so much!!!
Meanwhile I’ve started downloading some toonily entries and just encountered the same issue, where it would stop downloading chapters after a while (in my test, it stopped at chapter 27 out of 30).
Trying a 4 hours and a half later, I could download chapter 27, 28 and 29, but the final chapter 30 refused to work again, only getting this error over and over in the jvm_log.txt:
Error while downloading image: org.apache.http.client.ClientProtocolException
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source) Caused by: org.apache.http.ProtocolException: Target host is not specified
Tried an hour, later still no chapter 30 downloading, still the same error.
I just checked in my browser and the blocked chapter can be viewed normally (tested browser: Chrome), so it doesn’t sound like a blanket IP ban.
Then I tried downloading a different manhwa (using Manga Downloader again) on toonily, and it works just fine… for 4 chapters only, then the same error (posted above) shows up in the jvm_log.txt
Not exactly sure what they’re doing here, maybe:
Temporarily banning a cookie ID/user agent from loading more chapters (= lists of pages' URL) from the same entry once they hit a certain limit?
While also having a site-wide, global limiter (with a slow cooldown), only granting access/serving images' URLs for 100-150 pages per hour, after the limiter was triggered by accessing/requesting too many files? (ex: more than 500 files in under 30 minutes)
Stats of my tests:
1st manhwa stopped downloading after approx 600 files / 13 chapters (downloaded within 20 minutes)
(nb: some manhwa have 1 file per page, while other have 1 file per panel/1.5 panel, so for the same 20-pages chapter, some manhwa will have 20 files, 50 or 70 files)
I’ll try downloading the remaining chapters from these 3 manhwa tomorrow and report back on the results.
In the meantime, patience (trying again the following day) seems to be the best remedy so far
18 hours later, tried downloading the rest of these manhwas. The chapters that errored yesterday are still giving out the same error and refusing to download, while other chapters (of the same manhwas) are downloading normally. Could it be a cookie/session ban that “remembers” the chapters that triggered the block? I’ll test on a different computer (on the same network) tonight and report back.
EDIT (October): Toonily is down today so I can’t test again, but I remember I was getting errors on the second computers as well. So I checked how easy it would be to manually download chapters using DownThemAll, and it turns out Toonily can become a little unreliable, and is rather conservative with its bandwidth: the browser needs to wait a few milliseconds for each image to load (if you only scroll down to the bottom of the page, it only loads the first and last few images), and you often need to switch between Server 1/2/3 to get all the images of a chapter (back in September, Server 1 wouldn’t load 1-2 pictures every 2 chapters, Server 2 was more reliable, Server 3 (when available) had no issue at all).