Bot say "Sorry, you need to login first to access this service."

[Am1nCmd]

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 }

[Leask]

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.

[Am1nCmd]

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 GitHubhttps://github.com/Leask/halbot/issues/29#issuecomment-1531486720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADVBANLUWXELEGNORNXPPXLXEEEHJANCNFSM6AAAAAAXTBGKGA. You are receiving this because you authored the thread.Message ID: @.***>

[Leask]

Thanks for your info. I will reopen this issue and check on your link. Thanks!

[Leask]

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.