-
Notifications
You must be signed in to change notification settings - Fork 213
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
[BUG] PRAW exception: received 400 HTTP response #947
Comments
Have you recently had to change your reddit password? If so you need to re-authenticate. Just delete the "user_token = fakeusertoken1234" line in the default_config file (make a copy of the file first as a backup just in case) and run another command with --authenticate which then bdfr will prompt you with a link. |
Thanks for the assistance. Yes, I was forced to reset the password by Reddit.However I did try deleting the line in my config with user-token and reran the download authenticate just in case but it continues to error out with a JSON decode error. Again no error without --authenticate |
What is the new error? |
if i remove the user_token line:
|
I think this happened to me once. If I recall there's two config locations, one where bdfr itself is installed, and one in your users folder. I'm on Mac, but the user location is in the readme. I think I had to remove the user token line in both configs, then it prompted me with a url to login via a browser the next time I used This may help (try without reinstalling first, not sure if it's needed): Hopefully that works! |
Many thanks for trying to help ymgenesis. Apparently I have 7 of these default_config.cfg files, what a mess.
No 'Lib\site-packages\bdfr\default_config.cfg' as linked. I ensured the user_token line was removed from all of them , but --authenticate continued to error out as above. So I then tried pip install --upgrade --force-reinstall bdfr Insane to me this #884 bug has been open for a year without resolution. Seems a lost cause. I really miss v1 when bdfr didn't depend on python. |
Well that's not true because the BDFR has always been written in python. Also that bug is partly from pipx, which is not the same. You can manually specify a configuration file path if you're not sure which one is being used. |
I just meant it was a lot easier to use when it was an executable.
If I remove --authenticate but use --config it works. |
Providing part of the traceback is as useless as providing none. Can you provide the logs? |
I already posted a full traceback the same day.
|
A traceback is not the logs. Hence why I asked for the logs. They, among other things, say which configuration file you're using, which will be useful in helping you resolve this problem. They will also tell me what version of the BDFR you are running, and other important information, which is why there is a section for the logs in your bug report that currently only has a single line, which is not what was asked. Hence me asking for them now. If you're unhappy it's not fixed, you're more than welcome to submit a PR that does so. |
Nice. If I could fix it I'd have already done so. If you want me to upload a log please direct me to the log you want me to upload. |
This is an open-source project. If you are unhappy with the state of it, you can learn and contribute to it and get it to a place where you are satisfied. Else you can fork it and do what you want. If you're unable or unwilling to do that, you'll have to wait for someone else, such as me, to do it. That'll happen when I have the time and the motivation, since it's a project I do entirely in my free time and without compensation. Otherwise, something such as GitPay may be helpful, as you can provide a monetary bounty for having the issue solved. Right at the top of this page, you ticked the box that said you'd read the document Opening an issue. That and the README contain clear instructions on what log file to upload, which is why it's linked right at the top, and why you're supposed to actually read it before ticking that box. It will direct you to the file to upload. |
Not sure what warrants the attitude, but regardless I'll continue to provide information to help fix this bug. The Opening an issue page states:
The readme states:
this contains a file last updated [2021-05-30] other than that I see nothing other than 0 byte files, and one single 4kb file with the traceback I posted above. Fingers crossed a python developer can help you if you don't have time to work on the project anymore, it's a great project and provides an amazing service when it works. edit: |
Is this the development version? |
I just use the default version the readme says to use: |
Can you install the development version with |
|
Sorry it's |
This worked for me as I was having the same issue |
Description
When trying to use bdfr I get the error "PRAW exception: received 400 HTTP response" for all downloads.
I presume it's related to me being forced to reset my password on reddit, but as bdfr uses an app client id and there being nothing in the documentation about needing to change credentials after a password reset, I don't understand why it's now not working.
Command
python3 -m bdfr download --authenticate C:\bdfr\ --sort new --user nascentt --submitted
Environment (please complete the following information)
Python 3.9.13
Logs
Edit:
Ok if I remove --authenticate it works (until it hits a rate limit). So there seems to be a bug where bdfr needs to reauthenticate but it won't.
The text was updated successfully, but these errors were encountered: