snowby666 / poe-api-wrapper

👾 A Python API wrapper for Poe.com. With this, you will have free access to GPT-4, Claude, Llama, Gemini, Mistral and more! 🚀
https://pypi.org/project/poe-api-wrapper/
GNU General Public License v3.0
677 stars 81 forks source link

Take a look at the code, it stopped working and the basic example of your code no longer works #128

Closed noseon closed 2 weeks ago

noseon commented 3 months ago

Take a look at the code, it stopped working and the basic example of your code no longer works

snowby666 commented 3 months ago

Can you try updating the lib to the 1.4.1 version to check if it works now?

noseon commented 3 months ago

After the update it shows this error --> 2024-03-22 18:33:17.473 | DEBUG | poe_api_wrapper.api:connect_ws:164 - An unknown error occurred. Raw response data: <!DOCTYPE html>Just a moment...

zukixa commented 3 months ago

this is a cloudflare problem, they're blocking your request, not the wrappers' fault

noseon commented 3 months ago

this is a cloudflare problem, they're blocking your request, not the wrappers' fault

Well, I used Google Colab to run the bots, so if the error you mentioned is true, it will be difficult to use now =/ . but a matter of less than 1 week ago it worked fine

zukixa commented 3 months ago

poe itself watches this repo closely so things can change dynamically, it happened in the previous iteration and will continue happening

noseon commented 3 months ago

the poe could leave it as official. This api using Telegram is very good

RuohaoYan commented 3 months ago

regret

bluusun commented 3 months ago

Adding Cloudflare protection is quite common - most sites use that to protect from bad bots. iDB 2024-03-28 at 20 53 15

I feel adding these two cookies (only show on poe.com) will work.

This was also an issue here (and they solved it):

https://github.com/xtekky/gpt4free

Cisen07 commented 3 months ago

It looks like there are no more p_lat items here image

phamxtien commented 3 months ago

It looks like there are no more p_lat items here

Delete all cookie and login again or use Edge instead Chrome

snowby666 commented 2 weeks ago

This is fixed in the v1.4.3. Please check documentation for new config.