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
Bypass for The Athletic not working #859
Comments
I can confirm this problem both on Chrome and Firefox with uorigin and cookies removed. |
Also confirming this problem in Microsoft Edge/Google Chrome |
I was able to read articles from the Athletic up until yesterday ! But, it is not working for me today ! I have tried on Windows Edge, Chrome and Firefox, and also, on Firefox and Chrome on Linux. I have also tried the recommended troubleshoots, bit to no effect ! I, however am able to read articles from the Financial Times, the New York Times and the WashingtonPost. So, I suppose the issue exists only for The Athletic's Paywall. Thank You for your effort ! |
Same issue right now for me. Using Firefox 1.75 on this link, does not work. |
Same issue for me on Chrome, stopped working when I checked this morning. |
Same issue for me. Stopped working today in Chrome and Firefox. Was working yesterday. |
Having the same issue as @fw88. Was working yesterday. |
Looks like that article is behind a hard paywall? |
Is it possible to get around hard paywalls? |
Buying a subscription? or try the free trial. |
All good things must come to an end. Thanks for making it work before. |
@iamadamdev -- any plan for a workaround? If you did it once, I'm sure you can do it again ;) |
Please can you find a solution for this, I will happily donate if this is resolved. |
Install the apk and you can read for free. Then clear cache after number of free articles have been reached. |
Removed in latest version. |
Hello,
Thank you for this Chrome extension.
Paywall bypass for The Athletic appears not to be working at the moment. Please see the attached screenshot.
I followed all the recommended steps and also deleted and re-installed the extension -- both did not seem to fix the issue.
Thanks
Requests not following these instructions will be ignored.
The text was updated successfully, but these errors were encountered: