Blocked in production

[jskrn-1911]

it works totaly fine in local environment

when we deploy it in production it starts throwing errors like blocked by youtube or Transcript is disabled on this vedio

i tried deploying server and next js app to diff platform like render, digital ocean and vercel but the issue is not solving

and also i tried Using Niginx DNS server using ip address but issue is not solving

[teh0]

Same issue for me (firebase functions and Nextjs proxy server function)

[MohammeSafin]

same issue here. I am very disappointed since the last commit is 11 months ago.

[phalla-doll]

Is there any workaround for this?

[artemdrei]

Same issue. Also want some workaround.

[0xAmansol]

is there any workarround for this?

[bryantwilliam]

firebase cloud functions also broken. local working in emulator

[bryantwilliam]

Today it started working again! But this is a wakeup call to have a backup plan incase it fails in the future...
[Edit] Nevermind, broken again today. I'll be moving to a difference solution.

[thomasperge]

Hey guys, you need to use a residential proxy because YouTube detects that your IP is coming from providers like Vercel, Render, Netlify, OVH, etc. These IPs belong to cloud servers, and YouTube typically blocks traffic from cloud-based IPs. To avoid this, you need to use a residential IP — like a real user would have, not one from a cloud service. So either host your API on a server connected to your home internet, or purchase a residential proxy.

[thomasperge]

is there any workarround for this?

#43 (comment)

[Shub0899]

is there any workarround for this?

#43 (comment)

can u please contact me on telegram please -- @Shubhash089

please bro

[thomasperge]

is there any workarround for this?

#43 (comment)

can u please contact me on telegram please -- @Shubhash089

please bro

Discord.

[calebchiang]

is there any workarround for this?

#43 (comment)

Hey guys, you need to use a residential proxy because YouTube detects that your IP is coming from providers like Vercel, Render, Netlify, OVH, etc. These IPs belong to cloud servers, and YouTube typically blocks traffic from cloud-based IPs. To avoid this, you need to use a residential IP — like a real user would have, not one from a cloud service. So either host your API on a server connected to your home internet, or purchase a residential proxy.

So is it possible to host my api on a server connected to my home internet and use a residential proxy as a fallback in case that fails? How scalable is this for production?

[thomasperge]

is there any workarround for this?

#43 (comment)

Hey guys, you need to use a residential proxy because YouTube detects that your IP is coming from providers like Vercel, Render, Netlify, OVH, etc. These IPs belong to cloud servers, and YouTube typically blocks traffic from cloud-based IPs. To avoid this, you need to use a residential IP — like a real user would have, not one from a cloud service. So either host your API on a server connected to your home internet, or purchase a residential proxy.

So is it possible to host my api on a server connected to my home internet and use a residential proxy as a fallback in case that fails? How scalable is this for production?

If you’re on your own internet connection, there’s no problem

[rgsk]

another method that works in production
#45 (comment)