-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Bot say "Sorry, you need to login first to access this service." #29
Comments
Sometimes the Bing server can identify the hack of the way we use the token outside the website. We can only handle this issue once Bing opens a real API server to the developers. 😭 |
I already do that to get new token, but the problem still exist.
have you look at this https://github.com/acheong08/EdgeGPT maybe it can help you to update using new method to get Token
On 2 May 2023, at 20.32, Leask ***@***.***> wrote:
Sometimes the Bing server can identify the hack of the way we use the token outside the website. We can only handle this issue once Bing opens a real API server to the developers. 😭
You can log in to the website again to get a new token and restart the bot. I hope it can help.
—
Reply to this email directly, view it on GitHub<#29 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADVBANLUWXELEGNORNXPPXLXEEEHJANCNFSM6AAAAAAXTBGKGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thanks for your info. I will reopen this issue and check on your link. Thanks! |
Because the official OpenAI APIs are getting more and more powerful and controllable. I am going to fade out legacy Bing web-hacking. Sorry about this. |
I already login and using new cookies but bot always response like that
here's the logs
[HAL] Prompt: hello [HAL] UnauthorizedRequest: Sorry, you need to login first to access this service. at BingAIClient.sendMessage (file:///root/node_modules/@waylaidwanderer/chatgpt-api/src/BingAIClient.js:188:31) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.send (file:///root/node_modules/utilitas/lib/hal.mjs:64:35) at async file:///root/node_modules/halbot/skills/60_chat.mjs:42:34 at async Promise.all (index 0) at async action (file:///root/node_modules/halbot/skills/60_chat.mjs:62:5) at async execute (/root/node_modules/telegraf/lib/composer.js:485:17) at async /root/node_modules/telegraf/lib/composer.js:486:21 at async execute (/root/node_modules/telegraf/lib/composer.js:485:17) at async /root/node_modules/telegraf/lib/composer.js:486:21 [60_CHAT] Error: Sorry, you need to login first to access this service. at newError (file:///root/node_modules/utilitas/lib/utilitas.mjs:17:49) at throwError (file:///root/node_modules/utilitas/lib/utilitas.mjs:18:50) at Object.send (file:///root/node_modules/utilitas/lib/hal.mjs:71:13) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async file:///root/node_modules/halbot/skills/60_chat.mjs:42:34 at async Promise.all (index 0) at async action (file:///root/node_modules/halbot/skills/60_chat.mjs:62:5) at async execute (/root/node_modules/telegraf/lib/composer.js:485:17) at async /root/node_modules/telegraf/lib/composer.js:486:21 at async execute (/root/node_modules/telegraf/lib/composer.js:485:17) { status: 500 }
The text was updated successfully, but these errors were encountered: