-
-
Notifications
You must be signed in to change notification settings - Fork 975
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
[patreon][error] NotFoundError: Requested creator could not be found #4699
Comments
I tried a couple of creators (more than 5) listed in Patreon's front page and got this error once. The one with the error worked when running it a second time. You could try v1.26.0, which uses the old edit: related to #4639 |
So I've tried with 1.26.0 and 1.26.1; same issue. However, it does seem you're correct when not 'logged in', it will retrieve publicly available posts without issue. However, when using Cookies (for login authentication), then it shows the error. I'm unsure if it's related to authentication or related to some different post path when being 'logged in' vs not. |
Even with logged in cookies, I don't get this error ... I'd need the first file created by I should also implement a way to directly specify a creator's campaign ID to at least have a workaround in cases like this. edit: just the line containing |
Unfortunately, I think my page output will no longer be useful. It randomly started working for me as of five minutes ago (7:30pm EST) despite not working just prior to that. If it goes back to not working, I'll update with the relevant line. However, it seems like someone else is experiencing the issue now: #4715 |
For me too - I can download from Patreon again. |
Well, whatever this was, it is now possible to manually set the |
Please note I've substituted any identifiable names in the paths. (User and Creator respectively.)
This error occurs with the latest nightly build and as far as I can tell (since my config hasn't changed in months), there are no configuration issues on my end.
(Edit: This issue was previously marked as fixed in other Issues threads. I will also add that my Cookies had been refreshed, just in case.)
The text was updated successfully, but these errors were encountered: