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

Auth failed even when using the Chrome plugin #712

Open
jimbo831 opened this issue Feb 14, 2025 · 8 comments
Open

Auth failed even when using the Chrome plugin #712

jimbo831 opened this issue Feb 14, 2025 · 8 comments

Comments

@jimbo831
Copy link

jimbo831 commented Feb 14, 2025

I use the Chrome plugin to quickly copy my updated auth.json info every time I reload the website. Suddenly this time it is giving auth failed. I even tried looking the info up manually in both Chrome and Safari, logging out and logging back into OF, and restarting my browsers, but nothing is working. I only get "Auth failed" and the logs don't show any more details. I'm not sure where to go from here as I am very sure all of the info in the auth.json file is correct including the USER_AGENT string.

@jimbo831
Copy link
Author

Just to try one more thing, I also downloaded Firefox and tried the browser extension there and still go "Auth failed".

@eyeoniqbond
Copy link

I am pretty sure you'll need to include more info for anyone to of any help. I had some auth failure issues too at first. If you have a log file, screenshot of the error message when it fails, and maybe a screen of your auth.json format with the personal info redacted that might help.

@jimbo831
Copy link
Author

I would have included these but they didn't seem to have any helpful information. Just in case, here is the error I get:

config.json located successfully!
You are running OF-DL version 1.7.77
Please update to the current release on GitHub, 1.8.1: https://github.com/sim0n00ps/OF-DL/releases/tag/OFDLV1.8.1
auth.json located successfully!
rules.json located successfully!
FFmpeg located successfully
device_client_id_blob and/or device_private_key missing, https://cdrm-project.com/ will be used instead for DRM protected
videos
Auth failed, please check the values in auth.json are correct.

If you have previously been able to auth successfully, the most likely cause of this is that your browser has updated,
which will change the values of the USER_AGENT string. The version change to this string is usually very minor and easy to
overlook, but even a slight difference will cause an authentication failure.

If you are struggling to authenticate, you may want to try the browser extension which is documented here:

https://sim0n00ps.github.io/OF-DL/docs/config/auth#browser-extension

Press any key to exit

And here is my log:

2025-02-17 15:59:55.253 +00:00 [ERR] Auth failed

@eyeoniqbond
Copy link

This is the same thing it was telling me when I knew I had copied the correct info because I just used it in scraper successfully. I would suggest editing the auth.json directly to make sure all the quotations and semi colons are where they should be according to the official guide at
https://sim0n00ps.github.io/OF-DL/docs/config/auth

Pay close attention to the formatting of the last line, that's where my issue was. It's "COOKIE": "auth_id=xxxxxxxxx; sess=xxxxxxxxxxxxxxxxxxxxxxxxx;" } all in the same quotations except for the closing script bracket at the end. And equals signs after the designator with semi colons separating and ending them. The second example on the guide is what I used then it worked fine.

@jimbo831
Copy link
Author

I'll check on this and update the thread. I have previously just been copying from the plugin without any issue until it suddenly stopped working.

@jimbo831
Copy link
Author

Everything looks right to me. I'll post my auth.json file with some info redacted:

{
"USER_ID": "XXXXXXXXX",
"USER_AGENT": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36",
"X_BC": "XXXXXXXXXXX",
"COOKIE": "sess=XXXXXXXXXX; auth_id=XXXXXXXXX;"
}

@jimbo831
Copy link
Author

I also manually verified all the values coming from the plugin by looking through the dev tools as well and the values match.

@eyeoniqbond
Copy link

Hmm. You could try making sure you're using the updated version of the app since it did warn about that in the post. Also I don't know why it would matter but you could try switching the auth_id and sess so that auth_id and it's value is to the left of the sess and it's value so it matches what the wiki shows. That's how my json looks with auth_id listed first.

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

2 participants