On 1.9.12 and it fails the auth #17

New Issue

temper · 2025-05-24T21:59:32Z

temper commented

2025-05-24 21:59:32 +00:00

Hi,
I upgraded to 1.9.12 and the auth stopped working. I'm using the chrome ext to get the info and still not working. Couldn't figure out how to get the login page from chrome to work.
It just keeps saying the auth is wrong even though it is what's in the network request :(
Please help 🙏
Love your work!

Hi, I upgraded to 1.9.12 and the auth stopped working. I'm using the chrome ext to get the info and still not working. Couldn't figure out how to get the login page from chrome to work. It just keeps saying the auth is wrong even though it is what's in the network request :( Please help 🙏 Love your work!

em997nz commented

2025-05-25 03:05:59 +00:00

I am having the same issue with both 1.9.12 and 1.9.11. This is using the legacy auth.json method.

temper commented

2025-05-25 05:19:08 +00:00

I am having the same issue with both 1.9.12 and 1.9.11. This is using the legacy auth.json method.
I'm on the legacy auth.json. Couldn't get the other way to even open chrome so not sure what I missed there

> I am having the same issue with both 1.9.12 and 1.9.11. This is using the legacy auth.json method. I'm on the legacy auth.json. Couldn't get the other way to even open chrome so not sure what I missed there

tomyshoes.mfc commented

2025-08-20 09:39:15 +00:00

I have 2 problems with the auth:

I do not use chrome, but firefox (and it insists on loading chrome when auth fails). So better for me would be to open the default browser, unless there is some very specific technical reason it has to be chrome?
When auth fails, the auth.json gets deleted? why is that? Now I have to save a blank copy to rebuild it from scratch (using the "old" method of setting up auth.json)

I have 2 problems with the auth: 1. I do not use chrome, but firefox (and it insists on loading chrome when auth fails). So better for me would be to open the default browser, unless there is some very specific technical reason it has to be chrome? 2. When auth fails, the auth.json gets deleted? why is that? Now I have to save a blank copy to rebuild it from scratch (using the "old" method of setting up auth.json)

whimsical-c4lic0 commented

2025-08-20 18:38:04 +00:00

OF-DL uses a copy of chromium that it downloads and manages for the default auth workflow. Using the user's web browser is not currently supported, and firefox likely won't work from a technical perspective. The browser automation library uses chrome/chromium dev tools to interact with the browser.
The auth.json file is meant to be managed by OF-DL when using the default auth workflow. OF-DL deletes the file when auth fails to make future runs faster (skip attempting auth with a known invalid file). When you are using a legacy auth method, you can prevent this behavior by changing the DisableBrowserAuth config option

1. OF-DL uses a copy of chromium that it downloads and manages for the default auth workflow. Using the user's web browser is not currently supported, and firefox likely won't work from a technical perspective. The browser automation library uses chrome/chromium dev tools to interact with the browser. 2. The auth.json file is meant to be managed by OF-DL when using the default auth workflow. OF-DL deletes the file when auth fails to make future runs faster (skip attempting auth with a known invalid file). When you are using a legacy auth method, you can prevent this behavior by changing the [DisableBrowserAuth](https://docs.ofdl.tools/config/all-configuration-options/#disablebrowserauth) config option

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sim0n00ps/OF-DL#17