How are you handling YouTube bot detection with yt-dlp on a cloud server/Railway?

I'm trying to run yt-dlp as part of a server-side video-processing workflow. Everything works reliably when I run it locally from my residential connection, but when I deploy the same downloader to a cloud server (Railway), YouTube frequently returns: Sign in to confirm you're not a bot. The important part is that I'm looking for a reliable server-side solution, not something that only works temporarily on my local machine. Current setup Backend: Node.js Downloader: yt-dlp Server: Railway FFmpeg for processing YouTube URLs areDownloads are processed automatically on the server Local Docker environment works much better than the Railway deployment I've already tested/upgraded yt-dlp and experimented with cookies, different YouTube clients, request delays, etc., but the cloud deployment still gets blocked. What I'm trying to understand Is the main problem the IP/data-center reputation of Railway? Is there currently a reliable way to use yt-dlp from a cloud server without getting the bot-detection page? Are PO Tokens / JS challenge solving currently required for normal video downloads, or only for particular clients/formats? If cookies are required, what is the recommended architecture for a server-side application? I don't want to expose or continuously reuse a personal Google/YouTube account. Are there particular yt-dlp extractor/client settings that currently work better from cloud IPs? Has anyone successfully deployed yt-dlp on Railway, Fly.io, AWS, Hetzner, DigitalOcean, etc. and achieved consistent YouTube downloads? If the issue is fundamentally the cloud IP range, what type of infrastructure/network setup actually works reliably? I'm not looking for a list of alternative downloader APIs. I'm specifically interested in understanding what is happening with YouTube's bot detection and how people are currently solving it when the downloader has to run server-side. If you've successfully solved this in 2026, I'd especially appreciate details about your setup, including: Hosting provider yt-dlp version YouTube client configuration Whether cookies are used Whether PO Tokens are used Whether a proxy is involved Whether it works consistently over repeated downloads Thanks!