search

mikf / gallery-dl

Command-line program to download image galleries and collections from several image hosting sites
GNU General Public License v2.0
11.36k stars 925 forks source link

[Kemono]Timeout and EOF Errors During Download #5416

Closed 1223334444abc closed 5 months ago

1223334444abc commented 5 months ago

When downloading, I often encounter the following timeout errors and EOF errors:

[downloader.http][warning] HTTPSConnectionPool(host='c6.kemono.su', port=443): Max retries exceeded with url: /data/0d/6c/0d6c3d305e56d5829518364aa3c04cb39f1a3d5c11d772390f1614b5a6a10989.jpg (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1131)'))) (69/100000)
[downloader.http][warning] HTTPSConnectionPool(host='c6.kemono.su', port=443): Max retries exceeded with url: /data/0d/6c/0d6c3d305e56d5829518364aa3c04cb39f1a3d5c11d772390f1614b5a6a10989.jpg (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1131)'))) (70/100000)
[downloader.http][warning] HTTPSConnectionPool(host='c6.kemono.su', port=443): Read timed out. (read timeout=30.0) (71/100000)

However, when I access Kemono through a browser and view the corresponding images, everything works perfectly fine.

Could it be that gallery-dl is restricted, or is there some network access that is not going through the HTTP proxy connection?

mikf commented 5 months ago

I don't think kemono explicitly restricts gallery-dl. Network access should all go through a proxy server when using --proxy or the equivalent config file option.

Maybe it is just the c6 server that's causing these issues, or a problem with your proxy that sometimes drops a few packets and times out?

1223334444abc commented 5 months ago

I have tried more network proxies and found that although the probability of connection timeouts and EOF errors reported in different regions varies, most of the errors are caused by 'c6.kemono.su'.

In some network environments, the same error can persist for several hours, leading to a complete halt in downloads. In other network environments, the error occurs a few times and then the download continues normally. Meanwhile, browser access is normal.

I wonder if the servers are randomly assigned, and problems arise when assigned to a faulty server?

I will continue to observe this situation.