Closed rootytemp closed 1 year ago
Regular Bing also returns the same error
Is bing not working now?
Got the same error here
i get the same error
Same problem, with or without jailbreak enabled
me too
Same here, using non-jailbreak.
The same issue as well
Per the instruction, if the token ever doesn't work, you can provide all your cookies as a string instead. This is confirmed working for me using my project.
const bingAIClient = new BingAIClient({
// "_U" cookie from bing.com
// userToken:
// process.env.BINGAI_TOKEN == 'user_provided' ? token : process.env.BINGAI_TOKEN ?? null,
// If the above doesn't work, provide all your cookies as a string instead
cookies: process.env.BINGAI_COOKIES ?? null,
debug: false,
cache: store,
host: process.env.BINGAI_HOST || null,
proxy: process.env.PROXY || null
});
Try this: remove 'x-forwarded-for' from fetch options, or set a valid ip for it instead of '1.1.1.1'
Try this: remove 'x-forwarded-for' from fetch options, or set a valid ip for it instead of '1.1.1.1'
It worked!!!! Thx man
Choose a browser that works with the Bing Chat website. Press f12,find “Network”->"chats",copy the request header,replace the entries in src/BingAIClient.js. Maybe it work
I did both, but it doesn't work. I am using a host cn.bing.com on linux, I set fetchoptions from the original request in the edge browser with authorization and also set full cookies, still gives the error "failed to parse response body"
I went to the Pandora AI project, inserted my cookies, everything works, I insert my cookies at myself, it doesn't work. The module has been updated to the latest version.
When I updated to the latest version and deleted the cookie settings in the settings, I found that I could chat normally.
Seems to be working fine as of @waylaidwanderer/chatgpt-api@1.36.3
with jailbreak mode enabled. I'm using cookies still, haven't tested without.
abortHandshake(
^
Error: Unexpected server response: 403
at ClientRequest.
Try this: remove 'x-forwarded-for' from fetch options, or set a valid ip for it instead of '1.1.1.1'
that's working and thank you
Very strange. Mine was working just fine all day yesterday and all day today until just now. Getting this error:
Oops! Something went wrong. Please try again in a few moments. Here's the specific error message we encountered: /turing/conversation/create: failed to parse response body. <!DOCTYPE html>
Nothing has changed on my end so I fear MS has once again altered something on the backend. Can anyone else confirm?
Try setting your entire string of cookies instead of just the user token cookie (or removing the cookies config key/value entirely).
Try setting your entire string of cookies instead of just the user token cookie (or removing the cookies config key/value entirely).
Apologies for the delayed response. But yes, that turned out to the be the issue. I thought just the _U value was sufficient. Didn't realize there was another suuuuuuuper long cookie value I needed instead. Thank you so much! And great work on this incredible project. Keep it up!
abortHandshake( ^ 错误:客户端请求时出现意外的服务器响应:403。(/root/Desktop/bot/node_modules/ws/lib/websocket.js:888:7) at ClientRequest.emit (node:events:513:28) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient (node:_http_client:701:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) at TLSSocket.socketOnData (node:_http_client:542:22) at TLSSocket.emit (node:events:513:28) at TLSSocket.emit (node:domain:489:12) at addChunk (node:internal/streams/可读性:324:12) at readableAddChunk (node:internal/streams/readable:297:9) 节点.js v18.16.0
Hi buddy, I'm facing the same issue as you. Have you found a solution yet?
just delete 'x-forward-for'in setting.js , and problem solved for me
Describe the bug It's been working for a few days and now i get this bug (with a redirect as well)
(its longer but char limit on github)