Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Madokami: Missing from remote #71

Open
rpoovey opened this issue Feb 11, 2019 · 5 comments · May be fixed by #77
Open

Madokami: Missing from remote #71

rpoovey opened this issue Feb 11, 2019 · 5 comments · May be fixed by #77

Comments

@rpoovey
Copy link

rpoovey commented Feb 11, 2019

After using cum for a couple months with Madokami, I now get the same error any time I try and download issues.

==> Removing **MANGA NAME** **CHAPTER NUMBER**: missing from remote

@CounterPillow
Copy link
Collaborator

I think madokami now servers 404s as a ratelimit (which is fucking stupid), try lowering the number of threads in the cum config.

@rpoovey
Copy link
Author

rpoovey commented Feb 15, 2019

Download threads are set to 1. Previously 4, then 2.

@alexxsong
Copy link

alexxsong commented Feb 25, 2019

I am having the same issue with threads set to 1

as a dirty workaround I modified the base.py scraper to ignore 404 when checking availability and I;m at least able to use it for madokami for now.

@drewbitt
Copy link

Still broken. The issue comes down to not being able to do http auth on download links anymore. It now relies on setting a cookie when browsing the main site and using that cookie to not get a 404 when downloading. I don't see any rate limiting in my testing.

@rpoovey
Copy link
Author

rpoovey commented Jul 27, 2019

Still broken. The issue comes down to not being able to do http auth on download links anymore. It now relies on setting a cookie when browsing the main site and using that cookie to not get a 404 when downloading. I don't see any rate limiting in my testing.

Any idea on how to fix this?

@phantom-voltage phantom-voltage linked a pull request Feb 26, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@CounterPillow @alexxsong @rpoovey @drewbitt and others