Piped: how to fix "Sign in to confirm that you're not a bot"

Freee4U

Setting up a Cloudflare WARP connection for your OVH VPS to tunnel traffic is a practical way to bypass restrictions like YouTube’s bot detection. Below are the steps to configure this:

—

1. Install Cloudflare WARP

a. Install the Cloudflare WARP Client

Add the Cloudflare Package Signing Key:

   wget https://pkg.cloudflareclient.com/pubkey.gpg
   sudo gpg --import pubkey.gpg

Add the Cloudflare Repository:

   echo "deb http://pkg.cloudflareclient.com/ $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/cloudflare-client.list

Install the Cloudflare WARP Client:

   sudo apt update
   sudo apt install cloudflare-warp

—

2. Register and Connect WARP

a. Register WARP

Run:
```
   warp-cli register
```
This registers your system with Cloudflare’s WARP network.

b. Connect to WARP

Connect using:
```
   warp-cli connect
```
Verify connection:
```
   warp-cli status
```

—

3. Route Piped Traffic Through WARP

a. Set Up IP Rules

Mark Traffic for Routing:
Create a routing rule so only Piped traffic goes through WARP:
```
   ip rule add fwmark 1 table 51820
```

Add Routing Table:
Configure the routing table:

   ip route add default dev wgcf table 51820

Update Piped Configuration:
Modify the Piped backend configuration to use a proxy that routes traffic through the WARP connection.

—

4. Automate WARP on Boot

To ensure WARP reconnects after reboots:

Create a systemd service:

   sudo nano /etc/systemd/system/cloudflare-warp.service

Add the following:

   [Unit]
   Description=Cloudflare WARP Service
   After=network.target

   [Service]
   ExecStart=/usr/bin/warp-cli connect
   Restart=always
   User=root

   [Install]
   WantedBy=multi-user.target

Enable and start the service:

   sudo systemctl enable cloudflare-warp
   sudo systemctl start cloudflare-warp

—

5. Test Piped

Restart your Piped instance:
```
   yunohost service restart piped
```
Test if Piped can fetch YouTube content without the “Sign in to confirm that you’re not a bot” error.

—

Additional Notes:

If YouTube blocks Cloudflare WARP in the future, consider integrating fallback proxies.
Monitor your WARP connection regularly to ensure its stability.

Let me know if you encounter any issues!