Now my server is up and running again.
This is what I got from ChatGPT.
The issue likely stems from routing or DNS configuration changes made when WARP was activated. When you ran warp-cli connect, it might have altered the default network routing table, redirecting all traffic (including internal traffic) through WARP. If the routing was not configured correctly, the server may lose network connectivity, including access to its own services.
I was hoping the get the Piped running on my server and found that : a free Cloudflare WARP connection and tunnel traffic through it This will help bypass YouTube’s bot detection for your Piped instance. Then I followed the suggestions on ChatGPT then get to this mess.
Can anyone please help me to open this post Now my server is up and running again.
This is what I got from ChatGPT.
The issue likely stems from routing or DNS configuration changes made when WARP was activated. When you ran warp-cli connect, it might have altered the default network routing table, redirecting all traffic (including internal traffic) through WARP. If the routing was not configured correctly, the server may lose network connectivity, including access to its own services.
I was hoping the get the Piped running on my server and found that : a free Cloudflare WARP connection and tunnel traffic through it This will help bypass YouTube’s bot detection for your Piped instance. Then I followed the suggestions on ChatGPT then get to this mess.
Can anyone please help me to open this post : Piped Got error: “Sign in to confirm that you’re not a bot” and this one is resloved.
By the way, another question the Debian 11 is depreciated, do I need to upgrade to 12?