-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
On first search in web "too many 429 error responses" #2178
Comments
will look into it |
Same problem, running the command with only the query as parameter |
Did you try in v4.2.8 or 4.2.7? |
On v4.2.8 |
The issue you're encountering is related to Spotify's API rate limits. The limit is calculated based on the number of API requests made within a 30-second window. I suggest we close this thread since the problem is related to the API rate limits. Also it is working fine on my machine
|
Waiting for a while does nothing. I've been getting this error for weeks now. |
Ok, I just want to better understand how you're making the API requests. For example, if you're using the search feature, how many searches are you doing, and how quickly are they happening? It would really help me out if I could reproduce the rate limit issue on my side, so I can figure out a fix. Could you let me know exactly what you're doing or any patterns you've noticed that seem to trigger the problem? Thanks |
I personally just do But it seems like my problems might be related to #2111 instead. |
Please look into #2142. Many users have shared their solutions. One user mentioned this, and I recommend trying it:
|
Yeah, I've already fixed it by switching to my own app. |
Duplicate of #2142 |
System OS
Windows
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
4.2.7
Expected Behavior vs Actual Behavior
When doing the first search in the web interface, no results are returned.
Steps to reproduce - Ensure to include actual links!
spotdl web --web-use-output-dir --bitrate 160k --m3u playlist
Then do the first search in the web interface
Traceback
Other details
No response
The text was updated successfully, but these errors were encountered: