Closed lordoffools closed 2 years ago
Can't really do anything unless I have access to your account fix it since I can't replicate it
In theory, you just need the contents of my auth.json to be able to access and diagnose, right?
Done.
Were you using a VPN/Proxy?
nope here
No VPN/Proxy.
Hi, Have the same issue, Can help me? (TypeError: ´NoneType´ object is not iterable)
Happens to me as well, besides the difference it happens after the tenth Auth 404'ed
error message:
marcintosch
You seem to have two compounded issues. The 404 issue is a different one solved in #117.
The second issue appears to be similar to the one noted here.
@DIGITALCRIMINALS did you receive my auth.json from 12 hours ago via email, and was it helpful in allowing you to reproduce?
Hi, Have the same issue, Can help me? (TypeError: ´NoneType´ object is not iterable)
From the error message you posted, that appears to be different from the one described in this bug.
TypeError: 'NoneType' object does not support item assignment
Hi, Have the same issue, Can help me? (TypeError: ´NoneType´ object is not iterable)
From the error message you posted, that appears to be different from the one described in this bug.
TypeError: 'NoneType' object does not support item assignment
Oh, true. Anyway I have had this error for a long time, but apparently, this time it seems to me this variant, but I have had this error since version EDIT: (7.6)
marcintosch
You seem to have two compounded issues. The 404 issue is a different one solved in #117.
The second issue appears to be similar to the one noted here.
Thank you very much, buddy, haven't found the solution before, now everything works fine (and I don't get any NoneType TypeErrors anymore after installing the cert. Thanks a bunch 👍
I have solved with old auth and config files following this one
this is a fix for the issue
and changing "active": active with "active": true in the auth file
Anyone having any luck diagnosing this? Anything I can help with in terms of data or attempts to reproduce using different settings?
If it helps, I only have this problem with OF, and not Fansly. Granted, if number of profiles is a factor, then that would explain it since Fansly is significantly less for me.
Anyone with >1,000 profiles in their account able to run this? Or are you also hitting this issue?
Trying to figure out if it's due to that or something else.
Still trying to resolve this issue. Adjusting settings, etc. Not having any luck.
Anyone have any insights into what this error means? As far as I can tell, it literally hits right as the script tries to pull the list of profiles.
I just realized that I never posted my own error here (it matches the above):
`Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x10e0e67a0> Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x10d7b01c0>
Traceback (most recent call last):
File "/start_ofd.py", line 104, in
This starts right after a successful login (so I'm assuming it's when it tries to scrape the list of profiles). Then proceeds with a massively long list of:
Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x10e0e67a0> Unclosed client session client_session: <aiohttp.client.ClientSession object at 0x10d7b01c0>
That repeats for a while until it hits the exception noted above in the traceback.
Anyone else having any luck with this?
I'm stuck. Not making any progress despite trying different things and researching the issue as best I can.
I feel like I'm yelling into the wind, at times, when I scroll up. :(
The rest of you who were having this issue above, are you still reproducing it?
Thanks!
FYI, still able to repro with latest pull from master.
Is there a way to set this to be verbose so it outputs where it's at with the profile scraping? Maybe it's hitting a bad profile?
Occasionally it fails after 15-30s of scraping, instead of immediately.
Anyone else still encountering this issue with a high number of subscribed profiles (paid or free, doesn't matter it seems).
I'm still reproducing this bug. Can't figure out how to fix.
@DIGITALCRIMINALS I can send you an updated auth.json if it'll help. Just let me know.
Thanks all.
Anyone else reproducing this issue?
Friendly nudge here.
Those of you who were encountering this issue earlier, are you still able to repro? I am. And I'm stuck. Can't figure out how to get past this.
It's due to having too many requests, I was in the process of fixing this but I had to do something. I'd need a new authentication again to fix this.
The problem replies in the results2 variable which contains a list of users, but self.get_user will return None if there's a http error.
[OnlyFans | create_auth.py)]
for subscription in subscriptions:
subscription["session_manager"] = self.session_manager
if extra_info:
task = asyncio.create_task(
self.get_user(subscription["username"])
)
tasks.append(task)
results2 = await asyncio.gather(*tasks)
@DIGITALCRIMINALS glad to see you're Ok! Happy to send over a new auth.json to help out. Let me get re-authenticated and I'll email it over.
Sent. Please let me know if it didn't come through and/or if it doesn't work for you. @DIGITALCRIMINALS
Got it, thanks
I'm not encountering the error, is it still a problem for you?
Still reproduces.
Let me pull the latest code vs. 7.6.1.
Unfortunately, still reproduces with the latest pull.
Try the latest commit
Fixed for me now with the latest commit.
Thanks, @DIGITALCRIMINALS!
Identical to #71. I'm having this issue after upgrading to 7.6.1 just now.
Exactly the same error as above. Prior to 7.6.1, I ran just fine with threads = -1.
I have over 1,000 profiles.
I just tried threads = 100, and still hit this issue.
Fails with threads = 10, as well.
Originally posted by @lordofcookies in https://github.com/DIGITALCRIMINALS/OnlyFans/issues/71#issuecomment-985973690