Hanging on characterAI.authenticateAsGuest about node_characterai HOT 12 CLOSED

Yes its cloudflare's dumb shit with waiting times that might be yielding it, sorry!

from node_characterai.

Damn that's too bad. Thanks for the help though!

from node_characterai.

Do you know if its possible to wait until the cloudflare protection has passed? Once it starts hanging it doesn't stop and I'm wondering if I can just increase the timeout or something. Still a noob here though so I'm not sure lol.

from node_characterai.

No because its unpredictable sadly

from node_characterai.

Can confirm it hangs and doesn't do anything. I am currently invesgating into the issue.

from node_characterai.

[node_characterai] Puppeteer - ProtocolError: Page.navigate timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
client.js:211
        if (request.status() === 200) {      
                    ^

TypeError: Cannot read properties of undefined (reading 'status')
    at Client.authenticateAsGuest (client.js:211:21)

from node_characterai.

Hello, upon testing, the issue seems like its coming from a new slowdown of the new headless mode. Trying in old true headless mode seems to be working perfectly.

from node_characterai.

For some reason it feels like I cant even run it properly anymore.. I need to probably investigate deeper on this issue.

from node_characterai.

So sometimes it seems to work properly and sometimes it just hands on "https://beta.character.ai/chat/auth/lazy/". Running it on headful right now and I think they're now either waiting for you to click on the Accept cookie button, or they have a rate limit, or more, user input

from node_characterai.

Ok, after investigation, it might be an issue with CORS policies either from puppeteer or stealth plugin.

EDIT: Sometimes it works and sometimes it doesnt. I don't really know why.

from node_characterai.

Ok so I have made an experimental thing that keeps trying to generate a session for atleast 20 times until a response is recieved because I suspect there is now something around uuids.

from node_characterai.

Problem seems to have been fixed with this solution. If any have any errors or feedback, let me know. Commits: d1b6272 and 25a541d

from node_characterai.