Some clarification. For OFDL to work you need a working OF account in good standing. OFDL does not bypass that. If you can login to your OF account in a browser, you can use OFDL. I am in an age verification state and use no VPN with OFDL and OF with no problems. My account predates the verification requirements so I am not sure that makes a difference or not. I have a valid credit card on file and have purchased content.
For OFDL to work in it's current form you need 5 things to be correct.
1. A working OF account with content already ready to download. Meaning free or purchased. To sub to a free account currently you need a valid payment type.
2. The last most recent version of OFDL. 1.10.6 (Others MAY work but not verified.)
3. A valid rules.json file. My md5sum is a2f3b232fc44c30bd1ab4456f1157b41 but it's text so could be off by a char for some people and still work. It's in this thread somewhere.
4. A valid auth.json. Use the browser extension, do not hand author this, and I suggest NOT using the built in browser auth either.
5.
Valid encryption keys - named correctly, in the correct location. (The key server appears to be working right now, but due to the reports in this thread, I'd say it would be far better to have local keys and it would certainly be faster and more reliable.)
cdm\devices\chrome_1610
device_client_id_blob
device_private_key
If OFDL opens a browser window when launched then auth.json is not valid. Period.
This works if everything is correct. I bought content this past week, and downloaded it and it's fine and DRM free. My copy never stopped working.