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

API responded with 429 Too Many Requests. #996

Closed
fullnitrous opened this issue Sep 14, 2020 · 6 comments
Closed

API responded with 429 Too Many Requests. #996

fullnitrous opened this issue Sep 14, 2020 · 6 comments

Comments

@fullnitrous
Copy link

Hello,

I have already searched around quite a lot in order to find out how to fix this but nothing has worked. Downloading galleries from deviantart is extremely slow and changing to your own client-id and client-secret does nothing.

How can i check that the client-id and secret have been correctly loaded into gallery-dl? I have already tried the command line argument for passing a config file but again, using your own account seems to only make it worse.

Currently, I've tried

  1. Passing the config file as a command line argument
  2. Putting the config file in it's supposed directory
  3. Getting refresh token by gallery-dl oauth:deviantart

Nothing makes it better, I've had downloads running for 24 hours straight now and they are basically stuck because of the exponential wait.

How do i fix this, please help

@fullnitrous
Copy link
Author

For some reason running it on my vps with linux works

@biznizz
Copy link

biznizz commented Sep 15, 2020

Since you already got a client-id and client-secret from publishing an app for gallery-dl, have you tried increasing your wait-min up a few seconds? Try setting it to a value of 2 and see if it works.

It's also probably a good idea to wait a day or two so the amount of traffic coming from your end stops triggering the error everytime you run the command; the site might think you're a bot at the moment.

Keeping the config file in your USER folder is the best place for it. Does the config detail where to write the cache file? It should be towards the bottom like this (I've set it so that my cache is generated in my USER folder next to my config):

    "output":
    {
        "mode": "terminal",
        "log": {
            "level": "info",
            "format": {
                "debug"  : "\u001b[0;37m{name}: {message}\u001b[0m",
                "info"   : "\u001b[1;37m{name}: {message}\u001b[0m",
                "warning": "\u001b[1;33m{name}: {message}\u001b[0m",
                "error"  : "\u001b[1;31m{name}: {message}\u001b[0m"
            }
        },
        "logfile": {
            "path": "~/gallery-dl/log.txt",
            "mode": "w",
            "level": "debug"
        },
        "unsupportedfile": {
            "path": "~/gallery-dl/unsupported.txt",
            "mode": "a",
            "format": "{asctime} {message}",
            "format-date": "%Y-%m-%d-%H-%M-%S"
        }
    },

    "cache": {
        "file": "%USERPROFILE%/cache.sqlite3"
    },

    "netrc": false
}

@mikf
Copy link
Owner

mikf commented Sep 15, 2020

This isn't the first time someone had this exact problem, which always resolves itself after some time, and I think I've finally figured out what is going on: The access-token from the default, "slow" client-id is cached for 1h and even when entering a new client-id value, it still gets used for that amount of time. So just clearing your cache (--clear-cache) or waiting for an hour should "fix" this.

How can i check that the client-id and secret have been correctly loaded into gallery-dl?

By using -v/--verbose together with a dA URL:

$ gallery-dl -v deviantart.com/user
...
[deviantart][debug] Using custom API credentials (client-id 10608)

@fullnitrous
Copy link
Author

Ok, gotcha, also just wondering, when downloading from some profiles, the images are blurred. Though nsfw pictured are fine. I suspect this is because of watchers only. Can you bypass this by using username and password when using gallery-dl and having the account watch the target account. Or is there a easier fix?

@mikf
Copy link
Owner

mikf commented Sep 15, 2020

Watcher-only/premium stuff hasn't been implemented yet. See #995.

@fullnitrous
Copy link
Author

Ok, thanks, issue is resolved. You can close this thread.

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

No branches or pull requests

3 participants