I'm getting this same 403 error after running it with cron without any issues for several months, so I know it's not the login. Something changed with the login portal, I'm guessing.
kyledeanreinford opened this issue · comments
I'm getting this same 403 error after running it with cron without any issues for several months, so I know it's not the login. Something changed with the login portal, I'm guessing.
Seems to have stopped working on October 8th for me (I built a mini times scraper using your login function and my last successful stat scrape was for the 7th).
When I try putting my username/password into your site, it seems to have an issue as well.
Originally posted by @kyledeanreinford in #3 (comment)
It looks like something changed on the NYT login side for the URL we were using there. I've reproduced this issue on my end, looking into workarounds at the moment
I tweaked the user agent a bit more to match what the NYT API is expecting and this seems to be working again. I'm able to log in on my side at least after a fresh pull. @kyledeanreinford pull the latest and give it a shot!
Works for me too! Appreciate it Matt.