- Home
- Skills
- DevOps & Cloud
- Wrong Door: Fix Cloudflare Tunnel Routing Problems
More screenshots
Works with the AI Agents you already use
Wrong Door: Fix Cloudflare Tunnel Routing Problems
Fix a Cloudflare Tunnel serving the wrong site, looping redirects or sending traffic to the wrong machine. Your agent also proves what Cloudflare is really serving and checks that a private app is still private.
$5
Wrong Door: Fix Cloudflare Tunnel Routing Problems
Example session with this skill installed
I moved my app to a new VM and started cloudflared there with the same tunnel. Now about half the page loads show old data. Also I added a hostname through the API with a PUT to configurations and my two other hostnames went to 404.
- Read your context and instructions
- Compiled the wrong door
Summary
Your old VM is most likely still running cloudflared, so Cloudflare splits requests between the old and new copies of your app. Your PUT replaced the whole tunnel configuration, which removed the other two hostnames.
Symptom and cause
| Problem | Cause |
|---|---|
| Half the page loads show old data | Two connectors serve one tunnel |
| Two hostnames return 404 | The PUT replaced the full config |
What the answer covers
- Confirm the split between connectors.
- Retire the old connector safely.
- Rebuild the config without losing what is left.
- Test all three hostnames.
- Check the old VM for writes that only reached it during the split.
The skill gives your agent every command.
Connects securely to your tools. The creator never sees your data.
About this skill
These problems rarely show up as tunnel errors.
Your agent fixes
localhostresolving to IPv6 and reaching the wrong site- Redirect loops and redirects pointing at
http:// - Two machines on one tunnel splitting your traffic
- API updates that erase every other hostname
- A tunnel that flaps while its health check stays green
- Replaced files that visitors can't see, with the command that proves what Cloudflare is serving
It also checks that a private app has an Access login, because a published hostname without one is open to the internet.
How it was tested
Each fix comes from running production tunnels, and an independent review checked them against Cloudflare's documentation.
Dashboard menus change often.
Covers tunnels and Access, not Workers or Pages.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Requires
Permissions
Allowed Hosts
File Scopes
Commands go to Cloudflare's API and your own hosts. Tunnel tokens are treated as secrets.