crunchy-labs / crunchy-cli

👇 Command-line downloader for Crunchyroll
MIT License
606 stars 63 forks source link

Triggered Cloudflare Bot Protection #386

Closed GTM009 closed 7 months ago

GTM009 commented 7 months ago

Cammand : crunchy login --credentials email: password

Even giving same error for while ripping Content

Output : :: Triggered Cloudflare bot protection (https://www.crunchyroll.com/index/v2): <!DOCTYPE html>Just a moment...

westhecool commented 7 months ago

Are you using a VPN?

GTM009 commented 7 months ago

Are you using a VPN?

No Its VPS (From The Starting I Use Crunchy On VPS)

Edit : sometimes its working but most of the time i am getting this error

westhecool commented 7 months ago

Are you using a VPN?

No Its VPS (From The Starting I Use Crunchy On VPS)

Edit : sometimes its working but most of the time i am getting this error

Cloudflare probably marked the IP of your server as suspicious. You can try using a VPN or proxy.

GTM009 commented 7 months ago

Are you using a VPN?

No Its VPS (From The Starting I Use Crunchy On VPS) Edit : sometimes its working but most of the time i am getting this error

Cloudflare probably marked the IP of your server as suspicious. You can try using a VPN or proxy.

Proxy will be costly, need a way to Bypass it because sometimes its working I even ripped whole season

GTM009 commented 7 months ago

Closing this as i got solution for this I just Adding User-Agent in every cmd to avoid this issue Thanks all

GTM009 commented 7 months ago

User-Agent didn't worked

Kartatz commented 7 months ago

I don't see how this is a crunchy-cli issue.

Cloudflare is blocking you due to suspicious network traffic. There is nothing crunchy-cli can do to prevent that.

bytedream commented 7 months ago

This is a duplicate of #104. I already did the best I can to construct the requests so that Cloudflare doesn't get triggered but it cannot be 100% avoided. I have the same setup as you, crunchy-cli on a VPS, and get blocked by Cloudflare too. The only way to prevent this from happening it using a VPN on the VPS an tunnel all traffic through it.